pega community | training & resources for pega developers ......such examples are fictitious and...

Agile Studio

WORKING WITH DEVELOPMENT SYSTEMS ON

PREVIOUS PEGA PLATFORM RELEASES 7.4

© 2018 Pegasystems Inc., Cambridge, MA

All rights reserved.

Trademarks

For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks or service marks are property of their respective holders.

For information about the third-party software that is delivered with the product, refer to the third-party license file on your installation media that is specific to your release.

Notices

This publication describes and/or represents products and services of Pegasystems Inc. It may contain trade secrets and proprietary information that are protected by various federal, state, and international laws, and distributed under licenses restricting their use, copying, modification, distribution, or transmittal in any form without prior written authorization of Pegasystems Inc.

This publication is current as of the date of publication only. Changes to the publication may be made from time to time at the discretion of Pegasystems Inc. This publication remains the property of Pegasystems Inc. and must be returned to it upon request. This publication does not imply any commitment to offer or deliver the products or services described herein.

This publication may include references to Pegasystems Inc. product features that have not been licensed by you or your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems Inc. services consultant.

Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors, as well as technical inaccuracies. Pegasystems Inc. shall not be liable for technical or editorial errors or omissions contained herein. Pegasystems Inc. may make improvements and/or changes to the publication at any time without notice.

Any references in this publication to non-Pegasystems websites are provided for convenience only and do not serve as an endorsement of these websites. The materials at these websites are not part of the material for Pegasystems products, and use of those websites is at your own risk.

Information concerning non-Pegasystems products was obtained from the suppliers of those products, their publications, or other publicly available sources. Address questions about non-Pegasystems products to the suppliers of those products.

This publication may contain examples used in daily business operations that include the names of people, companies, products, and other third-party publications. Such examples are fictitious and any similarity to the names or other data used by an actual business enterprise or individual is coincidental.

This information is the property of:

Pegasystems Inc. One Rogers Street Cambridge, MA 02142-1209 USA Phone: (617) 374-9600 Fax: (617) 374-9620 www.pega.com

Agile Studio

Document: Working with Development Systems on Previous Pega Platform Releases

Software Version: 7.4

Updated: May 2018

CONTENTS

Introduction .................................................................................................... i

Working with Agile Studio from Pega 7, 7.1, 7.2, and 7.3 development environments ................................................................................................. 2

System administrators: Setting up a connection to a Pega 7, 7.1, 7.2, or 7.3 development system ....................................................................................... 2

Connecting to a Pega 7, 7.1, 7.2, or 7.3 development system ............... 2

All users: Viewing your work for a Pega 7, 7.1, or 7.2 development system3

All users: Viewing your work for a Pega 7.3 development system .............. 4

All users: Recording your effort ...................................................................... 5

Working with Agile Studio from PRPC 6.3 development environments ... 8

System administrators: Setting up a connection to 6.3 development systems........................................................................................................................... 8

Task 1: Setting up the connection and enabling project tracking .......... 8

Task 2: Creating an access group and enabling feedback ...................... 9

System administrators: Customizing Direct Feedback settings in all Pega versions (optional) .......................................................................................................... 9

Option 1: Changing the type of work object the feedback creates ..... 10

Option 2: Linking the feedback to projects ........................................... 11

Option 3: Adding email validation .......................................................... 12

All users: Viewing your work ......................................................................... 14

All users: Recording your effort .................................................................... 14

All users: Using the pushpin to send feedback (Pega versions 7.2 and lower)......................................................................................................................... 16

Working with Agile Studio from PRPC 6.2 development environments . 19

System Administrators: Setting up a connection in a 6.2 development system......................................................................................................................... 19

Task 1: Specifying the Agile Studio URL .................................................. 19

Task 2: Creating a ruleset and application layer .................................... 19

Task 3: Creating an access group and enabling feedback .................... 21

Enabling the operator to use Direct Feedback (optional) .................... 21

System administrators: Customizing Direct Feedback settings (optional) 22


All users: Recording your development effort ............................................ 24

All users: Using the pushpin to send feedback ........................................... 26

Working with Agile Studio from PRPC 6.1 development environments . 27

System administrators: Setting up a connection in a 6.1 SP1 or 6.1 SP2 development system ..................................................................................... 27

Task 1: Specifying the Agile Studio URL .................................................. 27

Task 2: Creating a ruleset and application layer .................................... 28

Task 3: Creating an access group and enabling feedback .................... 29

System administrators: Customizing Direct Feedback settings (optional) 30


All users: Recording your development effort ............................................ 32

All users: Using the pushpin to send feedback ........................................... 34

