Skip to main content

Adding additional configuration to a subprocess

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

Provide access to relevant resources, such as properties or rules, that are outside your current case type by changing the scope of a subprocess in the case type. As a result, you ensure that users can access information that is necessary to successfully resolve their business processes even if the resolution requires data from another case.

For example, a customer service representative (CSR) can resolve a complaint about hotel service by using information that a customer provided while booking a hotel room.
Before you begin: Add a subprocess to your case life cycle. For more information, see Calling one process from another process.
  1. In the navigation pane of Dev Studio, click Case types, and then click the case type that you want to open.

  2. In the Case life cycle section, in the header of a process that contains a subprocess, click Configure process.

  3. On the toolbar, click Open process.

  4. On the Diagram tab of the flow form, open the property dialog box by double-clicking the Subprocess shape.

  5. In the Subprocess details section, in the Define flow field, select a working context for the subprocess:

    Choices Actions
    The subprocess works on a current case Select On current page.
    The subprocess works on a specific case
    1. Select On specific work item.

    2. In the Work property field, enter a property reference in the current work item that identifies the key of the subprocess work item.

    3. In the Class field, enter the class of the subprocess work item.

    4. Optional:

      To specify a clipboard page that holds the subprocess work item, in the Page name, enter the clipboard page name.

      Note:

      If the case is open as a page on the clipboard, you can leave the Work property field blank.

      If the case does not already have a page and you do not provide a page name, your application creates a page named pyNextObj, pyNextObj_1, and so on.

    The subprocess works on an embedded page
    1. Select On embedded page.

    2. In the Page property field, enter a reference to the property of mode Page, Page List, or Page Group that holds the embedded page.

    3. In the Class field, enter the class of the embedded page.

  6. In the Flow name field, enter a name of the process that includes the subprocess for which you provide additional configurations.

    By default, the system autpopulates this field with the name of the current process.

  7. Optional:

    To display a message in the audit trail of the subprocess, in the Audit note field, enter a rule that stores the audit note that you want to include.

  8. Optional:

    To allow the parent flow to continue processing without waiting for this subprocess to return, select the Spinoff flow check box.

    Note: When a case reaches the subprocess that runs as a spin-off, the subprocess runs asynchronously and independently from the main process. The main process can continue without waiting for the results from the subprocess. The main process and the subprocess might operate on the same work item or different work items.
  9. Optional:

    To provide a link to the subprocess in the breadcrumb trail navigation, select the Enable navigation link check box, and then configure additional navigation options:

    • To enable users to get back to the subprocess after the case moves forward, select the Only allow navigating back to this step check box.
    • To enable post-processing or validation when users navigate back from the subprocess in the breadcrumb trail, select the Perform post-processing when navigating away from step check box.
    • To allow users to return to the entry points in the subprocess, select the Subprocess has navigation links check box.
  10. Click Submit.

  11. Click Save.

  • Calling one process from another process

    Make your business processes more granular by complementing a process with a subprocess in your case life cycle. As a result, you avoid creating long and complex case types and deliver an application that is easier to maintain and edit if your business requirements change. Additionally, you save time because you reuse assets across your application.

  • Subprocesses

    A subprocess, also called a subflow, is a flow that is called by another flow. You can create a subprocess by adding a step to a process in the life cycle of a case or by adding specific shapes to a flow diagram. Subprocesses modularize the events in the life cycle of a case.

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice