Skip to main content

Filter by idea status

10000+ Ideas

vmengiEmployee

Provision to Link Issue Type Object With Workfront Planning RecordNew

Description - The idea proposed is to help seamlessly connect the Issue object type with Workfront Planning records. This integration would offer a more intuitive and traceable workflow from the moment a campaign request is raised. Currently, campaign planning and execution can be fragmented, especially when the original request (issue) becomes disconnected from subsequent project records. By establishing a direct connection between the issue and the planning record—using relevant lookup fields—we enable requestors and stakeholders to get a comprehensive, real-time view of the campaign's progress. Why is this feature important to you - Campaigns often start as requests (issues) — linking them with planning records creates a seamless flow. Enables complete visibility of campaign status from request to execution. Lookup fields can show real-time progress to requestors and stakeholders. When an issue is converted to a project, the planning data remains connected — ensuring continuity. Supports better reporting: track campaign lifecycle, turnaround time, and request insights.   How would you like the feature to work - 1. Enable the ability to connect Planning record to an Issue object type 2.Have lookup fields related to Issue to have a comprehensive view 3.Have an option to display Resolve Project details Current Behavior -  Currently, there is no native provision to connect an Issue with a Planning record in Workfront Core. If there is a need to display the related request, it must be achieved through Workfront Fusion. The main challenge arises when attempting to populate the Issue link manually in Planning—since there is no option to make fields non-editable within Planning records, users may accidentally manipulate or overwrite the data, leading to inconsistencies and tracking issues.   @deekshapai @venkat_suren 

CJA Stitching(FBS/GBS) Visibility into Lookback Window, Replay Settings, and Scheduled RunsNew

Description -This feature would introduce a new settings panel within the CJA interface for stitched(FBS/GBS) datasets. This panel would provide clear visibility into the configuration and schedule of the stitching process, including the lookback window, replay settings, and the timing of data processing runs. Why is this feature important to you -Data accuracy and trust are fundamental to our analytics practice. Without knowing when the CJA dataset was last stitched or what lookback window was used, our stakeholders cannot be confident about which day of the week contains the most complete and accurate data. This ambiguity undermines our ability to make timely, data-driven decisions. It also creates an unnecessary dependency on the Adobe support team for basic information about our own data configuration. How would you like the feature to work -Within the CJA Data View settings, there should be a new tab or section dedicated to "Stitching Configuration". This section should clearly display:Lookback Window: The currently configured lookback window setting (e.g., 7 days, 30 days).Replay Setting: The status or configuration of the replay setting.Last Run Timestamp: The exact date and time of the last successful stitching run.Next Scheduled Run: The date and time for the next planned stitching run.Ideally, this feature would also evolve to allow administrators to not only view but also configure these settings directly within the UI, moving it from a "black box" to a self-service model. Current Behaviour -Currently, the configuration of the lookback window and replay settings for stitched datasets is a black box, managed entirely by the Adobe support team. There is no visibility within the CJA platform to see what these settings are, nor is there a way to know when the next stitching process is scheduled to run. This lack of transparency forces us to guess when the data is most accurate and requires us to go through support for any changes or information.

PolinaAbNew Participant

Add an ability to "Replace a file" from the asset's properties pageInvestigating

Request for Feature Enhancement (RFE) Summary: Content managers need an ability to "Replace a file" from the asset's properties. We implemented an override for them (pictures attached). In future we'd like to have this feature as Out-of-the-box functionality. Use-case: Content manager creates an asset's language copy, then "Reveal in Asset", then goes to the asset's properties and need to Replace the original file by translated version of file, having stored it on local computer with different name. Current/Experienced Behavior: Content manager can update an asset's file by one of the 2 ways: Create a Version: Open the folder in the DAM. Find his/her asset file. Select it and click on the "+ Create" button, then select "Version" button. Replace an original file OR Create a version:Save a future image with the SAME name as an original asset's file in the DAM. Drag and drop the future image to the DAM. System suggests "Create a version" or "Replace". Improved/Expected Behavior: User Story: As a Content manager, I want to be able to "Replace a file" from the asset's properties to avoid walking through assets listing and files renaming.   Acceptance criteria: Content manager can update an asset's file from the asset's properties by uploading the file from his/her local computer. Content manager can choose 2 options: "Create version" or "Replace". If "Replace" option is selected, AEM saves the file to the same directory and automatically rename uploaded file to the same name as the original asset (original file is deleted). If "Create version" option is selected, AEM creates a version of the file (original file is saved). Uploading file with different extension than original asset is not uploaded and the error is displayed. The button "Replace file" is displayed on menu above asset properties page. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Managed Services, v6.5.14 Customer-name/Organization name: Veeam Software Screenshot (if applicable): We implemented an override for Content managers: Code package (if applicable):