Working with Development Systems on Previous Pega Platform Releases 1

This guide is designed to help users developing on previous versions of the Pega Platform to effectively use Agile Studio 7.4. It assumes that you have installed Agile Studio 7.4 on Pega Platform 7.4.

Use this guide to understand how to view your Agile Studio worklist in Designer Studio, record your development efforts against your Agile Studio worklist, and relate rule changes made during development to Agile Studio work items.

Furthermore, system administrators can use this guide to set up a connection from a development environment to Agile Studio 7.4. For applicable releases, the guide describes how to customize the handling of feedback items created directly in the development environment.

This document is divided into the following chapters:

• Working with Agile Studio from Pega 7, 7.1, 7.2, and 7.3 development environments

• Working with Agile Studio from PRPC 6.3 development environments



Introduction


This section describes how to connect your development environment to Agile Studio 7.4, view your Agile Studio worklist in Designer Studio, and associate rule changes with the tasks and bugs on your worklist.

System administrators: Setting up a connection to a Pega 7, 7.1, 7.2, or 7.3 development system

You can skip this step if your development system is not built on Pega 7 or you are not planning to connect to a system.

These steps establish a connection between your Pega 7 development environment and Agile Studio. This connection allows developers to view and manage user stories and bugs from the Designer Studio of the development system and associate rule changes with the user stories and bugs on their worklist.

All connection setup tasks are performed in your development system. Repeat the setup process in each development system where you are planning to track and monitor project work.

In Pega 7 systems, you can use the Project Management landing page to do the following:

• Set up the Agile Studio URL connections between your applications and Agile Studio and test their connectivity

• Enable project tracking and feedback setup for operators who perform development work in the applications they are able to access

• Align the feedback with a product associated with that application in Agile Studio

Connecting to a Pega 7, 7.1, 7.2, or 7.3 development system 1. Select the Designer Studio System > Settings > Project Management landing page option.

2. In the PMF CONNECTION DETAILS section, enter the URLs needed to establish connectivity between the application and Agile Studio.

In the PMF URL field, enter the URL of your Agile Studio instance. In the PMF SOAP URL field, enter the SOAP URL that passes project tracking data to and

from an application to your Agile Studio instance. 3. Click Save Connection Details.

4. Click Test Connectivity to test the connection.

Working with Agile Studio from Pega 7, 7.1, 7.2, and 7.3 development environments


TITLE of INTERNAL DOCUMENT – Arial Bold 12 pt

5. In the APPLICATION SETTINGS section, you can do the following: enable project tracking to associate rule check-in with an Agile Studio item in each application that your developers can access, enable development feedback, and associate an Agile Studio product with an application.

The APPLICATION (VERSION) column shows a list of the applications you can access.

On Pega versions 7.2 and lower, select the check box in the FEEDBACK column to enable feedback. On Pega versions 7.2.1 and higher, leave the FEEDBACK check box unchecked and install the Smart Feedback component downloadable from Pega Exchange to enable Smart Feedback. When Smart Feedback is enabled, a "Send us feedback" option will appear under the operator menu.

Select the check box in the PROJECT TRACKING column of each application that you want to enable. If the application is locked, the Supply Password field displays in a separate window. Enter the password and click OK to continue with the save.

Use the PMF PRODUCT column to select and associate an Agile Studio product with an application. If you choose this option, when a Feedback item is entered from the application, it is added to the Feedback tab of that product in Agile Studio. You can also add a product to Agile Studio by clicking the “plus” icon to the right of the column and entering the product. For Smart Feedback, if the PROJECT TRACKING check box is selected but the PMF PRODUCT column is blank, the smart feedback will be assigned to PRD-1.

All users: Viewing your work for a Pega 7, 7.1, or 7.2 development system If your current development application is enabled to communicate with Agile Studio, the following changes appear in the Designer Studio when you sign into that system:

• A preference is available that allows you to enter your Agile Studio User ID in the Project Management section of your User Preferences menu. Use this to enter you Agile Studio User ID if it is different from your development user ID. If you do not set this value, it is assumed that your development and Agile Studio IDs are an exact match.

This ID is used to pull in your worklist from Agile Studio so that it can be viewed from the Designer Studio, and you can select items from the worklist to associate with your rule changes.

• Clicking View PMF worklist in new window displays at the bottom of the Pega task display of the Designer Studio Home tab. This window displays the tasks, issues, bugs, and user stories currently assigned to you in Agile Studio.

Expand a row to view the full description of an item.

https://pdn.pega.com/exchange/components/smart-feedback



