+2
New

Dynamic Row EAs for Content Management

Karthik Balakrishnan 3 months ago in Productivity Management • updated by Shalini Arisam 2 months ago 2

Dynamic Row EAs for Content Management in Aprimo.

By 2017, Aprimo told this functionality is in road map. One of our business is based on content management.In order to track all the content inside Aprimo, we were creating number of EA. This leads us to reach soft limit also hard limit of EA count.

We reached hard limit for one of our environment in 2017 and Aprimo told there is a road map to create a functionality "Dynamic row EAs" 

Michael Bennett

Additional comments (External)

Journal type: Additional comments (External)

Hello Susan, We heard back from Product Management regarding the dynamic row EAs and they're still on the roadmap, but no target date has been set yet. Additionally I'll be reaching out to see if there is any such plan for Mass Update at project level EAs and see if I can get a status update on that as well. Kind Regards, Michael Bennett Application Support Analyst Aprimo Michael.Bennett@aprimo.com

There are several reasons why Generic Objects (GO) will not solve the business use cases that EAs are able to solve for.

1. Attributes within GO are not visible within Task Data Collection Templates. User needs to directed to the GO to view/edit the attributes. Most of the users that need to see the information are Contributor users and they don't have access to content in Generic Objects (available to only full users).

2. We need attributes that are only visible to certain roles in an edit mode and read only for other roles. (Use Case: Gathering business requirements from multiple stakeholders. Requirements of Finance should be input by Finance but they should not be editable by Risk or Decision Mgmt. Other stakeholders need to be able to view them but not edit. They each have their sections to complete). Data security is an issue. Also data in GO can be changed by PM at any time even after approvals were obtained. Record cannot be locked for edits.

3. The same GO is accessible through all the projects and all activities, how will users know to distinguish one line from another? How can a user know to add requirements in GO ID# 123 and not in GO ID# 456 for a specific project?

4. We can only use 2 of GOs with Activity and Project. The other 3 GOs are not as useful as they are in Master List.

5. For our business use cases, we need a systemic way of capturing and reviewing data in an easy, readable, modifiable format on the screen as EA’s (and not require user to download document to view contents). We have tried to maintain some data in an excel file to reduce the EA’s, however, comparing before and after values in a file to ensure requested change has been made is a tedious process.

What we really need are some Custom Tables/Objects that we can relate with Activities and Projects with one-to-one relationship between Activity and Projects. But the GO has one-to-many relationship with Activity and Projects, hence we are not able to use this for our use cases.

Hope this clarifies why we cannot use the GO’s as proposed by Aprimo!

New

Aprimo invested in development of Generic Objects to address the need for 1 to Many sets of data related to an activity.  This feature is available today.  What is the use case for these EAs and would using a Generic Object address the need?  If not why?