Skip to main content

Configuring post-processing for a flow action

Pega Community logo

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

Define the behavior of your application after users complete an assignment by providing a post-processing configuration for a flow action. With a post-processing configuration you can save time, automate your processes, and take advantage of additional options that improve manipulating data in a case. Because you can use a data transform, an activity, and a robotic automation, your application development process is flexible and can help you meet your individual requirements.

For example, you can use savable data pages to save information that the current case does not include. Consider a scenario in which a user who has an account in an online shop edits personal details when placing a shipping order. Although the modification of the contact information is external to the main case, a user can still save the relevant data.

To store modified information, you can use a top-level data page that you need to provide in the flow action. You can also use an embedded data page. However, in this scenario the new information persists only in the context of a current case and your application does not save the new data to any external system.

For post-processing, the system first invokes a robotic automation, saves the data pages, runs the data transform, and then runs an activity. Specify the elements of post-processing according to your needs. For example, you can specify only robotic automation and a data transform, and you can omit providing an activity.
  1. In the navigation pane of Dev Studio, click Records.

  2. Expand the Process category, and then click Flow Action.

  3. If you use the Robotic Desktop Automation (RDA), specify the post-processing automation to run on the user's desktop when you want to send data that users enter in a case form to all the applications that run on the user's desktop:

    1. In the Run robotic automation field, enter an automation name.

    2. In the Description field, enter text that describes the purpose of the automation.

    Note: Automations always run synchronously and flow processing pauses while the automation is in progress. After the automation stops processing, the system updates the clipboard, and then the data transform runs.
  4. Optional:

    To save a data page after the flow action completes, in the Savable data pages subsection, list the data pages that you want to save:

    Choices Actions
    Use a data page
    1. Click Add data page.

    2. Optional:

      To save the data page only under certain circumstances, in the When field, enter a When condition rule.

      At run time, if the When rule evaluates to true, the application saves the data page. If you leave this field blank, the application always saves the data page.

    3. In the Data page field, specify a data page to save.

    Use a data relationship by providing an autopopulated property
    1. Click Add data page.

    2. Optional:

      To save the data page only under certain circumstances, in the When field, enter a When condition rule.

      At run time, if the When rule evaluates to true, the application saves the data page. If you leave this field empty, the application always saves the data page.

    3. Select the Use associated property check box.

    4. In the Autopopulate property name field, specify an autopopulated property.

  5. Optional:

    To add more data pages, click Add data page, and then repeat step 4.

  6. Optional:

    To monetize efforts connected with performing the flow action, in the Apply cost field, specify the flow action cost:

    • To specify the cost manually, enter an expression or a number in units of any type, such as currency.
    • To calculate the value automatically, enter a property reference that identifies a numeric property that is used in your computation.

    In a single application, use only numbers or property references.

  7. In the Apply data transform field, specify a data transform that the system applies to the current primary page at run time.

  8. In the Run activity field, enter the activity that the system runs after processing the flow action is complete.

    Consider the following factors when you use an activity for post-processing:

    • Do not include a Commit method in the activity.
    • If you use an activity that depends on parameter values that a user enters after selecting this flow action, enter the activity in the post-processing configuration rather than placing the activity in the flow.
    • You can use the activity to perform validation processing and add messages to the clipboard if validation fails. Validation by applying an activity is more suitable for complex validation scenarios. The activity can also perform additional processing that occurs after the user successfully submits the flow action.
  9. If the activity includes parameters, in the Parameters section, enter values for the parameters.

  10. Click Save.

  • 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.

  • 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.

  • Managing work across your team

    Achieve the best results while processing your Microjourney by efficiently managing work across your team. When you create a team for users and define routing conditions to assign tasks, you ensure that each task in the case is completed by the team member that is best-suited to the job. As a result, you meet your business goals faster, and to greater effect.

  • Assigning tasks to users

    Improve business process efficiency by assigning tasks to appropriate individuals or groups of individuals. For example, you can create a task for a CSR to follow up with a customer, and then route that assignment to the CSR work queue.

  • Assigning users automatically at run time

    Process your business cases with flexibility and efficiency by using business logic to automatically determine which individual or group of individuals receives an assignment in a case. Instead of entering specific names of users and teams, you can provide conditions that your application evaluates at run time to assign a task.

  • Customizing the Get Next Work logic

    You can customize Get Next Work processing to the meet the needs of your application and your business operations without creating new activities. If you create or override standard rules, save the rules in a ruleset and version that is available to all appropriate users.

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