What is the best approach for developing generic workflow which is called from within different parts of the main workflow but which, each time it is called, should have some customisation to identify at what point in the main workflow it is.
My scenario is that an ' impact a change request' task and an 'implement the change request' task are complex but both have exactly the same functionality. I would like to be able to call this generic workflow (IPC event) but be able to pass 'Impact' and 'Implement' at the appropriate times.
I was hoping to be able to update the activity name once in the sub-process, so that the information is available from the standard K2 Task List (we want to avoid customising the task list) but that appears to be read-only.
Any advice would be appreciated. Thank you.
