Skip to main content

 –

Changing the context of a subprocess

Suggest edit Updated on November 5, 2021

You can change the scope of a subprocess that you call from a flow. By running a subprocess in the context of a specific class or case, you can use properties, rules, and other functionality in your application that you cannot access from the parent flow.

  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. On the Workflow tab, click Life cycle.
  3. Click the process that contains the subprocess step.
  4. Click Open process.
  5. On the Diagram tab of the Flow form, double-click the Subprocess shape to open the property panel.
  6. Optional: To allow the parent flow to continue processing without waiting for this subprocess to return, select the Spinoff flow check box.
  7. Choose a context for the subprocess.
    • To work on the current case, from the Define flow list, select On current page.
    • To work on a specific case, from the Define flow list, select On specific work item. Complete the Work property, Class , and Page name fields.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, you application creates a page named pyNextObj, pyNextObj_1, and so on.

    • To work on an embedded page, from the Define flow list, select On embedded page. Complete the Page property and Class field names.Note:

      The Page property field must use a mode of Page, Page List, or Page Group.

      If you want to use a class that is not known at design time, in the Class field, you must enter a property reference or expression.

  8. Click Submit to close the property panel.
  9. Click Save.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us