Product ideas | Community
Skip to main content

10000 Ideas

Sujatha_TSNew Participant

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.

Adele_JNew Participant

Microsoft Teams Approval Request to include proof name and project titleNew

Description - We use the Workfront for Microsoft Teams plug-in and what we're finding is that when we get an approval request to approve a proof the notification does not include the proof name or the project title that the proof is part of. It simply says the proof owner wants you to approve the proof, with a button to "Go to proof" or to "Comment".When I get a new issue (e.g., packaging request) it includes the title of the new issue/request with the live link to that issue, and when I get a new update on a proof (where someone else has added a comment to a proof that I am on) the notification in Teams includes the name of the document and the project title with live links to both of them.So you have to click on the Approval Request notification to go through to the proof in order to see which proof and which project it is for. Is there a way of including that in the Teams notification?  Why is this feature important to you - It would increase time efficiency as it would help my Users to identify which project a proof was for "at a glance" rather than having to click through on the notification to the proof itself to find out which campaign/project the proof relates to. It would enable them to prioritise what they “react” to first based on knowing their own project priorities.  How would you like the feature to work - I would like it to work in the same way that a new issue or new update notification works where the project title and the proof name are included in the notification and these are both live links to the project and document. The buttons for "Go to proof" and "Comment" can remain in the notification. Current Behaviour - The approval request appears in the Workfront for Teams app Chat feed, in the same way a new message in a chat from someone else appears. And in the notification is detail about the proof that doesn't mean anything to my users. It also has a "Go to proof" button and a "Comment" button. Both of these are useful, but it would be more efficient to the user to know what the project and proof name were before having to click through to find out.