Build better products with our product team
Please let us add screenshots to comments or updates, as in JIRA. These images do not need to be revision-controlled, like a document, but we need to be able to easily share images within the team, and would prefer to stop using email or OneNote for this purpose.
Description - Currently, Workfront cancels automatic resource leveling anytime more than one person is assigned to a task. However, all of the information needed to execute this effectively (e.g., allocation percentages/hours, etc.) is present in Workfront. In many cases, automatic resource leveling is a critical feature because it automatically takes care of numerous, very complicated timeline adjustments that are difficult or impossible to do manually. However, it is unusable in the very common scenario where there are multiple assignees. This idea is to request that resource leveling is not canceled with multiple assignees. I would throw in there also that resource leveling be compatible with the Effort Driven duration type and any other features it is currently not compatible with. Why is this feature important to you - In many cases, automatic resource leveling is a critical feature because it automatically takes care of numerous, very complicated timeline adjustments that are difficult or impossible to do manually. However, it is unusable in the very common scenario where there are multiple assignees.How would you like the feature to work -This idea is to request that resource leveling is not canceled with multiple assignees. I would throw in there also that resource leveling be compatible with the Effort Driven duration type and any other features it is currently not compatible with. No UI changes would be necessary as far as I can see.Current Behaviour - Currently, Workfront cancels automatic resource leveling anytime more than one person is assigned to a task. However, all of the information needed to execute this effectively (e.g., allocation percentages/hours, etc.) is present in Workfront.
Hello All,Profile scripts are code snippets defined within Target using a form of server-side JavaScript. Using Profile Script we're targeting Visitors based on their behavioral information/segment filtering. For Our Client we have created many Profile Scripts to target visitors based on visitor behavior across site. Few times i had mistakenly edited/modified the profile script which is in LIVE and it affected many activities which is in LIVE, for resolving this i had contacted Customer service and they provided me the previous version of script by checking the Adobe Target Server Splunk Log and it took very long time to resolve this and also we can't always do the same to resolve this and few times i had developed the code again from the scratch since those are High Priority Activities. For Avoiding this i'm strongly Suggesting/Recommending here to Add/Include Version/Revision feature to Profile Scripts.Thanks,Charles
Would be useful to get a sense of time spent on our proofs by licensed (Work or greater) and for that time to roll up to the project it is attached. This should be in a way simpler than managing the proof plus the separate task. It should also improve the time tracking for proofs and where it is being applied within the job for better insights into this ongoing pain point. Let me know if I need to rewrite this to be clearer.
We'd like to have an option in Workfront Fusion to send repeated notifications when a Scenario is made inactive by Workfront Fusion because a connection is no longer valid. When a Scenario is made inactive through the Workfront Fusion platform at this time we may receive one notification that the scenario was set to inactive by Fusion. We encountered a situation recently where a notification was not sent due to a connection error and caused a Fusion Scenario to be down for an extended amount of time. Having the ability to send repeated notifications would ensure minimal downtime the next time a connection is severed unexpectedly.
Request for Feature Enhancement (RFE) Summary: This request is about the Content Transfer Tool, which can be improved for insufficient disk cases. Use-case: AMS instance with the S3 Data Store has been prepared for the very first initial extraction. Extraction started with about 400GB asset content. After about 1 hour, it failed. The logs forwarded to the Adobe Support. They noticed the following statement on top of the output.log, see attached zip file : Check Size results: Migration Set size: 381.247 GB Node store size: 2.202 GB Data store size: 379.045 GB Node count: 20,764,479 Free disk space (crx-quickstart dir): 24.398 GB You do not have enough disk space in the crx-quickstart subdirectory of the source AEM instance to perform this extraction. You need to increase disk space by 51.486 GB or reduce the migration set size. Current/Experienced Behavior: CTT tried to run all extraction steps, until a failure occurred for the obvious root cause. Improved/Expected Behavior: The error gets logged with the prefix ERROR and the extraction halts immediately. Environment Details (AEM version/service pack, any other specifics if applicable): AMS Author - 6.5.19. CTT Version : 3.0.10 Customer-name/Organization name: Volkswagen Group Screenshot (if applicable): Code package (if applicable):
Description - Ability to notify when an audience activation (dataflow) expires. Why is this feature important to you - Currently when a segment has been activated to a destination there is an end date placed upon the activation. When the end date of the activation dataflow a notification is not present to the CDP system and or user who has setup the activation.How would you like the feature to work - Before the dataflow is end date of the audience is set to expire, please send out a notification via alert and or email notifications.Current Behaviour - An audience can be activated to a batch destination, but an end date is specified. There is not an ability to be notified when an dataflow activation is in range of its end date.
Description - I would love to able to set a name as well as a label for sectionsWhy is this feature important to you - This would help to be able to differentiate between sections used in different contexts. Sometimes the name of a section repeats itself what is technically not possible to set up, as it has to be unique. I would prefer an (internal) name, which acts as the unique "primary key".I know, that I can use sections in multiple custom forms, but as described, would like to be able to have more flexibility here. If I use a label in more than one custom form, I am not able to modify the label later only for one custom form without needing to create a new section with the new label name.How would you like the feature to work - Similar to custom fields, where we have a name, which is used internally and a label, which is the display name.Current Behaviour - Only unique display names possible
Description - Would like for the Awaiting My Approval area to be a scroll list like the legacy home is/was versus clicking through pages to see proofsWhy is this feature important to you - This is a concern that users can only see 5 proofs per page and have to continue to click through the pages to see more proofs. This is concerning as we sometimes have projects that have 10+ proofs at the same time and this could leave the door open for users to miss proofs that went to that same project if they are falling onto the next page.How would you like the feature to work - Would like to have scrolling like Legacy Home offered to remove the clicks from users and possible room for users to miss reviewing proofs for projects when there are more than 5+ proofsCurrent Behaviour - Does not exist
Description - Please add the functionality to MANAGE TAGs just like we currently have the ability to manage any number of other Components: Why is this feature important to you - Tags are spread out over MULTIPLE components and can exist in many different incarnations as they can be created by different people. The purpose of Tags is to make searches easier, but if we have the ability to manage them from a central location, we can then standardize and improve them for easier searches and optimize the use of our components and Workspaces. How would you like the feature to work - Just like we can currently manage other components, we need a page for Tags, but in this case, provide filters for all of the relevant Components off to the side.Example:FIRST provide the ability to see ALL tags, listed in ALPHABETICAL order, and then provide a summary of all components they are associated with.It should be possible for us to click on any Tag to view it individually and see every component associated with that tag.We should be able to edit a tag if we open it. For instance, if a tag has been in existence as ALL CAPS, we can rewrite it as lowercase and save it so that it is updated as lowercase across ALL components with which it is associated.This should be an ADMIN-level only functionality. Current Behavior - There is currently no decent way to edit or manage Tags en masse. The only way I have found that works in any kind of fairly decent manner is to select a number of components, and then choose Component Actions, click Tag, and then I can either Edit or Add tags. from that point. OR
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK