Copyright © Cloud Software Group, Inc. All Rights Reserved

Sub-Procedures

Sub-procedures provide the ability for a case of one procedure to start a case of another procedure as one of its steps.

When a sub-procedure is started, flow is halted along that particular path of the calling procedure until the sub-case has completed. When the sub-case completes, flow will resume in the main procedure.

When a procedure is defined, it is defined as either a “main procedure” or a “sub-procedure”. You can directly start a main procedure from the procedure list. Sub-procedures cannot be directly started; they can only be started by a step in another procedure.

Sub-procedures can be many levels deep, i.e., a sub-procedure can also contain a sub-procedure call step, and the sub-procedure started by that call step can contain another sub-procedure call step, and so on.

When a sub-procedure is started from another procedure, the system looks at the sub-case precedence setting to determine which status of the sub-procedure it should start. The default is to always start the released status of the sub-procedure, although you can specify that it look for other statuses of the sub-procedure to start. For instance, you may specify that the system look for a model status of the sub-procedure first, and if it doesn’t find one then to look for a released status. For information about setting the sub-case precedence, see Sub-Case Version Options.

You can also view the case history for the sub-case by viewing the case history for a main case, which shows you when sub-cases are started and completed, as well as the actions that are performed within the sub-case. For more information, see Case History.

Also see Displaying Main and/or Sub-Procedures for information about choosing whether or not sub-procedures are displayed in the procedure list.

Copyright © Cloud Software Group, Inc. All Rights Reserved