Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Adding a work type to a framework and its implementation layer

Updated on June 10, 2020

Enterprises that have a framework and have built an implementation layer on that framework often want to extend both the framework and the implementation by adding work types that directly inherit from the framework. Although you can use the Application Accelerator to add work types to both the layers, the accelerator cannot set up the inheritance between them.

This article describes how you add a work type to the framework layer using the Application Accelerator, and then extend the work type to the implementation layer by configuring rules in the implementation to set the inheritance.

This procedure is for implementations built on PRPC versions 6.1, 6.2, and 6.3.

Extending a work type is a two-step process.

  1. In the first step, you use the Application Accelerator to add a work type to the framework layer.
  2. In the second step, you configure updates in the implementation layer to extend the work type and inherit it from the Framework.

In this example, the site has a framework named ServiceFW with an implementation named WebService built by the Application Accelerator with one work type called Account Change.

Framework and implementation layers in explorer

Step 1: Adding a work type to the framework layer

Perform this step in the framework.

  1. Select the framework as your current application.
  2. Open a new instance of the Application Accelerator, and select the Update Existing Framework option.
    1. Set the value of the Existing Implementation Name and Version to your framework and version.
    2. In the Make Changes field, select Current Version or New Version.
    3. Click OK.
  3. On the Create Processes tab, select the Add a work type option.
  4. Add the work type and any other work type information you want to define the work type, such as use cases, requirements, and a discovery map.
  5. On the Review Application tab, click Build the application to add the work type and a starting flow to the framework.

Select Update option

The Application Accelerator overview

Work type option

The Create Processes tab

Resulting explorer display of framework

Resulting display of the framework

Step 2: Extending the work type to the implementation layer and setting inheritance

In this step, you do three configuration tasks in the implementation layer.

  1. Create a corresponding work class that inherits from the work class in the framework.
  2. Create a starting flow in the corresponding work class that calls the starting flow for the work type in the framework.
  3. Update the application rule to reference the work type and work class.

Creating a corresponding implementation work class

  1. Copy an existing work class or add a new work class for the new type.
  2. In the Class Inheritance section of the General tab, select the corresponding framework class as the parent class.
  3. Click the Save icon to save the class.

Add application class

Creating a starting flow in the class

Create a starting flow in your new implementation class.

  1. Set the Applies To value to the class you created for the work type.
  2. On the Diagram tab, right-click the starting shape to display its properties panel. Enter the same name as the framework flow and reference it as the name of the Flow rule.
  3. On the Process tab, select the Creates a new work object? check box to mark it as a starting flow.
  4. Click the Save icon to save the flow.

Creating a starting flow in the class

Adding the work type to the Application rule

  1. Display the Application rule form for the implementation.
  2. In the Work Types section of the Details tab, click the Plus icon to add a row.
  3. Enter the work type in Name field, and select the Implementation Class that you added to the implementation.
  4. Click the Save icon to save your changes.

Update application rule

Resulting configuration

After you complete these steps, the resulting framework and implementation layers should look similar to the following example.

Resulting configuration

  • Previous topic DCO 6.2 and 6.3 - Working with Application Use Cases and Requirements
  • Next topic DCO 6.1 - About the Direct Capture of Objectives

Have a question? Get answers now.

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

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us