You are viewing limited content. For full access, please sign in.

Question

Question

Forms sub-processes and field rules using process steps

asked on March 3

I'm working on a large HR process with 12 different options for approval 'paths'.  I was hoping to use sub-processes to keep my process diagram clean and modular and copy and modify the sub-process for each path.  I'm using field rules based on process steps to show/hide/disable/validate fields.  This works for my 1st sub-process, but as soon as I copy that sub-process it renames all the process steps with a (1) and if I eliminate that naming, I get an error when validating that I have steps with the same name.

So, I seem to be left with the option at this point of adding an additional condition to each field rule for each process step I copy or scrapping the use of sub-processes all together.   

The use of sub-processes seems to be so restrictive and specific, I wonder how anyone actually uses them?  I can't use a sub-process more than once, and I can't add process stages within a sub-process to help with the use of field rules.  In a large complex process as this it seems as if they would be useful, but I cannot find the utility I'm looking for.

0 0

Replies

replied on March 3 Show version history

I usually name them with an ending based on the name of each Sub Process to keep it organized.  I have one process that has 3 Sub Processes: All Required Docs, Temp Sub Docs and Payroll Docs.  If the steps within my process have the same name as another one, I just add All to the end of each activity and so on.  

BPs won't let you name any activity the same as one that already exists.  

2 0
replied on March 3

That's what I found as well, activities need a unique name.  So, for my field rule to show a field when process step is Comp & Class Review.  I'd need to add additional field rule conditions for that process step that goes to that team but with a unique name for each sub-process. Which I was hoping I wasn't going to have to do as the Comp & Class team would participate in all 12 subprocesses.

I'm going to re-think my process design and see if it is better to have dozens of field rules and field rule conditions or just move everything back to the main process and scrap using sub-processes.

Thanks

0 0
replied on March 6

Depending on your overall designer, you can utilize Process Stage instead of step so it would apply to any activity in that stage.

 

1 0
replied on March 6

So, for the options of approval task...  Do you mean it could possibly go to one of 12 people for the task, but the task is the same?  Just got to thinking.  

1 0
replied on March 3 Show version history

All sub-processes need to have a unique name, but I use this option and I copy/pasted these, just made sure when I removed the (1), I renamed the Sub-process to Sub-process 2, 3, 4, etc:

0 0
replied on March 3

That's what I did as well - what do you do with the process steps within the sub-processes?  Do you leave the step names with the (1) or do you rename the steps within the sub-process? Do all the sub-processes have the same steps and step names?

 

0 0
replied on March 3

If a user task is going to the same person and it has the same name, only one will show up for that person, especially if it is the same form too.

 

2 0
replied on March 6

I have 12 different options from combos of radio buttons, that basically used the same 'approval path' with a few exceptions.  I decided to stay with one sub-process for the approvals and put in gateways for those exceptions. I think this is going to work. Thanks

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.