• Click an item ID to display the item in a window. If you are not logged into Agile Studio, you will be prompted to enter your credentials before the item displays.

• Click View Recent Feedback to view a list of recent feedback items created in Agile Studio for the product that is associated with your application.

• Click View Changes to display a list of your rule changes that have been associated with your assigned tasks, issues, user stories, and bugs. You can also view a list of all rule changes in your application that are associated with a bug, user story, issue, and task ID.

• Click Open PMF to launch an Agile Studio session in a new window.

• Click the “Refresh” icon in the top right corner of your screen to refresh the worklist with new work from Agile Studio and delete work that you have completed since the last time you signed onto the development system.

All users: Viewing your work for a Pega 7.3 development system If your current development application is enabled to communicate with Agile Studio, the following changes appear in Designer Studio when you sign into that system:

• A preference is available that allows you to enter your Agile Studio User ID in the Project Management section of your User Preferences menu. Use this to enter you Agile Studio User ID if it is different from your development user ID. If you do not set this value, it is assumed that your development and Agile Studio IDs are an exact match.

• Users will see a worklist from Agile Studio in Designer Studio after checking in rules. The worklist is not available in the Designer Studio Home tab.

• Currently, the following warning is on the Project Management landing page: “Integration with the Project Management Framework is deprecated. You can set up integration with another project management tool from the Integration & security tab of the Application rule form.” This warning refers to Integrating Agile Workbench with Agile Studio 7.3.1 or higher versions. However, Agile Workbench integration between Pega Platform 7.3 and Agile Studio 7.3.1 or higher is not supported. Users need to upgrade Pega Platform from 7.3 to 7.3.1 or higher.



All users: Recording your effort for a Pega 7 and 7.1 development system From the New Rule, Save As, and Check-in screen for rules in the Designer Studio you can do the following:

• Select the task, issue, bug, or user story you are working on from the drop-down list.

• In the Additional Worked field, enter the amount of time you have spent in hours since your last update. When this information is submitted, this value is added to the Actual Hours on the item.

• Update the Remaining Hours field to reflect the valance of the effort that is needed to complete the item. When this item is submitted, this value replaces the Remaining Hours value on the item.

• In the Note field, enter your development details.

• When you check in a rule, you can record the Additional worked and update the Remaining hours field. You can also flag the task, issue, or bug as complete by checking the work complete box. In this case, you enter only your Additional worked time. Checking the box resolves the item in Agile Studio and removes the task from the list.

Note: You cannot mark a user story as complete during check-in. It must be processed directly in Agile Studio.

Check-in example



All users: Recording your effort for a Pega 7.2 and 7.3 development system

From the New Rule, Save As, and Check-in screen for rules in the Designer Studio you can do the following:

• Select the task, issue, bug, or user story you are working on from the drop-down list.

• In the Additional time spent field, enter the amount of time you have spent in hours since your last update. When this information is submitted, this value is added to the Actual Hours on the item.

• Update the Remaining time field to reflect the valance of the effort that is needed to complete the item. When this item is submitted, this value replaces the Remaining Hours value on the item.

• In the Note field, enter your development details.

• When you check in a rule, you can record the Additional time spent and update the Remaining time field. You can also flag the task, issue, or bug as complete by checking the work is complete box. In this case, you enter only your Additional time spent time. Checking the box resolves the item in Agile Studio and removes the task from the list.

Note: You cannot mark a user story as complete during check-in. It must be processed directly in Agile Studio.

Check-in example



System administrators: Setting up a connection to 6.3 development systems

These steps establish a connection between your PRPC 6.3 or 6.3SP1 development environment and Agile Studio. This connection allows developers to view and manage user stories and bugs from the Designer Studio of the development system and associate rule changes with the user stories and bugs on their worklist.


The following tasks are required and should be performed in the order listed:

• Task 1: Setting up the connection and enabling project tracking

• Task 2: Creating an access group and enabling feedback

Task 1: Setting up the connection and enabling project tracking

In PRPC 6.3 systems, the Project Management landing page allows you to set up the Agile Studio URL connections between your applications and Agile Studio, test that connectivity, and enable project tracking for operators who perform development work in the applications they can access.

1. Select the Pega icon > System > Settings > Project Management.

2. In the Connection Details section, enter the URLs needed to establish connectivity to Agile Studio.

In the PMFURL field, enter the URL of your Agile Studio instance. In the PMF SOAP URL field, enter the SOAP URL that passes project tracking data to/from an

application to your Agile Studio instance. Click Save the Connection.

3. In the Application Project Settings section at the bottom of the page, enable and disable project tracking for applications your developers can access. To enable an application, it must be present in your operator's access group.

