Subprocess activity

Examples

• (Example) Configure a Subprocess Activity for the Absence Request Process
• (Example) Create a Subprocess
• Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Good to Know

• In most text fields, you can use process data variables as an alternative to literal data values.
• This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
  • Properties for System Activities
  • BPMN Properties screen
  • Notifications
• You can configure whether this activity waits for other activities before it runs.

  For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?

How to Start

1. Open Process Builder.

   For information about how to open this screen, refer to Process Builder.

   
   
   

2. In Process Builder, in the Activity Library, open the Common tab.

   
   
   

3. On the Common tab, drag the Subprocess activity onto your process.

   
   
   

Procedure

1. Complete the fields on the General Configuration screen.
2. Click Subprocess .
3. On the Subprocess screen, do one of these:
   • To use a specified process model for your subprocess, do this procedure.
     1. Select Predefined Subprocess (Only From This App) or Predefined Subprocess (From All The App).
     2. Click Subprocess Template .
     3. On the Subprocess Model screen, in the Subprocess Model field, select the process from the list.
     4. Click Subprocess Configuration .
     5. On the Subprocess Configuration screen, do this procedure.
        1. To specify the format for the name of the subprocess, do one of these:
           • To use the name of the process model to create the process instance name, in the Subprocess Instance Name Format field, select Name .
           • Select Custom to specify a different format.

             In the Custom field, enter the name of the process, or drag a process data variable from the Process Data screen.

        2. (Optional) To add a GUID to the custom subprocess name, select If the subprocess name already exists, append the name with @${GUID}.
        3. To specify the name of the process that starts the subprocess, do one of these:
           • To let the parent process start the subprocess, in the Subprocess Initiator Name, select Process Initiator.
           • To let a different process start the subprocess, select Custom.

             In the Custom field, enter the name of the process, or drag a process data variable from the Process Data screen.

     6. Click Subprocess Mapping Attributes .
     7. On the Mapping Attributes screen, do one of these:
        • To share all the process data variables from parent to child, select Share all Attributes (Basic).
        • To copy all the process data variables from parent to child, select Copy all Attributes (Advanced).
        • To specify variables to share from parent to child, do this procedure.
          1. Select Map Specific Attributes (Advanced).
          2. Click Schema Mapping .
          3. On the Schema Mapper screen, drag the variables from the parent process model schema to child process model schema as necessary to connect them.
   • To use a subprocess you created based on a variable in schema, do this procedure.
     1. Select Dynamic Subprocess (Advanced).
     2. Click Subprocess Configuration .
     3. On the Subprocess Configuration screen, do this procedure.
        1. In the Subprocess Model field, enter the name of the process, or drag a process data variable from the Process Data screen.
        2. To specify the format for the name of the subprocess, do one of these:
           • To use the name of the process model to create the process instance name, in the Subprocess Instance Name Format field, select Name .
           • Select Custom to specify a different format.

             In the Custom field, enter the name of the process, or drag a process data variable from the Process Data screen.

        3. (Optional) To add a GUID to the custom subprocess name, select If the subprocess name already exists, append the name with @${GUID}.
        4. To specify the name of the process that starts the subprocess, do one of these:
           • To let the parent process start the subprocess, in the Subprocess Initiator Name, select Process Initiator.
           • To let a different process start the subprocess, select Custom.

             In the Custom field, enter the name of the process, or drag a process data variable from the Process Data screen.

     4. Click Subprocess Mapping Attributes
     5. On the Mapping Attributes screen, do one of these:
        • To share all the process data variables from parent to child, select Share all Attributes (Basic).
        • To copy all the process data variables from parent to child, select Copy all Attributes (Advanced).
        • To specify variables to share from parent to child, do this procedure:
          1. Select Map Specific Attributes (Advanced).
          2. Click Initial Attributes .

             An initial attribute is a process data variable in a subprocess that is populated with a value from the parent process when the parent process starts the subprocess.

          3. (Optional) To share the parent process's variables with the subprocess if the subprocess uses the same data, do this procedure.
             1. On the Initial Attributes screen, in the Name field, enter the name of a variable to connect with a subprocess.
             2. In the Value field, enter the value for the attribute, or drag a process data variable from the Process Data screen.

                The value in the child process is connected to the variable in the parent process.

             3. To add more attributes, click Add .
4. (Optional) Click Advanced > Email Notifications .

   For more information, refer to Email Notifications screen (Process Activities).

Specifies the basic settings for the Subprocess activity.

Fields

Specifies the type of subprocess you want.

Fields

Specifies the process model for a subprocess.

Fields

Specifies the format for the name of the subprocess. For example, the format can contain the name of the subprocess, the session ID, and the name of the Subprocess activity in the parent process. You can use the name to manage your processes in Manage Center.

Examples

• (Example) Create a Subprocess
• (Example) Configure a Subprocess Activity for the Absence Request Process
• Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Fields

Specifies how to map variables in a subprocess.

Fields

Specifies a set of process variables to pass to a subprocess. You can share the parent process's variables with the subprocess if the subprocess uses the same data.

The subprocess can have its own data only within the subprocess, or it can share its data with the parent process. For example, a subprocess can access the data of the parent process, such as the reviewer name and review completion date.

Fields