Using project management features supported by Process Commander, the Project Management Framework allows you to identify, track, and update the progress of development tasks and bug fixes associated with projects created and managed in the framework.
Using project management features supported by Process Commander, the Project Management Framework allows you to identify, track, and update the progress of development tasks and bug fixes associated with projects created and managed in the framework. Real time updates are passed from the development system to PMF.
Part of the process of installing PMF is loading the PegaCESvcs RuleSet into the development system(s) where you build or make changes to applications associated with projects. The RuleSet supports the structure required to implement the communication link between the two systems to pass and track development updates.
To set up the connectivity between PMF and a development system, perform the following steps:
Step 1: Create a RuleSet and a development application layer
For each application where you want to make updates and track development activity, it is a good practice to create:
- an additional application layer that is built on the primary application
- an additional RuleSet for storing new and modified rules
Having a separate application rule and RuleSet gives you the flexibility to manage development work independently of your primary application's rules and validate changes without impacting the integrity of the previous development iterations. This also allows you to package and migrate changes to the primary application, production and other systems without moving the entire application configuration.
In the following steps, the phrase primary application refers to the existing application and the phrase development application layer refers to the development application where you build your changes.
a. Create a RuleSet to store the primary application's development rules
For development systems on V6.1 SP1:
- From the Rules Explorer, select SysAdmin > RuleSet > New.
- Enter a name and tab to the next field. The system provides default values for the version and description.
- In the Requires RuleSet and Versionssection, replace the system default with the name of the primary application's RuleSet and version.
For example, if your primary application's RuleSet and version is OrderEntrySystem:02-03, replace the pre-filled Pega-ProcessCommander value with OrderEntrySystem:02-03.
Note: Do not choose to update your current application with this new RuleSet.
- Click Create, then Click.
For development systems on pre-V6.1 versions:
- In the Rules Explorer, select SysAdmin > RuleSet > New.
- Enter a name and click Create. Click the Save icon to save the RuleSet.
- In the Rules Explorer, in the SysAdmin category, right-click RuleSet Version and select New.
- Select the name of the RuleSet you just created and enter a version number. Click Create.
- In the Requires RuleSet and Versionssection, enter the name of the primary application's RuleSet and version.
For example, if your primary application's RuleSet and version is OrderEntrySystem:02-03, enter OrderEntrySystem:02-03.
b. Create a new application rule that is built on your primary application
- In the Rules Explorer, in the Application Definition category, right-click Application and select New.
- Enter a name and version for this testing application. For example, if your primary application is named OrderEntrySystem, create a new development application named OrderEntryDev. Click Create.
- Enter the built-on application and RuleSet information on the General tab (for V6.1 and V5.5 systems) or on the Definitiontab (for 5.4 systems):
- In the Built on Application field, select the primary application.
- Check the Include Parent check box.
- Add the RuleSet that you created for holding development work to the Application RuleSets list.
- Add the PegaCESvcs RuleSet for the system version to the Component and Shared RuleSetslist.
System Version Located on RuleSet V6.1 SP1 General Tab PegaCESvcs:06-01 V5.5 SP1 General Tab PegaCESvcs:05-05 V5.4 SP2, V5.4 SP3 Manage Tab PegaCESvcs:05-04
- Enable the Project Management function.
For V6.1 SP1 and V5.5 SP1 application rules, check the Enable Project Management box on the Advanced tab.
For V5.4 SP2 or V5.4 SP3 application rules, check the Enable Project Management box on the Manage tab.
Note: When you check the box, a link to a Declare page called ProjectMgmt displays. There is no need to update values on this page. These are preset for initial use when the communication link is installed.
Repeat these steps for other development applications you add to your primary application.
See help topic: About Application rulesfor additional information.
Step 2: Create access groups to the development application
In the primary application, give access to operators that you want to work in the development application.
- Create a new access group. Enter a name that is related to the development application. For example, if the development application is named OrderEntryDev, the access group name could be OrderEntrySystemDev.
- In the Access Group form, select the development application and version.
- Save the rule.
- Update the operator IDs with the new access group.
Repeat the steps to give access to the other development applications.
See online help topic: About Access Group data instancesfor additional information.
Step 3. Enable the Communication Link Between PMF and the Development System
During installation of the communication link, a dynamic system setting called Pega-RULES.ProjectManagementFW is added to the development system. This rule specifies the URL of the framework and activates SOAP connectivity that is preconfigured in PMF.
The connection pulls the project tasks and bug assignments that have been assigned to development resources over to the development system.
To enable the link:
- From the Class Explorer, select Data- > Admin- > System > Settings.
- Select the Pega-RULES.ProjectManagementFW instance.
- Enter the URL of the framework SOAPServlet in the Value field on the Settings tab.
Step 4. Synchronize Project Resources with Operators in the Development System
Operator IDs set up in the framework as project resources to work project tasks and bug fixes must have the same Operator ID in the development system where the work is performed. This enables the development system to query the framework when an operator signs on and pull back a list of bugs and tasks assigned to that operator and display them in the Project Explorer area of the portal.
If Operator IDs are not the same, either add the operators to your development system or modify their IDs in the framework.
See Tracking Development Activity in a Project for details about how the framework tracks and reports development progress.
This article links to the following articles describing features and functions of the PMF 6.1.1 release.
Select one of the following links to connect to a group of articles specific to working with Scrum or SmartBPM projects in PMF.
Return to About the Project Management Framework