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
Our request is allow the base Program field to be surfaced on DCTs like any other EA; as Read Only, Required or Editable but Optional. We currently surface the Program field on Work Request Forms but sometimes the requester makes an inaccurate selection. It would be great if someone in the process could update the Program to the accurate option through their Task Inbox rather than having to access the Activity to update the selection.
With the new "Export for Project Load" function on the Activity's Project list page, we lost the ability to perform a "Normal Export". (Amelia rejected this as a defect!) Please add it back!
We would like the ability to remove or deemphasize the comment box in annotations.Some End user at times don't use annotations and add it to the Comment box, making it difficult for our Designers to make the correct modifications to the Creative file. We train users to use annotations, but there are those that still add comments to the box and forgo using the Annotation toolbar. If we can't remove the comment box, someway for us to modify with a message, perhaps - "don't use for annotating, use annotation toolbar".
Several workflow templates are set up to kick off another workflow template. When this happens we don't have a good way to understand what project initiated another project. We would like to get better tracability of project kickoff.
A couple of options
Leverage status actions to set an EA of the parent project initiating the work
Allow user to select linked workflow - similar to change order workflow types
Systematically tie workflows together with a new base feature field that would associate the workflows together.
We have the scenario where we have multiple attachments that are limited by project where the user cannot always version the attachment to flow through a review, so what happens is there are multiple attachments that flow through review. So there end up being multiple attachments that are sent through review and not appropriate for a review.
We would like the user to be able to select specific attachments in a task that would flow to the next review vs showing all attachments at the project level so that unnecessary documents don't flow to the reviewers
Like in Visio when you select a task/review or a section of a workflow you have the ability to copy it. This is helpful when a section of a workflow will be repeated or the workflow will be similar, so you can copy and tweak rather than starting from scratch.
Need logs to capture API payloads sent to Aprimo from external users using integrations. Will help to debug any issue with API calls or missing data sent by external user to Aprimo.
As we are having an issue of missing data on Aprimo end which was successfully sent from our end using API, and we have to post same data twice to get the missing field data on Aprimo UI. Its hard for us to find the root cause for issue as Aprimo don't keep the incoming API payload log.
We have teams in our organization who would like to see tasks on the Agile Board, but only within groups of projects. This request is to add a filter within the Agile Board that can display tasks only within active (In Process) projects that fit within a specific Project Type.
We have a lot of users complaining that when you close a task in the inbox, Aprimo automatically puts the next task in the list in edit mode. Our users are in auto drive and start editing this task without really noticing which task it actually is and sometimes even closing the task. It would be nice if the middle task details wouldn't appear unless you click on the task card, behaving more like an inbox, so mistakes wont be made and tasks be closed off accidentally. Just interested what other customers think or if this is considered an extra click. Our users are new and still getting used to Aprimo, so also interested if this issue is just early adoption related? Thanks.
We would like the ability to add the Activity created by a Work Request Form submission to a Program. The same way a Program can be selected through an Activity/Activity Proposal, we would like to be able to select the applicable Program directly in a Work Request Form.
(1) Start a task next business day at 3:30 pm.
(2) Send direct email to printer next Sunday
(3) A task needs to happen every 2nd Monday of the month, if Monday is a holiday, option to skip or move to Tuesday.
Currently, we use a manual step where the project manager sets the project EA date as the relative date (next Sunday). It would be nice to automate this and avoid the manual intervention.
Customer support service by UserEcho