Skip to main content

Filter by idea status

10000+ Ideas

Add "Flat Table" Visualizations to WorkspaceNew

Description -   While Breakdowns are great, it can make the visuals harder, especially if you want to replicate something like a source/medium report like in GA; or any other 1 to 1 relationship.   Being able to add multiple dimension columns followed by multiple metric columns, and to be able to sort those columns would go a long way to allowing simpler visualizations when needed. Having access to both Freeform breakdowns AND flat table visualizations would allow for more ways to represent our data (without having to take it out to Report Builder)     Why is this feature important to you -   More ways to visualize data is always important, and being able to represent and sort data based data sets as a whole would allow people to have a simpler view of sets of data...   As in, instead of sorting by Metric A on Dimension 1 (altogether), then a sub-sort on the metric by Dimension 2 (i.e the breakdown). The Sort would be on the combination of Dimension 1 and Dimension 2 together.     How would you like the feature to work -   Create sets of data in a flat table visualization that can be sorted as sets, it will allow us to see information in a cleaner view: Both freeform (drill down data) and flat tables have an important roll in data visualizations.   Freeform collect all the data consolidated at each level, whereas flat tables would split those dimensions up, but allow us to sort fully by which combinations are most relevant.     Current Behaviour -   This is a new visualization type that could be used in parallel with the existing freeform tables.

Enable request routing option between the formNew

Description -Why is this feature important to you - This has been an ask from long, I understand we can do this via fusion today, but having this provisioned via custom form will be of great help. This will not only help user not to get confused what topic queue option to choose but just by choosing the right option between the form like what deliverables they are looking for will bring them additional fields to detail out and submit the request.  Also helps admin not to create all general fields for all the forms.  How would you like the feature to work - This comes in handy when we are looking for integrated custom forms. When we open a custom form we should be straight going to filling form to basic or general details. Followed by to choose what one is looking for and choose the same to fill in as they submit the request. eg., General information fields that any subgroup might want to have like geo, budget, business areas, industries etc. With a section break to choose the option what deliverables requestor is looking for like Social, thoughtleadership, video etc filling in details to fields populated should be received by right team of social, thoughtleadership or video.  Current Behaviour - We can set routing rules by queue topics only, we are unable start with all mandatory fields we might want requestors to add and further have drop down or radio button where it might allow routing option to right user or team to the request.

bjoern__koth
bjoern__kothNew Participant

Adobe Client Data Layer - possibility to preprocess event dataNew

Description - Currently, the ACDL does not support modifying the event object at a global scale, meaning adaptations or patches to the incoming data can be applied and work for every other ACDL-triggered that executes. One can push up an event listener to that specific ACDL event as custom code, that allows modifying the event and passing it into the rule actions by calling "trigger()". This is for instance the way AEM core components and Launch / Tags communicate together (a slightly overengineered approach that requires transformation of the incoming event data to make it actually usable inside of Launch, but is just my opionion). However, this works only on that single rule / event. Any additional rule that listens to the same ACDL event will not see these applied modifications. Why is this feature important to you - How often does it happen that for some reason data may be corrupted and a fix could be a small patch in Launch itself, rather than fixing the data problem at its source (I know, the data should be correct, but this just happens sometimes). Meaning, if a particular attribute in the data is not correct, I would have to fix it in every single rule that is processing this information, alternatively in a separate data element. But without data element this is just impossible to maintain. How would you like the feature to work - add some kind of "preprocessing" callback feature, that allows modifying the incoming ACDL data as soon as it is pushed, that executed before any ACDL event.This could be done directly in the ACDL extension configuration by providing a custom code block that gives access to modify the raw event data Current Behaviour - raw event data cannot be modified effectively.