Enter your enhancement requests or ideas for any of the components of the Aprimo SAAS platform, or vote for your preferred feature requests below.
For more information on how to use this forum: Aprimo Voice How-to-Guide
Would like to have the ability to configure the left hand task tiles within the Task Inbox so that users can add/substitute the current fields that appear. For example, adding a user requested due date EA for a task on to the task tile would allow users to prioritize tasks based on the requested due date.
when multiple project triggered automatically from a mail workflow (using same workflow template), all the projects triggered have same name.
So should have an ability to change the Activity/Project/Task title using EA value from workflow template.
Equip the Task Inbox so that the task tile listing doesn't require an explicit page refresh to show new or updated tasks.
Description: Currently our users have to refresh their page in order to see new tasks in their In Box. We have situations where user can receive back to back tasks and they have to refresh their page before they see the next task. We would like the system to auto refresh so that users do not need to do this.
Business Use Case: page views should auto refresh after an action has been completed. a Manual refresh should not be necessary.
As a user I need to accept terms an conditions when downloading an asset. That info is then captured and logged for auditing reasons later on.
as a user i want to subscribe to get notified of any changes to an individual record, changes to a set of records identified by a view and changes to a set of records belonging to a collection
Allow customize options to selectively choose which default notifications to receive rather than the current all/off option.
The "Task Inbox Only" domain right should remove the 2nd hyperlink on Notifications which routes to legacy task view
The "Task Inbox Only" domain right should also remove the 2nd hyperlink in Project Notifications (i.e. Task Assigned; Review Tasks; Reminders; etc.) Or even better, add "Task Inbox" as a Link Destination option on Notification Templates. It can be confusing to have two links and be routed to the legacy view when the customer is used to the Inbox view.
When using the legacy task completion page and attempting to close a task after creating Draft Annotations, the user will get a prompt with a reminder that they have created Annotations that are still in draft mode. This prompt prevents users from forgetting to publish their annotations and make them visible to others. However, when using Task Inbox, users do not get this prompt and can close a task leaving annotations in draft status. It is only in review tasks where users will get prompted to promote annotations from Draft to Published when using Task Inbox.
This request is to provide Task Inbox users with a prompt to publish their draft annotations when closing a task.
This will be available in version 105.
We would like the ability to tag any user/reviewer (anyone who is a licensed user) in a Chat. We'd prefer to have the entire list of licensed users in the drop down and choose anyone from the list that could benefit/participate in the chat.
Currently, we can only tag a reviewer in a chat but it would be more efficient if we could tag a future reviewer or another licensed user in a chat rather than having to follow up with them through email in order to keep them in the loop as to what was discussed via chat on a project.
In the Legacy Task Inbox, if the user selects Close on a task when not all required fields have been populated, an exclamation mark in a red circle highlights and identifies required fields to be populated.
This feature pinpoints missed required fields and is very helpful to quickly isolate what information is necessary to complete the task; especially when working with lengthy DCTs.
This request is to add this highlight feature to the Task Inbox.
We used to have a Print icon in Aprimo Legacy Navigation, now that we have moved to Aprimo New Navigation the Print icon is no longer there. Our PM's used this Print option to print out the Team roster list in their Campaign.
It would be great if DAM would have support for handling duplicates in the system upon ingestion. Currently, when an asset gets uploaded via UI, DAM can detect if the file is duplicate of an asset that already exists in the system, however user can disregard the message about duplicate and still publish the asset.
It would be good to give system administrators in DAM opportunity to configure desired behavior when duplicate is detected, so that publishing of duplicates can be prevented if so configured.
On a bigger scale, it would be good if this feature is applicable to all types of ingestion (including custom ingestion mechanisms, via REST API) so that ingestion can be prevented for duplicate assets if so configured by system administrators regardless of ingestion mechanism.
When browsing classifications or classification list fields, if a classification does not have a child, there should not be a plus symbol next to the classification name.The plus symbol i
ndicates that a classification has a child, and when browsing larger, more complex classification structures, end users do not always know which classifications have children, causing a more difficult browsing experience. Also, after clicking on the + symbol next to a childless classification, the symbol disappears.
Often, we’re able to optimize and simplify workflow processes by using 1 workflow to accommodate many different channels. This is great because we can reduce the amount of configuration in the system and mitigate the amount of maintenance. However, SLAs in this scenario for duration on a task tend to get generalized and are not specific. It would be great if there were a way to set criteria such as a Type to determine which duration would apply on a given task. This way, we could configure many different SLA’s to apply to 1 optimized workflow based on a Type that could be determined up stream in Job Starter, a Planning Task or manually within the Activity or Project Details page.
When a project is created in Aprimo, the title defaults to the workflow template that was used to create the project. Project managers don't always update the title of the project to a unique name. In some cases, this is not necessarily part of their business process. In some processes, an extended attribute is used as the project "title", since an EA can be updated on a DCT and a project title cannot.
In New Nav, a project card might be useful to some users, but in cases where the title is not unique, it is difficult or impossible to find the project you are looking for since you can only search by title.
This request is to add Project ID to the search on the project card.
An example is below.
Customer support service by UserEcho