In terms of KDB footprint, which one is recommended for (set of script task + 1

nikhilh0001 over 13 years ago

In terms of KDB footprint, which one is recommended for (set of script task + 1 user input task) which re occurs many times throughout a process model:
1. Individually copy pasting the script task and the the User input task in the main process
2. Creating sub process for the set and calling this sub process throughout the main process. In this case, we cannot archive this sub process since we have to show the task details in reporting.

Even if, for maintenance purpose, the 2nd option is better, for Performance or KDB getting loaded, which one is recommended? Please let us know...

Discussion posts and replies are publicly visible

Parents

0 Michael Tan
Appian Employee
over 13 years ago

Since you are not going to kick off the subprocess and immediately archive or delete it, then option 1 is better. You don't need to copy and paste the script task and user input task x times. If it needs to be repeated, then you can loop around to this part of the flow or make it a quick task if needed.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Michael Tan
Appian Employee
over 13 years ago

Since you are not going to kick off the subprocess and immediately archive or delete it, then option 1 is better. You don't need to copy and paste the script task and user input task x times. If it needs to be repeated, then you can loop around to this part of the flow or make it a quick task if needed.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data