The Application (Version) column defaults to a list of applications you can access. For each application you want to enable:

Working with Agile Studio from PRPC 6.3 development environments



Select the Project Tracking Enabled check box. Click the Save icon. If the application is locked, the Supply Password field appears in a

window when you click Save. Enter the password and click OK to continue with the save. Repeat these steps for each

application.

Task 2: Creating an access group and enabling feedback You can enable the Direct Feedback function for operators if you want users of the development system to enter and submit feedback about bugs, issues, or configuration and enhancement ideas directly to Agile Studio using the Pushpin icon. This is an optional setup step.

In addition to your development systems, the Direct Feedback feature can be enabled in production and test applications to pass feedback to Agile Studio.

Creating the access group

1. From the Rules Explorer, select Security > Access Group.

2. Select an existing instance or click New to create a new instance.

3. Enter an Access Group Name that represents the development application you previously created.

4. On the Layout tab, select the development Application Name and Version.

Enabling the operator to use Direct Feedback (optional)

1. On the Layout tab, add PegaRULES:Feedback as a Role.

This access role activates the feedback feature. When users have this role in their access group, it adds the Pushpin icon to their portal.

2. Click the Save icon.

3. Add the access group to operators who require access to the development application.

4. Repeat this process if you want to create additional access groups to provide access to other applications in the development system.

Click the Help icon on the rule form for more information about configuring access groups.

System administrators: Customizing Direct Feedback settings in all Pega versions (optional)

Skip this configuration process if your development system is on Pega 7.1 or higher. This process only applies to Pega versions 6.x and 5.5.



If Agile Studio is connected to your development environment and a user submits feedback using the pushpin icon, it is configured to do the following:

• Create an FDBK item

• Send an email to the email address of the user who submits the feedback

To change this behavior, customize the feedback configuration by changing the default options listed below. You perform these customizations in Agile Studio and not in your development system where you enabled the pushpin to submit feedback.

Option 1: Changing the type of work object the feedback creates Agile Studio is configured to create an FDBK work object when a feedback item is received from a system enabled for feedback and connected to Agile Studio. Alternatively, you can choose to have Agile Studio create a BUG work object anytime new feedback is received.

A decision table named DetermineTargetClass in the PegaProjectMgmt ruleset determines the type of work object that is created. Change the default behavior to create a bug item by creating a customized version of the decision table.

1. In the search field, type DetermineTargetClass. Select the PegaProjMgmt-Work class instance.

2. Save it to your Custom Ruleset, but do not change the name of the rule.

3. On the Table tab, locate the FDBK work type. Click the Actions column in that row to change the value from Declare_PM_Implementation.WorkClassFeedback to Declare_PM_ Implementation.WorkClassBug.


Click the Help icon in the rule form for more information about configuring decision tables.



Option 2: Linking the feedback to projects Feedback can be configured to link feedback from the sending application to projects using property values. Use this option only if you used the previous step to change the work type to a Bug item.

A decision tree named DetermineInitialGroup in the PegaProjectMgmt ruleset specifies the logic that decides which project to associate the incoming feedback message with. To change this default logic, create a customized version of the decision tree.

1. In the search field of the Designer Studio, type DetermineInitialGroup. Select the PegaProjMgmt-Work class instance.


3. On the Results tab, enter your return values in the Allowed Results list. These will be referenced in the next step.

Click the Expand arrow icon to expand the display for each result. For each property in the list, update the Project ID that appears in the Value field.

4. On the Decision tab, update the logic that maps an incoming message property to a return result that you entered on the Results tab.



The following table lists the recommended feedback message properties you can use in your mapping logic to evaluate the feedback message. These properties are sent in the feedback message from the development server by the SOAP service used to submit the direct feedback via the Pushpin icon. When Agile Studio creates the work item, the properties are added to it.

Property name Description GenericWorkForInt.BuildData.ApplicationName Name of the application on the sending

server GenericWorkForInt.BuildData.ApplicationVersion Version of the application on the sending

server GenericWorkForInt.Category The category value selected by the operator

submitting the feedback from the drop-down list on the pushpin pop-up window. Choices are: General, Usability, User Interface, Process Improvement, Policy Decision

GenericWorkForInt.ReportedByDivision Organization division of the operator who submitted the feedback

GenericWorkForInt.ReportedByOrg Organization of the operator who submitted the feedback

GenericWorkForInt.ReportedByWorkgroup Work group of the operator who submitted the feedback


Click the Help icon on the rule form for more information about configuring decision trees.

