Skip to main content

Filter by idea status

10000+ Ideas

gkalyan
gkalyanLevel 1

Intelligent Content Recommendations: Driving Engagement and Business Outcomes in AEM SitesNew

Request for Feature Enhancement (RFE) Summary: Implement an intelligent content recommendation engine to leverage AI and machine learning to suggest relevant content for each page, driving increased engagement and business outcomes. Use-case: Marketers need a way to deliver the most relevant and engaging content to users based on their behavior, interests, and the current context. By providing AI-powered content recommendations, AEM Sites can help surface the most impactful content to drive conversions and achieve business goals. Current/Experienced Behavior: Currently, marketers must manually curate and select content for each page, which can be time-consuming and may not always align with user preferences. There is no automated way to surface top-performing content or make recommendations based on user behavior and business rules. Improved/Expected Behavior: With the intelligent content recommendation engine, AEM Sites would analyze user interactions, content performance metrics, and contextual data to suggest the most relevant content for each page. Marketers could set business rules to prioritize certain content types or topics, and track the engagement and revenue impact of AI-recommended content. The system would learn and optimize recommendations over time based on user interactions, providing valuable insights to marketers on content performance and opportunities for improvement.   Environment Details (AEM version/service pack, any other specifics if applicable): AEM + Adobe Experience Platform + RT CDP Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

konstantyn_diachenko
konstantyn_diachenkoNew Participant

Add optional description/note for Cloud Manager Environment VariablesNew

Request for Feature Enhancement (RFE) Summary: Environment variables is a good feature in AEMaaCS to change OSGi service configuration in runtime without redeployment. Sometimes, project has to have a lot of env variables, especially if you are running several sites on the same program. That's why I would like to have an option to set a description or note for env variable in the Environment Configuration modal in Cloud Manager.   Use-case: I can provide few use cases: 1. Imagine you have 2 brand that are running on AEMaaCS. Each of them should pull data from third-party service by schedule. Sometimes there are cases when you need to change a frequency for pulling data for both services or service URL. For example: BRAND1_SERVICE_URL is an env variable with a 3rd party service URL to provide data for brand1, BRAND2_SERVICE_URL is an env variable with a 3rd party service URL to provide data for brand2, BRAND1_SERVICE_CRON is an env variable with a cron expression for brand1 service, BRAND2_SERVICE_CRON is an env variable with a cron expression for brand2 service. I would like to provide some notes for like "3rd-party service for brand 1. Example: https://api.service1.con/api/v1 " or "Every 5 hours: 0 0 */5 * * ? | Every 5 mins: 0 */5 * * * ?". 2. When you need to follow concept of secrets rotation (like for CDN: CDN_PURGEKEY_081324, CDN_PURGEKEY_111324) you can forget about last changed key even if you named it using data format. Some description or note for env variable might help to provide more clarity.  Current/Experienced Behavior: Currently such option is absent. Improved/Expected Behavior: -  Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager Environment Configuration flow Customer-name/Organization name:   Screenshot (if applicable): Example of the idea how to render it:   Code package (if applicable):  

PollyCoLevel 9

Audit log passed on by Adobe Admin Console to Workfront should display as actioned by the correct administratorNew

The current state is that we have to create users first on Adobe Admin Console in order to control that the user will be created as Federated ID. Unfortunately, one of the many disappointing things about Adobe Admin Console is that it can randomly create the user as Federated ID or Adobe ID if the user creation originates from Workfront. As we were also forced into Adobe Admin Console and there is already an Adobe Admin Console Systems administrator, we can only get Product Administrator access levels on Adobe Admin Console which does not provide access to the logs. The problem occurs in that when other product administrator or the Adobe Admin Console Systems Administrator creates/deletes a user on Adobe Admin Console, these appear as if actioned by the main Workfront systems administrator in the workfront logs which becomes an audit issue. We can't refer to the Adobe Admin Console logs quickly as that would require requesting from the Adobe Admin Console systems administrator every time we need to figure out a user creation/deletion log. While Adobe is aware that this is an issue and they are looking to rename the log to say system administrator in the long run, there is no ETA on this fix. I am writing this Idea to get this bug(!)/feature fixed as I don't understand how this is acceptable as an audit issue. 

