Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

bigbaldbasso
bigbaldbassoNew Participant

Fix Exception in Web SDKNew

Description - An exception is thrown and processing halts when using the WebSDK extension and there are two instances of the adobe_mc in the query string. Note:  this was reported in Support Case E-001008770, and even though it does not seem to be a Analytics-related problem I was asked to also enter it here.  For good measure, it was also reported in the Alloy extension github as issue #346.  Hopefully one of these will get it fixed. Why is this feature important to you - While there should not be two instances of the adobe_mc parameter in the query string when attempting to pass identity between domains, the WebSDK extension should deal with the situation better than throwing and exception and halting processing.  When this happens, no tracking occurs, no test propositions are returned, etc. How would you like the feature to work - When there are two instances of the same parameter, the results of a parse operation are returned as an array, not a string.  The extension code that is looking for the identity parameter needs to be aware of this, check the type and proceed accordingly instead of assuming it will be a string and throwing an exception when attempting a split operation. Current Behaviour - The following error popped up in the console:Uncaught (in promise) TypeError: [alloy] [Identity] An error occurred while executing the getIdentity command.Caused by: [Identity] An error occurred while executing the onBeforeRequest lifecycle hook.Caused by: o.split is not a functionThis kept the page from working. Investigation showed the root of the problem was the adobe_mc parameter had been appended to the URL twice (by accident). The code that parses the parameter value does not do a type check after getting the parameter, and when there are more than one instance of a parameter it is represented by an array instead of a string. The code attempts to do a split() operation, but since the type is Array the exception is thrown. To recreate, simply duplicate the adobe_mc parameter on any link and load it.The extension needs to be updated to check the type and take appropriate action if it is an Array and not a String.

sgarrisNew Participant

Controlling for Word Counts in Custom Form Text FieldsNew

There is no way to control for or enforce a custom word or character count within the various custom form text fields. While there are native character limits in the various fields available (https://experienceleague.adobe.com/docs/workfront/using/basics/update-work-items-view-updates/character-limits-in-fields.html?lang=en), none are customizable and each field has its own unique strengths and weaknesses. This functionality would be particularly valuable for the text field with formatting as we are using these forms to author content and the text often needs to fit within a predetermined amount of space within a report's template or on a webpage. We are using a Fusion integration to move the text from these text fields to AEM Assets, and need a way to flag to the creatives who are authoring the text within Workfront how many words they can author to control for publication errors before they submit their content. We've explored a lot of different options and are surprised there is no way at all to enforce a limit or even highlight the word count to authors within the form. We've explored calculated fields as well and think the LEFT or LEN functions could be interesting, but they are incapable of referencing rich text fields. Is there any plan to include the optionality to enforce a word or character count within custom form text fields or show a word count to users using the field within the form?

ctroNew Participant

Workspace: Add a way to group related reports and visualizationsNew

Description -Add a way to group related reports and visualizations. It could be as simple as a container box, like in the attached image. Other options, change background colors, change border colors, etc. Why is this feature important to you -We have a few 'snapshot' dashboards that have many summaries, and it would be great to be able to group and differentiate them. This way, you can glance at it, see the overall picture, and not go cross-eyed. We've been adding in text visualizations to give some separation but sometimes it just makes the report long instead of easy to scan. BTW, we don't rely on these for takeaways and/or alerts, but they are handy for quick glances and answering frequently occurring questions. Some of other dashboard would benefit from this as well, but those are typically more specific. How would you like the feature to work -Add a method to group, define, or visually separate two or more reports and/or visualizations. Select the items to group, right click, and have the option to group in a box, change background color, change border color, or whatever method is implemented to do this. While multiple ways to differentiate would be okay, I think only one is needed. Current Behaviour -The only distinguishing feature currently is the description.  Sample data: obviously just the same two summaries in each 'group' but it's easy to see in this display that there are four separate chunks of information.