I think it would be beneficial to have the ability to repeat an action inside a process. Currently, you can only add an action once inside a process.
Hello @pratikjaiswal
Why do you need this ability ?
Can you explain your use case please ?
Let's say I create a staging list and the plan is to use it to stage data from multiple sources and delete them one by one after sending it to the required modules/list.
After each iteration of importing and sending data, I can use empty fields from a line item to clear the list.
But as of current functionality, I can only use the action I created to clear the list once inside a process. And if I need to stage something else, I would have to again create an action to clear the list inside the same process. Why can't I use the same clearing action multiple times for each iteration of staging inside the same process?
Let me know if you think there is a better way to deal with this.
Cheers!
Also for iterative calculations this would be beneficial.
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…
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…
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.