Option 3: Adding email validation When Agile Studio receives a feedback message, it sends an email to the person who submitted the feedback.

A decision tree named ValidEmailAddressesforCorr in the PegaProjectMgmt ruleset specifies the logic that decides whether to send email in response to the feedback based



on the email address of the sending operator. To change this default logic, create a customized version of the decision tree.

1. In the search field, type ValidEmailAddressesforCorr. Select the PegaProjMgmt-Work class instance.


3. On the Decision tab, update the circumstance logic for sending the feedback email based on the email address.

You can enter specific email addresses or use a contains evaluator to include or exclude domain names. For example, send an email if the email contains YourCompany.com; otherwise, do not send an email.

The Otherwise option is the default for any email address that does not meet any of the criteria.

Return true for circumstances where you want to send an email. Return false for circumstances where you do not want to send an email.


Click Help on the rule form for more information about configuring decision trees.



All users: Viewing your work If your current development application is enabled to communicate with Agile Studio, the following changes appear in the Designer Studio when you sign on to that system.

• A preference is available that allows you to enter your Agile Studio User ID in the Tools section of your User Preferences menu. Use this to enter your Agile Studio User ID if it differs from your development user ID. If you do not set this value, it is assumed that your development and Agile Studio IDs are an exact match.

• A My Project Worklist section is added to your home tab. This list shows the tasks, issues, bugs, and user stories currently assigned to you in Agile Studio.

• Expand a row to view the full description of the item.

• Click an item ID to display the item in a pop-up window. If you are not logged into Agile Studio, you are prompted to enter your credentials before the item displays.

• Click View Changes to display a list of your rule changes that have been associated with your assigned tasks, issues, user stories and bugs. You can also view a list of all rule changes in your application that are associated with bug, user story, issue, and task IDs.

• Click Open PMF to launch an Agile Studio session in a new window.

• Click the Refresh icon to refresh the worklist with new work from Agile Studio and delete work that you have completed since the last time you signed on to the development system.

All users: Recording your effort 1. Select the task, issue, bug, or user story you are working on from the drop-down list.

2. In the Additional Worked field, enter the amount of time you have spent in hours since your last update. When this information is submitted, this value is added to the Actual Hours on the item.

3. Update the Hours Remaining field to reflect the balance of the effort that is needed to complete the item.

When this information is submitted, this value replaces the Remaining Hours on the item.

4. In the Note field, enter your development details.

When you check in a rule, you can record the Additional Worked and update the Hours Remaining. You also can flag the task, issue, or bug as complete by checking the Task Complete box. In this case, you enter only your Additional Worked time. Checking the box resolves the item in Agile Studio and removes the task from your Project Explorer list.

Note: You cannot mark a user story as complete during check-in. They must be processed as complete directly in Agile Studio.



New and Save As example



Check-In examples

All users: Using the pushpin to send feedback (Pega versions 7.2 and lower)

When the Direct Feedback feature is enabled in a development application, a pushpin icon appears on your portal. You can drag and drop it on the desktop, enter a description of the problem or issue, capture a screenshot, and send it as a message to Agile Studio over a communication link set up between the two systems.

Like feedback items entered directly into Agile Studio, these items become FDBK- items where they are triaged and either assigned to a project or the backlog for a product or release as a user story, task group, bug, or issue, or they can be rejected.



1. Click the pushpin icon and drag it to the area on the screen that you are describing in the feedback. The pop-up window where you enter the feedback appears.

A screenshot is captured if you are using Internet Explorer 8 or 9. When a screenshot is captured it includes the entry window. Position the box so the area of the screen you want to reference is not hidden by the box.

2. Enter your feedback text describing the scenario or problem in as much detail as possible.

3. Select a feedback Category that best describes the application area related to the feedback.

If you are using Internet Explorer 8 or 9, the Include Screenshot box is selected by default. Deselect it if you do not want to capture a screenshot in the feedback message.

4. The email address in your operator profile populates the From field.

5. Click Send.

6. If the Include Screenshot box is checked, the shot is captured and a pop-up window displays to notify you when the capture is complete. Click OK to close it.

When the message is sent over the communication link, Agile Studio does the following:

• Creates a FDBK item and associates it with a product based on the application you were logged into when you used the pushpin

• Routes the feedback to a workbasket for triage

• Adds the feedback entry details and the build information captured from the sending application to the Details tab of the item that includes the Application Name, Version, and Build ID

• Sends you an acknowledgment email that the FDBK item was created



• Adds the screenshot to the item and a copy of the acknowledge email it sends you to the Attachments list of the item

• Adds the name of the person who created the item to the PEOPLE tab of the item; if the person who created the item is a user in Agile Studio, it adds that person as a Follower of the item

