I would like to propose changing the default functionality of recalling an issue or request that has a pending approval status. It would be even better to have the ability to customize the behavior at the system level, but any improvements would be appreciated. In current state, when a user submits an issue or request that has an approval process, they have the ability to Recall the issue while it is still pending approval. When the Recall button/icon is selected the issue is deleted and sent to the recycle bin. Because these recalled issues are deleted, we are unable to keep a record of the need and users are unable to refer to the information that was included. We find that users who need to recall an issue need to either cancel it due to some change, or they need to revise it before initiating approvals. In either case, we would like to retain a record of the recalled issue, as well as have the ability to copy or resubmit it. Ideally, we would have the option to customize the behavior of the Recall functionality at the system level. This would be similar to the functionality in approval processes that allow you to select a status for rejected work items, i.e. if rejected change to status XYZ. However, if the default functionality of Recall was to "revert to draft" rather than delete, we could easily create our own process to change the status manually.
Description - Add the ability to bulk update the recipient list for Alerts Why is this feature important to you - It reduces time when needing to bulk update Alerts to send to specific users. How would you like the feature to work - After selecting the specific Alerts in the Alerts UI, it would be nice to have a 'Share' button (similar to how sharing Segments works) so you can add users to receive Alert emails. Current Behaviour - Currently this is a very manual effort to add additional users to an Alert after creating. If there are 100 Analytics Alerts and you get requested to add 1 person to receive those alerts, you have to edit each Alert to manually add the user to it.
Request for Feature Enhancement (RFE) Summary: Request for a separate column for each CQ tag group (Devices, Keywords, Symptoms, etc) when generating an Export Metadata report. Use-case: 1. Select multiple assets in AEM Assets UI.2. From the top menu, click 'Export Metadata'.3. Enter the export details then click 'Export'.4. When the report generation is completed, download the report (CSV Download). Current/Experienced Behavior: All the cq tags are for an asset are listed in a single column (see attached screenshot). Improved/Expected Behavior: Each cq tag group (Devices, Keywords, Symptoms, etc) is listed in a separate column. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.12 ; AEM Guide 4.1 Customer-name/Organization name: Verizon Screenshot (if applicable): Uploaded Code package (if applicable):
We have reports that we set up to send daily for a short period of time each quarter.We'd like to be able to select "Weekday" instead of daily, our users don't generally need these reports over the weekend.Also, to expand on that, it would be amazing to be able to set up a repeating deliver for example, every weekday, for 2 weeks, beginning the 3rd week of each quarter -- this one may be a bit of a stretch request, but a dreamer can dream!
Any reports that are set up within a program of course are meant to report on that program specifically. When cloning a program, reports that are set up directly under the program itself are updated automatically. However, when you apply some housekeeping on more complex programs and put reports into a subfolder, the updating of this reference to the cloned program no longer happens. It would save a lot of manual work if this would also be updated automatically.
It's great that so many people helped with the re-ordering of Progressive Profiling fields though Javascript. But why is not possible to just drag & drop the whole section on the form editor? Nobody wants their ProgPro fields underneath an opt in box.
Description - Need a way to ingest data at profile level from Edge Server API Why is this feature important to you - next best action, edge segmentation How would you like the feature to work - Be able to update the profile attributes in AEP so that segment conditions can be simplified so that it can qualify for Edge Behavior. Alternatively, support sequence events conditions for Edge. Current Behaviour - It's supported only for Events.
Would allow the viewer to quickly reference where in the timeline the task is. Especially when there are multiples of the same task. This would be most helpful to be shown somewhere in the header/chrome.
Due to my company's cloud structure, the IT team isn't able to install the encrypted Workfront InDesign Plugin that is available in the Creative Cloud, they need an unencrypted version to be able to install that plugin on our sessions. I don't know if other companies face this same issue, but we would love to be able to utilize this plugin in an effort to create more efficiencies, we just can't with the file that is currently available on the Creative Cloud.
To extend the idea provided at "Add additional usage data for bulk API queries", handling bulk API data should be adjusted to understand datacenter locales as well. As an example, if you were looking to set up API extractions after a daily API limit is passed, knowing where the datacenter is helps integration providers understand when, exactly, an API limit will reset. Would it be possible to get AB, SJ, E, NL, SN, etc. passed as a result to calls like usage.json, or could we get a generic instance metadata call to provide information like this?
Note: this isn't limited to Analytics, but Adobe's Documentation Infrastructure as a whole. Description - While this may be hard to go back in time to achieve, I have seen a number of complaints and felt the pain myself... Either bookmarking something I would use frequently, like the Raw Data Column Reference (which has been moved about 4 times), or finding old links in Experience League... Many of the old posts still offer a wealth of information; but they are lessened by the fact that half the reference links are broken. Why is this feature important to you - We all rely on documentation, and being able to find that documentation quickly and easily is of utmost importance. Adobe being such a long running company, it's understandable that the documentation would move from place to place... what is not understandable is why basic functionality like using 301 redirects to keep all the varied in-links functional was skipped. How would you like the feature to work - When moving documents, ensure that proper 301 redirects are in place to make sure users end up in the correct location. Review all your 404 pages and make sure that old documentation links have 301 directs created for them to try and fix all the lost value that exists in the Experience League and other resources aimed at supporting the Adobe Community as a whole. Current Behaviour - So much history has been lost over the years due to document migrations that didn't include proper 301 redirects...
- This feature should be consider important and it should be created inside Adobe Analytics - Server calls usage. - We need to track Video calls, Starts or Media Streams. At the moment it seems that Adobe has not added this feature yet into the platform or future Roadmaps. - This feature gives more usage visibility to all users of Analytics in order to improve their adoption, usage, strategy for the future and avoid any over usage invoices
Description - Show the overall percent complete a portfolio is based on how far along the projects within that portfolio are. Why is this feature important to you - We have enterprise wide campaigns that consist of several projects. We put these projects into a portfolio to track how that campaign is going. It would great to see how much of that campaign is complete by showing the percentage complete for that portfolio. How would you like the feature to work - If a portfolio has 10 projects in it, and two are 100% complete and one is at 50% complete, then the portfolio would show that it's overall completion percent is 25% complete. This could be shown in the portfolio optimization page at the top, or be a filter when creating portfolio report. Current Behaviour - No option exists to track percent complete of a portfolio.
Request for Feature Enhancement (RFE) Summary: This is a request to add a functionality to be able to generate a list recently modified dita topics and be to choose the topics (from the list) to generate output for. Use-case: Current/Experienced Behavior: Improved/Expected Behavior: Ability to identify recently updated topics and chose which ones to generate output for. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.512 ; AEM Guides 4.1 Customer-name/Organization name: Verizon Screenshot (if applicable): Code package (if applicable):
In light of the latest discontinuation notice informing that Adobe will be ending the services of "Reports and Analytics" section including all of its exclusive metrics and reports, and replacing it with Workspace, we'll be losing one of the metrics which is of an utmost importance to our daily analytical tasks, and also important to other markets, which is "Monthly Unique Visitors" metric. What makes this metric very essential is being able to breakdown the monthly active base across the month's days, in order to identify which users have appeared for the first time in exactly which day of the month.It'd be great if Adobe can either retain their metric somehow, and replicate it to be used in Workspace, due to its great importance. Also, my question is, is there a work-around to calculate this metric under custom metrics? Thanks.
The ability to turn on/off various layers present on an Adobe Workfront file aka the uploaded PDF. While reviewing a document it would be invaluable to be able to turn on various layers in Workfront, those layers can indicate PMS colors, special effects, etc. A simple layers palette similar to Acrobat would be the easiest and most direct solution as users would be most familiar with that approach. Currently there is no layer access in Adobe Workfront.
Description - Allow calculated field values to populate list of same field that can be used for drop down. Why is this feature important to you - I want to create separate IDs associated with certain projects and I want to be able to tie like projects to another project (it is our workaround for no real campaign object). How would you like the feature to work - A calculated field creates a value upon project creation when project type = campaign. The value generated will be "campaign-1234"; the field name will be "campaign custom ID" it is a calculated field. I want to then create a custom form for a non-campaign project object and on this form i want to have a drop down of the existing values in the "campaign custom ID" field. That way, I can tie projects to one or many other campaign like projects. Current Behaviour - I don't believe there is currently an option to do this.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.