Build better products with our product team
Description -Currently, we only have the name of a Data Element or Rule to describe them. Notes are helpful for changes to an item but are not immediately visible from both the list and detail screens.Why is this feature important to you -Because I like to know what a thing does without having to look into it first. Also because it helps communicate functionality to others.How would you like the feature to work -Have a description field next or below the name of a Rule or Data Element in the detail screen. If an item has a description, show a little i-icon on the overview page that, upon hovering over it, shows the description as an overlay (like a tooltip).Current Behaviour -😭
Description -In Analysis Workspace there is the ability to 'tag' segments, calculated metrics, workspaces etc. works brilliantly making searching, filtering and organising easier. It seems like such an obvious thing to introduce the same capability into Adobe Launch so we can tag Data Elements, Rules and maybe even Properties.Why is this feature important to you -Organisation of all the data elements and rules we have would be a lot easier if we could use tags.How would you like the feature to work -Ability to add tags to data elements/rules to enable us to search by tags much the same as the functionality in Analysis WorkspaceCurrent Behaviour -Without tags we have been forced to try to add additional information to the names of data elements/rules to make them searchable. This is far from ideal as it makes the name unwieldy and they can't contain all the information we need. In addition you can't change the name of data elements without breaking stuff so you only get one chance to get the info you need into the name or you have a lot of work to do to change it.
In a custom email template, it would be handy to have a limited set of values for the "mktoColor" variable (represented by a drop-down list of a palette). Most brand guidelines only allow for a certain set of colors to be used. Currently, each person in charge of emails has to either look these colors up every time they build an email, or remember the hex color codes. Both of those are becoming not very practical as the volume of work grows, new team members get hired, or the guidelines change. Having a limited palette would not only save teams time and effort, but also guarantee against accidental use of off-brand colors. Attaching an example from another app.
Hello, A few months ago Adobe added the hour level of granularity in the Workspace calendar widget. It's really annoying when all I want is the end date (full day) because now I have change the end hour from 12:00am to 11:59pm (previously the end day defaulted to 11:59pm). Does anyone know if a fix is being worked on? Thanks. -Peter
Description - A request to expose the current loaded Adobe library path in the _satellite object. Why is this feature important to you - Our organization is transitioning over from different Tag Management System to Adobe Launch. There is a need to track the path of the loaded TMS URL path in a prop. Our team is responsible to verify that the Developers load the appropriate Launch URL in Development/Staging and Production environment whenever a new web page is created. So we track this path in a prop on the Adobe Analytics reports and set alerts if something goes wrong. How would you like the feature to work - Have the full path of the current loaded library in the _satellite.environment object. Also to have a new key which says if the Adobe Launch is using self-hosting or Akamai. Current Behaviour -Current _satellite object has the environment object which holds the type of environment, but it does not contain the path of the the Launch library loaded.
Request for Feature Enhancement (RFE) Summary: AEM Assets - When using the Filter rail to search, it should only display matching assets. Use-case: Using the Filter rail, with a Property Predicate set up, adding a keyword to that field should make it so the filter only returns assets that have that value in the configured metadata field. Current/Experienced Behavior: Search returns all assets that contain said keyword in any metadata property Improved/Expected Behavior: Search returns all assets that contain said keyword in the metadata property configured in the Property Predicate Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Service Pack 8 Customer-name/Organization name: The Raymond Corporation Screenshot (if applicable): Code package (if applicable): N/A Notes: This feels like a bug to me, and certainly not a "new idea", but we opened Support Ticket E-000488914 and were told to file a "feature enhancement request".
We use the method documented to implement External Page Prefill however this method is dependent on the munchkin cookie which means that if we wish to implement prefill a user also has to accept that they will be tracked. Would it be possible to somehow separate the functional use of this cookie (i.e. for pre-fill) from the marketing (i.e. tracking) behaviours. Perhaps via a use of a separate cookie or by some for of cookieless solution?
Right now if you have a combined proof and 1 file is static and 1 is a video or gif, the animated/movie file won't work. Combined proofs should allow for interactive and static files, this defeats the functionality of being able to upload more than 1 file in a proof!
Keeping the browser zoomed always to 100% is not feasible. When projecting Workfront to a large room of people, no one can read what is in Workfront in the back.
Just like you can view who uploaded a document and when in update feeds, we'd like to have the ability to see who downloaded a document and when. We need to see who downloaded documents sometimes for confidentiality reasons.
A lot of companies are using Google for their email and calendars in 2021 and it is critical that "Add to Calendar" functionality is added as an out of the box functionality for webinars. If a "Add to Calendar" token can be created for Google that will include the {member.webinarURL} token it would be a huge step forward as I find it hard to believe that this doesn't exist today.
When trying to generate a proof from a file in Google suite, we need to use the interactive setting. This prompts the user to download Workfront Proof tool., and then log in to Google suite every time they want to review the proof which leads to a poor user experience. We would like to see the google suite being a supported file format of proofing which should hopefully remove the problem of seeing a 'login screen' when using a static page or downloading the software to use an interactive screen.
Description - In case if you need to disabled the extension for some reason, there is option to disable and once you clicked on that action there is no choice to revert back. Why is this feature important to you Because if we have multiple extensions installed in your property and by mistake you disable the wrong extension then there is no way to cancel. How would you like the feature to work -Have a Cancel button next to OK button so that user can cancel the action and return back to Installed extension screen. Current Behaviour -
The documented default for Proof is to send a daily summary of comments. For users managing dozens of proofs at a time, this is bogging down their email. I think there are a variety of ways to customize this experience: allow the user to set defaults for when comments come in, decisions are made, or they're mentioned. Related: It would help if the admin could set or even lock defaults for the above options based on access level.
ProofHQ currently can not view content in PDF "Sticky Notes" comments. Our clients often send us PDFs riddled with them, from multiple reviewers. It would be great to be able to see them by default, much like how you can see comments and changes in Track Changes view in MS Word.
Description - Currently CDF logs gives us the legacy segment IDs and to check for any segment, it involves login into AAM UI and then back the trace each of the segment to know whether it was realized or not. This take a lot of effort to do back tracing a legacy ID from multiple segments.Why is this feature important to you - Having segment IDs in the CDF which ease the job for end users who are utilizing these logs for data tracing. With segmentID in the file, one can directly check whether a segment was came in fine or not.How would you like the feature to work - Just replace legacy ID with segment ID.Current Behaviour - Currently legacy ID being exported in CDF logs.
I would like a way to edit planned hours at the assignment level:task > multiple assignees > different hours per assigneePM = 1hrDev = .5hrNow the scope changes and we need to double the timePM = 2hrDev = 1hrIf I just double the planned hours at the task, Workfront simply divides the planned hours evenly across assignees.For a PM who runs several projects, on a client that causes such shifts at least once a week , doing this currently in WF is super time consuming - in list view everything' would be right there and editable. The workaround easily doubles if not triples time spent on this I am looking for an efficient way to edit allocation on a task, something like this:
I have lost hours of work over time using workspaces due to not remembering to press save, after having my attention pulled onto something else. Sometimes workspace tries to accommodate this with its unsaved changes prompt, sort of a 'pick up where you left off' feature, but it doesn't save everything. Just yesterday I lost about 2 hours of work.An autosave feature saving every few minutes, or after every action, would save significant time. I'm thinking along the lines of cloud services such as Google and Microsoft documents, which cloud save constantly.I imagine there are resource and usability implications to this, though I would happily accept a second or two of sluggishness now and again to prevent loss of work.Where a workspace is saved with a name, the autosave would save against the named project.Where a draft is being worked on, it could be autosaved into a drafts category.And to throw in some idea creep, perhaps we could get version history added along with this.
Group Admins can currently build custom Layout Templates.We would like an option to disable this functionality.This allows us to control Layout Templates at a central level.
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