• Displays the item on the Feedback tab of the product associated with the feedback item


System Administrators: Setting up a connection in a 6.2 development system These steps establish a connection between your PRPC 6.2SP1 or 6.2SP2 development environment and Agile Studio. This connection allows developers to view and manage user stories and bugs from the Designer Studio of the development system and associate rule changes with the user stories and bugs on their worklist.


The following tasks are required and should be performed in the order listed.

• Task 1: Specifying the Agile Studio URL

• Task 2: Creating a ruleset and application layer


Task 1: Specifying the Agile Studio URL As part of the Agile Studio install, the step that installs the communication link between Agile Studio and your development system adds a Dynamic System Settings rule named Pega-RULES.ProjectManagementFW. This rule specifies the Agile Studio SOAP Servlet URL.

Enabling the communication link in your development system 1. Log in to the development system as a user with system administrator security.

2. From the Class Explorer, click Data > Admin > System > Settings.

3. Select the Pega-RULES.ProjectManagementFW instance.

4. On the Settings tab, enter the URL of your Agile Studio SOAP Servlet in the Value field.


Task 2: Creating a ruleset and application layer For development systems installed on PRPC 6.2 SP1 and 6.2 SP2, and for every application on your development server in which project resources perform project tasks and bug fixes or you want to enable Direct Feedback, create the following:

• An additional ruleset for storing new and modified rules in that application

• An application rule built on the primary application rule




Creating a separate ruleset and application rule gives you the flexibility to export rules without moving your Agile Studio and Direct Feedback configuration.

In the following configuration steps, the term primary application refers to the existing application, while development application refers to the application in which you are implementing the project changes.

Creating the ruleset

1. From the Rules Explorer, expand the Sysadmin category. Right-click RuleSet and select New.

2. In the Name field, enter a name for the ruleset and tab to the next field.

The system defaults values in the Version and Description fields.

3. In the Requires RuleSet and Versions section, replace the default value with the primary application's ruleset and version.

4. Leave the “Update your current application to include this new version” check box blank.

5. Click Create.


Creating the application rule

1. From the Rules Explorer, expand the Application Definition category. Right-click Application and select New.

2. Enter a Name and Version. Select the name of the ruleset you created and click Create.

3. On the General tab:

In the Built on Application field, select the primary application and version. Select the Include Parent check box. Add the ruleset you created to the Application RuleSets list.




Click the Help icon on the rule form for more information about configuring application rules.

Enabling the link

Project management functionality is enabled when you indicate that you want to enable the communication link between Agile Studio and your development system. This is done by selecting a check box in a topmost application rule of your development system. Agile Studio tracking can be enabled on one or more applications on your development environment.

1. Open the Application rule.

2. On the Advanced tab, select the Enable Project Management check box.


Task 3: Creating an access group and enabling feedback

For development systems installed on PRPC 6.2 SP1 and 6.2 SP2, after you create the new application layer, the project resources who perform the development work on project tasks and bug fixes in the application must be given access to it.

This is done by creating an access group that references the application and version where the work is taking place and then updating the operator record with that access group.

At the same time, you can enable the Direct Feedback function for operators if you want users of the development system to enter and submit feedback about bugs, issues, or configuration and enhancement ideas directly to Agile Studio using the pushpin icon. This is an optional setup step.




2. Select an existing instance or click the New icon to create a new instance.

3. Enter an access group name that represents the development application you previously created.


Enabling the operator to use Direct Feedback (optional) 1. On the Layout tab, add PegaRULES:Feedback as a Role.



This access role activates the feedback feature. When users have this role in their access group, it adds the pushpin icon to their portal.



4. Repeat this process if you want to create additional access groups to provide access to other applications in the development system.


System administrators: Customizing Direct Feedback settings (optional)

Customizing Direct Feedback settings for PRPC 6.2 development systems is done in the same way as for PRPC 6.3 systems. For more information, see System Administrators: Customizing Direct Feedback settings in all Pega versions (optional).

All users: Viewing your work If your current development application is enabled to communicate with Agile Studio, the following changes appear in the Designer Studio when you sign on to that system.

• A Project Explorer is added to the explorer list.

− When the explorer is in focus, the navigation panel lists the projects and user stories containing the tasks or bugs assigned to you. You can toggle between them as you work on different assignments.

− When you perform work on a task or bug and update the Project Management section of a New, Save As, and Check-In rule form, the navigation panel for the project or user story is populated with those rules. A tree display is visible where you can view and access the rules that have been added or modified as part of the development work.