Feature Request: Blueprints Sharing Across Workfront InstancesNew

DescriptionI would like to have the ability to create blueprints of objects within my Workfront instance that can be easily shared with other sister agencies. For example, instead of exporting project templates as Excel files and emailing them for manual recreation, I would like to share 2-4 project templates as blueprints that can be directly imported into another Workfront instance.Why is this feature important?This feature is crucial because it significantly reduces time and effort, increasing efficiency and productivity. It eliminates repetitive manual processes and ensures consistency across instances, fostering better collaboration between teams and agencies.How should the feature work?Workfront could introduce a dedicated "Share" section within Blueprints that allows users to:Select project templates, including associated custom forms, assignments, predecessors, and constraints, to compile into a blueprint.Export the blueprint as a file that can be shared externally.Import the blueprint into another Workfront instance, where the recipient can:Open the blueprint in their Blueprints section.Adjust assignments, custom form fields, and other configurations as needed.Save the blueprint as a project template within their instance.This streamlined workflow would empower teams to collaborate more effectively while preserving template integrity.Current BehaviorCurrently, I need to manually export project templates as Excel files, email them to the recipient, and have them:Copy and paste task names into their instance.Manually recreate assignments, predecessors, constraints, and custom forms from scratch.This process is time-consuming, error-prone, and inefficient.

Feature Request: Convert Paragraph Custom Field to Text Field with FormattingNew

DescriptionEnable the ability to convert a Paragraph custom field into a Text with Formatting field. This functionality would provide users with the flexibility to copy and paste formatted text from other applications and format requirements directly within Workfront using bullets, numbering, bold text, etc.Why is this feature important?This feature enhances user efficiency and maintains consistency within the Workfront instance by:Allowing users to format project requirements or other data directly in the field, reducing reliance on external tools.Eliminating the need to create duplicate fields just to add formatting capabilities, saving time and minimizing administrative overhead.Retaining existing custom fields without requiring redundant work to migrate data to newly created fields.How should the feature work?Within the Custom Form Builder:Click on an existing Paragraph custom field.In the field properties/attributes, navigate to the Display Type dropdown.Change the field type from Paragraph Text Field to Text Field with Formatting.Upon conversion, Workfront should:Preserve all existing live data as plain text (i.e., no formatting will be applied retroactively).Allow new data to utilize the formatting options available in Text Field with Formatting.This streamlined approach avoids data loss while expanding formatting capabilities for future entries. (See attachment for a dropdown screenshot.)Current BehaviorCurrently, this functionality does not exist. Users must create a new Text Field with Formatting, manually migrate data, and delete the original Paragraph field—an inefficient and time-consuming process.

brentradLevel 5

Allow date-time data types to work with filter operatorsNew

DescriptionIn Customer Journey Analytics, dimensions can be configured to use a date-time schema data type. For example, a dimension showing when a product was added to wishlist could use this data type. Despite dates being akin to numbers, they cannot be used with greater than and less than operators in fitlers. The recommendation is to allow for this type of functionality. Why is this feature important to youAllowing the use of operators on dimensions that use a date-time data type would be useful for filter creation. For example, let's say that a user wanted to see a list of customer IDs that added a product to a wishlist between September 20, 2023, and October 20, 2023. A dimension exists that captures the date that a product was added to a wishlist (Dimension 1), and the dimension's values are in date-time format. If filter operators worked with date-time dimensions, the user could build a filter with logic similar to "greater than or equal to Dimension 1 = Sep 20, 2023, and less than or equal to Dimension 1 = Oct 20, 2023". Currently, the user would have to list out 31 different dimension values to cover each of the dates from Sep 20, 2023, and Oct 20, 2023. How would you like the feature to workTreat dimension values with a date-time data type as numbers, which will allow greater than, less than, etc. operators to be used. Current BehaviourDimensions with date-time data types do not currently work with operators.