Skip to main content

Ideas

Filter by idea status

10000+ Ideas

bjoern-koth
Adobe Employee
bjoern-kothAdobe Employee

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.

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.

brentradLevel 5

Add Number of Users column to Workspace managerNew

DescriptionIt is difficult to determine how frequently Workspace projects are accessed. Adding a feature to the Workspace homepage that shows the number of unique users who have viewed the project will make it easy for admins to quickly find this information. Why is this feature important to youAllows users, especially admins, to see which Workspace projects are used frequently without having to parse Usage Log data. This may also make it easier for admins to determine if a Workspace project can potentially be removed, as projects that have not been engaged with in, say, 180 days may not be useful anymore. Adobe has made a "Used In" column available in the Filter/Segment and Calculated Metric manager pages, which has made it easy for us to see how a component is used in other components.  How would you like the feature to workAdd "Number of Users" as a table option in the Workspace manager. This would show the total number of unique users who have engaged with a Workspace project (viewed, created, modified, shared, etc.) over a set time period (e.g. last 90/180 days).  Current BehaviourThe number of users who have accessed a Workspace project is not currently available in the Workspace manager for Adobe Analytics or Customer Journey Analytics. To find which projects are used, admins must parse through Audit Logs (CJA) or Usage Logs (AA). This is time consuming.

lizanneNew Member

Integrate Target APIs as Power Platform ConnectorInvestigating

Description -Integrate Target Admin APIs (and potentially all Target APIs) into Microsoft's Power Platform as a Connector: Integrate your service with Microsoft products and services | Microsoft LearnWhy is this feature important to you -Low/No Code solution to assist with automating workflow and reporting of Target- consistent with Target's approach to simplify experimentation access via a low/no code platform. How would you like the feature to work -Target Admin APIs (and potentially all Target APIs) are available as Certified Connectors published by Adobe into PowerPlatform- this is consistent with other Adobe Product integrations available today as connectors: Microsoft Power Platform and Adobe integrations | Microsoft Learn - List of available Adobe Connectors in Power Platform (Updated 2023); Adobe Experience Manager - Connectors | Microsoft Learn - AEM Connector (Not mentioned in above link)Current Behavior -Any automation or even basic reporting needs that have to happen outside of the Adobe Target Web UI require a developer to build a postman connection & run an API. Extensibility of the Target platform is limited to those with developer resources & time- something as simple as sending a notification when an activity has been live for more than 90 days has to be done manually or through extensive development & custom integration.