Creating a stand-alone process
Create a stand-alone process, or flow, to support or supplement the steps in a case life cycle. By creating a process outside the context of a case life cycle, you can reuse the process in other cases.
Create the rule that stores the flow.
In the header of Dev Studio, click.
On the Create form, enter values in the fields to define the context of the flow.
In the Label field, enter text that describes the purpose of the flow.
- To change the default identifier for the flow, click Edit, and then provide a unique value in the Identifier field.
In the Apply to field, press the Down Arrow key and select the class that defines the scope of the flow.
The class controls which rules the flow can use. It also controls which rules can call the flow.
In the Add to ruleset field, select the name and version of a ruleset that stores the flow.
Click Create and open to open the Flow form.
- To support a class that is different from the class to which
the flow applies, enter a class name in the Work class field on
the Design tab of the Flow form.
This approach is helpful when your flow runs on an embedded page that is not in the same class path as the applies to class of your flow.
Add a primary path to the flow by connecting and configuring shapes.
For more information about the different shapes that you can use, see Flow shapes.
- Enhance your flow with advanced functionality.
Integrate the flow with your application by using one of the following techniques:
- Flow shapes
A shape in a flow represents a task that a user or application completes as part of a business process. By connecting different types of shapes in a flow, you can define the path that a case follows from creation to resolution.
- Unit testing a Service SOAP rule
Services start their processing in response to a request from an external application. Before you add the external application to your testing process, use the Simulate SOAP Service Execution feature to verify that the service processes data appropriately. When using this feature, you manually provide some representative data to process. You specify a test page for the rule to use, provide sample data as the input, run the rule, and examine the results to see if they are what you expect.
A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.