• The Application menu on your portal header is populated with three project options. These options can appear grayed out and unavailable to you. Typically, this happens when there are no tasks or bugs directly assigned to you for any project. It also happens when your operator ID does not match your operator ID in Agile Studio.



Project options

• Select Switch Project to toggle between projects and backlogs when there is more than one project or backlog with tasks and bugs assigned to you. The item you select becomes your default parent in the Project Management section of the rules you add or update.

• Select View Worklist to display the list of tasks and bug items currently assigned to you.

• In PRPC 6.2, this option replaces Project Tasks that display in systems built on 6.1 and earlier.

• Expand a row to display descriptive detail of the assigned work.

• Click Export to Excel to export the list to an Excel spreadsheet.

• Click the Rule Changes tab to display a list of your rule changes that have been associated with your assigned tasks and bugs. This tab is only available in PRPC 6.2 and higher. You can also view a list of all rule changes in your application that are associated with bug and task IDs.

• Select Refresh Tasks to refresh your worklist with new assignments from Agile Studio and delete work that has been completed since the last time you signed onto the development system.

All users: Recording your development effort Your current project, backlog, sprint, or user story defaults in the Project ID field. If you want to record work against a different parent, use the Switch Project option from the application menu.

1. Select the Task Group and the Task you are working on from the dropdown list.

2. In the Additional Worked field, enter the amount of time you have spent in hours since your last update.

When this information is submitted, this value is added to the Actual Hours on the task or bug.

3. Update the Hours Remaining field to reflect the balance of the effort that is needed to complete the task or bug.

When this information is submitted, this value replaces the Remaining Hours on the task or bug.


5. When you check-in a rule, you can record the Additional Worked and update the Hours Remaining. You also can flag the task or bug as complete by checking the Task Complete



box. In this case, you enter only your Additional Worked time. Checking the box resolves the item in Agile Studio and removes the task from your Project Explorer list.




Check-In examples

All users: Using the pushpin to send feedback Customizing Direct Feedback settings for PRPC 6.2 development systems is done in the same way as for Pega 7 systems. For more information, see All users: Using the pushpin to send feedback (Pega versions 7.2 and lower).



System administrators: Setting up a connection in a 6.1 SP1 or 6.1 SP2 development system

These steps establish a connection between your PRPC 6.1SP1 or 6.1 SP2 development environment and Agile Studio. This connection allows developers to view and manage user stories and bugs from the Designer Studio of the development system and associate rule changes with the user stories and bugs on their worklist.


The following tasks are required and should be performed in the order listed.

• Task 1: Specifying the Agile Studio URL

• Task 2: Creating a ruleset and application layer


Task 1: Specifying the Agile Studio URL As part of the Agile Studio install, the step that installs the communication link between Agile Studio and your development system adds a Dynamic System Settings rule named Pega-RULES.ProjectManagementFW. This rule specifies the Agile Studio SOAP Servlet URL.

Enabling the communication link in your development system

1. Log in to the development system as a user with system administrator security.

2. From the Class Explorer, select Data > Admin >System > Settings.

3. Select the Pega-RULES.ProjectManagementFW instance.

4. On the Settings tab, enter the URL of your Agile Studio SOAP Servlet in the Value field.





Task 2: Creating a ruleset and application layer

For development systems installed on PRPC versions 6.1 SP1 to 6.1 SP2, for every application on your development server where project resources perform project tasks and bug fixes or you want to enable Direct Feedback, create:

• An additional ruleset for storing new and modified rules in that application

• An application rule built on the primary application rule

Creating a separate ruleset and application rule gives you the flexibility to export rules without moving your Agile Studio and Direct Feedback configuration.

In the following configuration steps, the term primary application refers to the existing application, while development application refers to the application in which you are implementing the project changes.

Creating the ruleset

1. From the Rules Explorer, expand the Sysadmin category. Right-click RuleSet and select New.

2. In the Name field, enter a name for the ruleset and tab to the next field.

The system defaults values in the Version and Description fields.

3. In the Requires RuleSet and Versions section, replace the default value with the primary application's ruleset and version.

4. Leave the “Update your current application to include this new version” checkbox blank.

5. Click Create.


Creating the application rule

1. From the Rules Explorer, expand the Application Definition category. Right-click Application and select New.



2. Enter a name and version. Select the name of the ruleset you created and click Create.

3. On the General tab:

In the Built on Application field, select the primary application and version. Select the Include Parent box. Add the ruleset you created to the Application RuleSets list.

4. To establish connectivity between Agile Studio and a development system installed on Pega versions from 6.1 SP1 to 6.1 SP2, add the PegaCESvcs ruleset to the Component and Shared Rulesets list.

