From business perspective, what is the best practice of naming Stage and Step?
1. What are these two definitions?
2. Does Step have to be assignment shape (human interaction)? Or if within a flow rule everything is utility shape (automatic), still do they become Steps?
3. In my scenario I have only one shape in each stage. In that case, I tend to name the Step as the same as Stage but I feel having the same name between Stage / Step look kind of strange. In that case how do people handle naming? Select different wording or am I doing something wrong?
4. If there are any best practice on these I would like to follow.
***Edited by Moderator Marissa to update platform capability tags****
For the Steps, I was playing around what would be easy to understand for business user but actually when I modify work flow (like adding utility shape or assignment shape etc) it automatically updated the view. Was it like this from before? In prior Pega platform like 7.2, I thought that step drawing is not related to actual flow rule shape drawing. Also, anyways if this is how things work, business user thinking a lot about step structure at the beginning is not really important as it would be overrode by developers later. Is my understanding correct?
I would still consider "business user thinking a lot about the step structure at the beginning" is still important since it gives the blueprint of the use case/application. However, it would still get overridden by developers as per the requirement
Stage: A stage is a first level of organizing all the different tasks required to complete work associated with a case. Step: Represents a task that is completed in a stage. A step can range in scope from a single assignment to a complex, multi-step process.