Refactor the action "Imports" tab

nathan_rudman

The action import tab should include:

- all the info that is in the first tab the source ID ( especially the last execution date)

- source object should be exploded into workspace/model/module/view fields

- the data source ID should be available here as well

- an export button, just like on the first tab

- the ability the filter by all the existing fields

Comments

jziemer

@nathan_rudman I very much agree! We need to combine the Actions Tab and the Imports Tab. This has been a thorn in my side for years. I end up exporting both tabs and joining them in Excel to get all the data I need to troubleshoot and research how a process is working. Thanks!

Quick Links

New ideas

Anaplan Color Pallet
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: The Anaplan Color pallet should be consistent across all forms. Text Pallet is different Action Icon Default Colors, and different…
Workflow: Continue Workflow after Decision Task Rejection
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: Currently a workflow ends if a decision task is rejected and it is not possible to add workflow steps after the rejection. I want to…
Allow non-WSAs to view source module name in UX.
When a user clicks the ellipsis in a grid card they should be able to see the name of the source module. This empowers end users with the ability to connect to the source data they see in the UX to the module in the backend. It also enables end users to pull the data into Google Sheets or Excel.