5. See the Installation and Upgrade guide on your distribution media for information about loading the PegaCESvcs ruleset.


Click the Help icon on the rule form for more information about configuring application rules.

Enabling the link

Project management functionality is enabled when you indicate that you want to enable the communication link between Agile Studio and your development system. This is done by checking a box in a topmost application rule of your development system. Agile Studio tracking can be enabled on one or more applications on your development environment.

1. Open the Application rule.

2. On the Advanced tab, check the Enable Project Management box.


Task 3: Creating an access group and enabling feedback For development systems installed on Pega versions 6.1 SP1 to 6.1 SP2, after you create the new application layer, the project resources who perform the development work on project tasks and bug fixes in the application must be given access to that system.

This is done by creating an access group that references the application and version where the work is taking place and then updating the operator record with that access group.

At the same time, you can enable the Direct Feedback function for operators if you want users of the development system to enter and submit feedback about bugs, issues, or configuration and enhancement ideas directly using the pushpin icon. This is an optional set up step for systems built on Pega Version 6.1 SP1 and higher.






2. Select an existing instance or click the New icon to create a new instance.

3. Enter an access group name that represents the development application you previously created.


Enabling the operator to use Direct Feedback (optional) 1. On the Layout tab, add PegaRULES:Feedback as a Role.

This access role activates the feedback feature. When users have this role in their access group, it adds the pushpin icon to their portal.



Repeat this process if you want to create additional access groups to provide access to other applications in the development system.


System administrators: Customizing Direct Feedback settings (optional)

Customizing Direct Feedback settings for PRPC 6.2 development systems is done in the same way as for PRPC 6.3 systems. For more information, see System administrators: Customizing Direct Feedback settings in all Pega versions (optional).

All users: Viewing your work If your current development application is enabled to communicate with Agile Studio, when you sign on to that system, the following changes appear in the Designer Studio.

• A Project Explorer is added to the explorer list.



− When the explorer is in focus, the navigation panel lists the projects and user stories containing the tasks or bugs assigned to you. You can toggle between them as you work on different assignments.

− When you perform work on a task or bug and update the Project Management section of a New, Save As, and Check-In rule form, the navigation panel for the project or user story is populated with those rules. A tree display is visible where you can view and access the rules that have been added or modified as part of the development work.

• The Application menu on your portal header is populated with three project options. These options can appear grayed out and unavailable to you. Typically, this happens when there are no tasks or bugs directly assigned to you for any project. It also happens when your operator ID does not match your operator ID in Agile Studio.

Project options

• Select Switch Project to toggle between projects and backlogs when there is more than one project or backlog with tasks and bugs assigned to you. The item you select becomes your default parent in the Project Management section of the rules you add or update.

• Select View Worklist to display the list of tasks and bug items currently assigned to you.

• In PRPC 6.2, this option replaces Project Tasks that displays in systems built on 6.1 and earlier.

• You can expand a row to display descriptive detail of the assigned work.



• Click Export to Excel to export the list to an Excel spreadsheet.

• Click the Rule Changes tab to display a list of your rule changes that have been associated with your assigned tasks and bugs. You can also view a list of all rule changes in your application that are associated with bug and task IDs.

• This tab is only available in PRPC 6.2 and higher.

• Select Refresh Tasks to refresh your worklist with new assignments from Agile Studio and delete work that has been completed since the last time you signed on to the development system.

All users: Recording your development effort Your current project, backlog, sprint, or user story defaults in the Project ID field.

Note: If you want to record work against a different parent, use the Switch Project option from the application menu.

1. Select the Task Group and the Task you are working on from the drop-down list.

2. In the Additional Worked field, enter the amount of time you have spent in hours since your last update.

When this information is submitted, this value is added to the Actual Hours field on the task or bug.

3. Update the Hours Remaining field to reflect the balance of the effort that is needed to complete the task or bug.

When this information is submitted, this value replaces the Remaining Hours on the task or bug.


When you check in a rule, you can record the Additional Worked and update the Hours Remaining. You also can flag the task or bug as complete by checking the Task Complete box. In this case, you enter only your Additional Worked time. Checking the box resolves the item in Agile Studio and removes the task from your Project Explorer list.



Check-In examples

All users: Using the pushpin to send feedback Customizing Direct Feedback settings for PRPC 6.2 development systems is done in the same way as for Pega 7 systems. For more information, see All users: Using the pushpin to send feedback (Pega versions 7.2 and lower).

pega community | training & resources for pega developers ......such examples are fictitious and...

Documents