Same Process Type in Process Clone
Kamal Saran
Merged in a post:
Retain Filters on Clone Process window
H
Harsh Seksaria
When we configure a new process, a cloning window opens up as soon as we get into the process.
The options on this clone window don't persist and a user has to select all options again which is very time-consuming especially in scenarios where deployment is heavy and we need to clone multiple processes.
If these preferences (Same process type only and Context filters) can persist atleast for the current session, that would immensely save time during deployment.
Photo Viewer
View photos in a modal
C
Claudine Richardson
Hello Harsh Seksaria! I have a few more questions for you:
- How frequently do you need to clone multiple processes in a single session?
- Are there specific filters that are more important to retain than others?
- Would retaining filters across different sessions be beneficial, or is it only necessary for the current session?
H
Harsh Seksaria
Hi Claudine Richardson,
- In certain accounts, based on the solution, most of the configuration can be done by just cloning. Within a session it could range from 40-200+ depending on the number of teams we are configuring for.
- Same process type only, Customer, Contract and Service filter on this cloning window is important.
- Retaining across sessions is definitely beneficial. To quickly get this feature, we can initially look at current session by storing these in browser data storage/something else instead of changing in db & new APIs to enable this, and then gradually move to retaining this across session.