The Application Accelerator is a guided Direct Capture of Objectives (DCO) development tool that jump starts the creation and extension of an application, and automates best practices for application design. By leveraging data captured in an application profile, it speeds the creation of new applications, including applications built on frameworks or extensions of existing applications. As a result of running the Application Accelerator, the system generates the base foundation of the application, creating organization and class structures, draft versions of processes, user interface elements, and other items as defined in the application profile.
- Starting the Application Accelerator
- Specifying baseline information for the to-be application
- Example: Typical sequence for a simple application
- Navigating the Application Accelerator
- Deleting a generated application
The result of the Application Accelerator is a system-generated, working application. The Application Accelerator guides you through a series of steps to gather and review the information that the system uses to create the initial class structure, rules, and processes for your application. The accelerator supports an iterative development approach that allows you to enter, update, and save data until you are ready to create the application.
When the Application Accelerator is primed with an application profile, the profile's data is transferred into the accelerator's input forms to avoid duplication of effort and ensure project requirements on the application are captured. The data transferred from a profile includes:
- Application overview information, such as the application name, type (for example, a framework), organization name, and business objectives.
- Process information, such as the discovery maps and case trees
- Use cases and requirements
- Details about reports and correspondence
- Details about interfaces
When you complete the steps of the Application Accelerator, the resulting generated application is a base foundation from which to further develop and refine the processes, user interfaces, and other aspects of the application.
Note: This article describes the Application Accelerator in Version 6.2. For information about using the accelerator in Version 6.1, see DCO 6.1 — Using the Application Accelerator.
You start the Application Accelerator in the Designer Studio. The accelerator can be started and run by users who have access to the Designer Studio.
- Do not run the Application Accelerator when logged in with the operator ID [email protected] or with operator IDs that use the access group PegaRULES:Administrators.
- When you want to generate a new application that is built on an existing application, or to update an existing application, that existing application must be the in-context application when you start the Application Accelerator. The in-context application is the application displayed in the Designer Studio header bar.
Use the Switch Application menu to switch to the other application.
To start the accelerator:
In the Designer Studio, start the Application Accelerator by clicking next to the name of the currently logged-in application, and selecting New Application > Application Accelerator.
The system starts the Application Accelerator in the Designer Studio, and displays the Application Overview window:
To work on an existing prior run of the accelerator:
When the Application Accelerator starts, it creates a work object in the system. Prior runs of the accelerator that are available to your operator ID to modify are listed in the All Wizards list. (A prior run is available for you to modify if you created it, or the creator gave your operator ID explicit permission to open it). To open an accelerator work object from the All Wizards list:
- Click > Application > Tools > All Wizards.
The list initially displayed is the list of wizard and accelerator tasks that were performed by the current operator. To see profiles that were created by others, clear the Create Operator Is Equal field and click Run.
- Click the name of the work object to open it in the Application Accelerator.
Note: In addition to Application Accelerator work objects, the list of all wizards includes those tasks from non-DCO-related wizards and accelerators in the system.
When you start the Application Accelerator, the system displays the Application Overview window, and you choose whether to use information from a previously created application profile or directly specify the baseline information about the type of application you intend to build, the nature of the project, and the targeted business objectives.
Usually you select an application profile on which to base the new application. The system uses the specifications in the profile to pre-fill the required fields in this window. You can update them, or use the values from the profile.
Note: If the selected profile specifies building a new application upon an existing one, or updating an existing application, and the existing application is not the in-context application, you must switch to that existing application before running the Application Accelerator. Otherwise, the fields in the Application Overview window do not reflect the values from the existing application.
Optionally, you can start without an application profile; in this case, you must specify the items that are usually specified in a profile (such as the name of the new framework). In this case, you must first choose whether you are running the accelerator for:
- Creating a new application.
- Updating an existing application.
|When you are||Building on an existing framework?||You must specify|
|Creating a new framework||No||A name and version number for the new framework.|
|Yes||The name and version of the framework in the system on which to build the new application.
A name and version number for the new framework.
|Creating a new framework and implementation||No||Names and version numbers for both the new framework and implementation.|
|Yes||The name of the framework in the system on which to build the new application.
Names and version numbers for both the new framework and implementation.
|Creating a new implementation||Yes (an implementation is always built on a framework)||The name and version of the framework in the system on which to build the new application.
A name and version number for the new implementation.
|Updating an existing application||Not applicable||The name and version of the existing application on which to base the changes.
Whether the system is to make the changes specified in the accelerator to the current version of the application or generate a new version. If you specify that the changes are for a new version, you must enter a version number for the new version.
- Version numbers must be of the form
- The available choices in the drop-down lists of existing applications to build on or update are determined by your in-context application, and any applications it is built upon.
After specifying the required information, click OK in the Application Overview window.
Note: When working in the accelerator, you can open the Application Overview window and review or update the overview information by selecting Actions > Overview in the main display of the Application Accelerator:
After the overview information is specified, a new tab ("Generate an application") opens in the Designer Studio with a series of named steps (for example, Base and RuleSets). On any step of the Application Accelerator, click the Help icon () to display help about that step, including choices for fields and controls used in that step.
The Application Accelerator tab and its steps in the Designer Studio:
See Navigating the Application Accelerator for descriptions of each step.
This article section gives an overview of the basic steps used when generating a new simple application using an application profile. This examples in the Sample inputs/results column are based on using the profile from the Onboarding example in DCO 6.2 — Creating Application Profiles and Discovery Maps. While you can work on steps in the Application Accelerator in any order, this example is a typical sequence to follow.
Best practice tip: Use the Actions > Save choice to periodically save your work in progress whenever you enter information into the accelerator. While the system automatically saves detail entered in a step as you move from that step to another, periodically saving your work is helpful on steps where you are entering large amounts of data over a period of time (such as when working on the Create Processes or Project Explorer steps).
Start the Application Accelerator in the Designer Studio, and then follow this sequence:
1. Specify baseline information for the to-be application.
Select an application profile or directly enter the information (as described in the Build options in the Application Overview window table). When selecting a profile, optionally update the values from the profile as appropriate.
|Application Overview window||Select profile |
2. Specify the actors that participate in the business process steps.
If using a profile, the Actors window shows the actors specified in the profile, and you can update them. If not using a profile, specify the actors.
|Actors window (select Actions > Actors)||Actors window with examples from Onboarding profile:
3. Specify information about the to-be application's RuleSets, organization, base class names and structure, and standard operator IDs.
The system displays default values, which you can change as appropriate.
|Base and RuleSetsstep:
The displayed default values are based on the options specified in the Application Overview window, on the selected profile (if any), and on information about your operator ID's organization and division.
You can modify the default values to adjust them to meet the needs of your intended application. If you update a default value and a record corresponding to the updated values does not already exist in the system, it is created when the application is generated. For example, you can enter a new organization name, and the system creates that organization when it generates the application.
|Using the default values for our chosen |
Click Preview to see the class structure for the organization and framework layers:
4. Define and optionally update the work types, processes, case types, and case type structure.
If using a profile, confirm the work type, processes, and case types and structure from the profile are what you want, or update them as appropriate. If not using a profile, create the discovery maps and design the case type relationships as described in DCO 6.2 — Creating Application Profiles and Discovery Maps.
|Create Processes step - Discovery Map and Case Tree views||The example EquipmentRequest discovery map
5. Define and optionally update the work-related class structure.
The system displays default values based on the work types specified on the Create Processesstep.
When building a new application not built on another framework, all work types inherit from
Work-Cover. When building on, or updating an existing framework or application, you can select to have added work types inherit from classes in the existing framework or application.
||The following image shows an example of the Class Structure step for the NewHireCaseFW application with its specified work types grouped under shared-layer classes named |
Clicking the Preview button displays:
Note: Optionally, you can choose to have a class stored in its own, dedicated table in the PegaRULES database by selecting the Store Separately checkbox. When the application is generated, the system creates a class group rule and a table in the PegaRULES database for those classes that have Store Separately checked. This selection is useful when you want to have the ability to create reports using data in fields specific to a given work type or a group of related work types. Click the Help icon ( ) on this step in the accelerator for more details.
6. Specify work role-actor combinations.
Create a list of the role and actor combinations that specify how the actors participate in the processing of work in the application. When the accelerator generates the application, the system creates work party rules according to this list. Work parties can be associated with work items when the processes run.
|Roles step||In the NewHireCaseFW application, the HR Staff Member actor originates work items and the Hiring Manager actor approves them. The option Set to Current Operator is selected for the |
7. Review and optionally update use cases and requirements.
Confirm the use cases and requirements, or update them as appropriate.
|Project Explorer step||EquipmentRequest work type and use cases on the Project Explorerstep:
8. Review the to-be-generated rules and classes.
The tabs in this step list the rules and the base class structure the system will generate based on the items specified in the accelerator's steps. If you want to make a change before creating the application, click the accelerator step that specifies the information you want to update. After making the updates, click this Review Applicationstep again to review the changes.
|Review Application step||NewHireCaseFW example
Rules to Generate tab:
Class Structure tab:
9. Generate the application.
When you click Build the Application, the system generates the appropriate rules and classes, according to the lists in the Review Applicationstep. The system also updates your operator ID to add the access group for this new application, and set it as the default.
|Click Build the Application on the Review Applicationstep.
As the system builds a group of rules, an animated processing symbol () displays to track the build process. The system displays a checkmark when it finishes creating each group of rules. If a rule cannot be created, a warning message is displayed. Typically, a warning message indicates a duplicate record exists in the system.
When the system finishes creating the application structure, a set of checkmarks displays (indicating success).
|Example of progress completion after generating the NewHireCaseFW application:
To complete the accelerator work item, click Finish. The system displays the Switch to new application button. Click it to display the new application in the Designer Studio.
The Application Accelerator is dynamic — the system refreshes the available steps and fields based on selections that you make.
When the Application Accelerator starts, the system assigns and displays an ID. For example, the following image shows AA-21 in the Application Accelerator display:
On any step of the Application Accelerator, click the Help icon ( ) to display help about that step, including choices for fields and controls used in that step. In any secondary window opened from the Application Accelerator (such as the Application Overview window), click the window's Help icon ( ) to display help about the fields and controls used in that window.
The steps of the Application Accelerator are designed to guide you through the process of specifying the information the system needs to generate the base application. Click the step name to move to that step and specify the information associated with that aspect of the application or project area. For example, to specify the types of correspondence the to-be application is expected to send, click Correspondence. When a step has been visited once, it displays a green checkmark ().
You can work on the steps in any order, and optionally omit steps if they are not relevant to your project. If you selected an application profile when starting the accelerator, the system initially populates the accelerator steps with the relevant information from the profile, and you have the option of updating the specified values.
The following list provides short descriptions of what to use each step for. For more in-depth details of how to use the fields and controls on each step, see the online help () for that step.
- Base and RuleSets
- Use this step to specify:
- Class names and class structure for the application's organization class layers and framework class layer. (Click Preview to see the classes that will be generated based on the current specified values.)
- RuleSet names and RuleSet versions.
- Whether to create or modify the standard operators when the application is generated. The system can update the standard operator IDs (such as [email protected]) with the access group for the new application when the application is generated.
Which fields are displayed in this steps depends on the build options specified in the Application Overview window (Actions > Overview). This step initially displays default values based on:
- Options specified in the Application Overview window
- Information in your operator ID (for example, your organization and division)
- Information specified in the application profile selected in the Application Overview window (if any)
- Create Processes
- Use this step to:
- Define work types and their starting processes.
- Create visual maps of the processes using discovery maps
- Organize work types into structures of cases and subcases
This step has two distinct views: the Discovery Map view and the Case Tree view. You can toggle back and forth between the two views. Usually you choose which view to work in based on your situation and what you want to focus on. For example, if all of the work types and processes are already defined and you want to focus on building the case tree, choose the Case Tree view. If you are starting from scratch and want to focus on capturing the process for one work type, choose the Discovery Map view.
- Class Structure
- Use this step to specify how the work types (such as those specified in the Create Processes step) fit into the application's class structure, and to optionally specify shared layer classes and any parent-child relationships between the classes. (A shared layer is a class in which to define assets shared for reuse across multiple implementations.) For a particular class, click to edit the class name and set parent-child relationships between this class and other classes.
Important: By default, in a development system, each time you create a new class (including the default shared work layer) that has Store Separately selected, the system creates a corresponding table in the PegaRULES database and maps the class to the new table through a Database Table data instance. (In other words, the system creates a database table for each class group.) For example, when you create a new application using the Application Accelerator with the default shared layer class
GLBX-FW-PolicyApp-Work, the system creates a database table
pc_GLBX_FW_PolicyApp_Work. Use the Schema Change Tracking gadget on the System - Database landing page for a list of the automatically created tables in the PegaRULES database.
If the table already exists (for example, from an import process or from generating an application with the accelerator and immediately deleting it), the system creates a new database table with a random string appended in the name (such as
To temporarily disable this dedicated table creation feature, before generating the application, update the Dynamic System Settings rule named database/AutoDBSchemaChanges to set the value to
false(instead of the default value of
true). When the system generates the application, it maps the class groups to the pc_work table. Remember to set the value of the database/AutoDBSchemaChanges rule back to true after generating the application. Otherwise, certain wizards that rely on schema changes (such as the Property Optimization tool, Property Optimization dashboard, and making schema changes during the import process) are disabled.
- Use this step to specify reporting for the application. When the application is generated, the system creates the appropriate rules according to this list.
- Correspondence includes all types of notification used by the application including letters, emails, and faxes. On this step, you indicate the level of correspondence (high or low) this application requires. Use this step to specify pieces of correspondence for the application. When the application is generated, the system creates correspondence rules according to this list.
- This step appears if you are creating a new application. Use this step to specify a list of role and actor combinations that specify how the actors participate in the processing of work in the generated application. When the application is generated, the system creates work party rules according to this list. Work parties can be associated with work items when the process runs.
- Other Extensions
- This step appears if you are creating a new application built on an existing framework that has rules, other than reports and correspondence rules, marked as extensions. (Reports and correspondence rules that are marked as extensions in the framework are listed in the Reporting and Correspondencesteps).
Use this step to specify whether to copy over the framework's extension rules into the generated application.
- Project Explorer
- Use this step to examine use cases, requirements, work types, and supporting use case types already defined for the application, and optionally modify their details, delete them, or add new ones.
- Review Application
- Use this step to:
- Review the to-be-generated rules and class structure of the application before creating the application in the system.
- Create the application (using the Build the Application button).
The to-be-generated rules and class structure are displayed in this step. Their names and types are determined by the selections specified in the steps of the accelerator. When you click Build the Application, the system generates the application with the listed rules and class structure.
Use the Actions menu's choices (actions) to:
- Provide input about the overall application to be generated (such as its type).
- Perform actions related to this run of the accelerator, such as saving the current state to resume later, or withdrawing this run of the accelerator.
|Create a list of actors who perform work in the application. Actors referenced in use cases are entered here.|
|Specify information about the type of application to be generated. Note: Changing the Application Overview information in this screen while in the process of completing the accelerator work object can result in the removal of previously entered information.|
|Save work in progress before you exit a window or the accelerator.
Best practice tip: Use this action to periodically save your work in progress whenever you enter information into the accelerator. While the system automatically saves detail entered in an accelerator step as you move from that step to another, periodically saving your work is helpful on steps where you are entering large amounts of data over a period of time (such as when working on the Create Processes or Project Explorer steps).
|Withdraw the accelerator work object.
When you no longer want this run of the accelerator and want to remove it (for example, a trial run used to test some choices), use this action to resolve and withdraw the accelerator work object. After the Withdraw action, this run of the accelerator cannot be used to generate an application.
Sometimes you generate an application, and then want to immediately delete it and start over. The accelerator displays a Delete button on the build and confirmation screens after the rules are created. The Actions menu displays a Deletechoice when a resolved accelerator object is reopened.
Delete button next to the Finish button after the rules are generated:
Delete choice in the Actions menu:
To delete the generated application after generation:
- Click Delete. The system opens a window and displays the list of the rules that were created when the application was generated.
- Click Delete All Listed Objects. The system begins deleting the rules starting at the beginning of the list. An animated symbol () displays to track the deletion progress.
- When a checkmark displays next to each rule in the list, indicating that all of the objects have been deleted, click Close.
At this point, it is recommended to log off the system and log back in, so that the appropriate default application for the operator is displayed in the Designer Studio.
To delete the auto-generated table, use the Optimize Schema gadget on the System - Database landing page. Expand the View the unused tables section to see the tables unassociated with any class in the system. Then select the appropriate tables to delete, and click Proceed with Changes.