Build better products with our product team
Deactivate the following two hotkeys when the Edit description mode is active. They are default ones for jumping between words. alt + Right Key (Move to next panel)alt + Left Key (Move to previous panel)
Because I’m the owner of a large handful of projects, I get a ton of emails every morning about updates. An email for each object in the system (tasks, requests I submitted and received, projects, etc.).If the digest emails were setup to send as one email with sections for each item, it would be more manageable to digest the information and less intensive on the email front.
Analysis Workspace provides a built-in "Days Since Last Visit" dimension. However, this is at a granular "day" level. In some visualisations, it would be more useful to see this by buckets, e.g. "same day", "less than 3 days", "less than 30 days", etc. Since this dimension cannot be classified (using Classification Import or Classification Rule Builder), it would be good if Adobe can create a "Days Since Last Visit Bucketed" dimension to support visualisations that don't need granular per-day values.
With the latest Update in Salesforce Sales Cloud Spring '20, tasks can finally get assigned to Lead Queues: Please implement necessary Changes to leverage thisSales Owners field should also pull in Lead Queue info, or reference in some other way.e.g: Sales/Lead Owner First Name = "Lead Queue"; Sales/Lead Owner Last Name = "actual sfdc queue name" or at least pull in the queue email into the Sales/Lead Owner Email field so they can be referencedTasks should be assignable to Lead Queues as well, not only usersRelease Not Update FYR:https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_sales_productivity_activities_task_queues.htm
We are unable to optimize search results as in document search returns so many results. If we could turn this off, and allow users to turn on and off as required, this would allow us to optimize but also give users the ability to broaden their search if they cant find what they are looking for, searching ony metadata field values.
From a quality and compliance standpoint, admins should be able to restrict the ability for certain user roles to press (or even see) the "Edit Code" button in the Email editor.
We have a large number of forms that have multiple sections of fields that must be on them for reporting purposes. One section at the top for user input and one section at the bottom for calculations and form metadata. These are a couple examples, but some forms have many more.Right now, I have to open a form in a separate window and use that to compare side by side as I create a new form.It would be nice to have sections or groups that can be preset so when I create a new form, I can add the section/group and the fields will pop in automatically with the same settings (required, calculations, logic, etc.). From there I can add addition fields as needed.
I decided to contribute a write up for creating aggregated metrics, given a couple of issues I found with common use cases: Comparing metrics over time in Analysis Workspace provides a visualization of non-aggregated trend lines.Using the Summary Change visualization will provide a calculation of deltas that is not apples-to-apples, but instead comparing a partial day’s figures against another day’s aggregated total.Using Time-parting for Aggregated Metrics in Analysis Workspace Let me know if you have any questions, or feedback. Thanks.
Ability for a user to delete a project ONLY if the user created a project.
It would be very helpful if we can mark a special announcement or update within a project. People are receiving notifications, but because all updates look the same they are not noticing if/when there’s a critical update on a project.
It would add a very useful additional layer of flexibility if the Adobe Analytics extension allowed you to add a condition against the variable you were setting (dare I say it, similar to processing rules! 😅) At the moment if I want to conditionally set a variable (e.g. an eVar) I either have to have a completely separate rule or I have to use custom code within the action both of which are a compromise for different reasons.
The auto detection of download and exit links provided by the Adobe Analytics appMeasurement.js is useful. However, it would make far more sense to me if these were events provided by the core extension. The benefit would be we would be able to:make the way these events are handled consistent with everything else we are doing (i.e. managing what happens through Launch rules rather than hacking stuff together using doPlugins)make these events available as a trigger event for other capabilities implemented through Adobe Launch (i.e. rather than just being an Adobe Analytics thing)
Currently, running a report as an admin will actually only apply to the results of the report and not to the prompts of the report. The purpose of this Idea is to allow the Prompt Feature of a report to run according to the reports access settings. For instance, if the report is supposed to be run with the access rights of a sys admin, then the users with whom the report is shared should be allowed to adjust prompts as if they were at the Sys Admin level. Otherwise, the access levels of the users running the report need to be upgraded to Sys Admin access to be able to use the Prompt functionality to run the report. Thank you.
We'd like to map one field (regardless of what object type it's on) to one field in the DAMWe currently have one custom field that is used on both issues and tasks - we'd like to be able to map it from Workfront to the DAM's Keywords field. But unfortunately, when you select the field from the Workfront side, you have to indicate the object type it's on.
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