Project Management Framework User Guide - Pega · ©2018 PegasystemsInc.,Cambridge,MA...

Pega Agile Studio

IMPLEMENTATION GUIDE7.4

© 2018Pegasystems 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 oftheir respective holders.

For information about the third-party software that is delivered with the product, refer to the third-party license file on yourinstallation 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 proprietaryinformation 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 thediscretion of Pegasystems Inc. This publication remains the property of Pegasystems Inc. and must be returned to it upon request. Thispublication 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. Ifyou have questions about whether a particular capability is included in your installation, please consult your Pegasystems Inc. servicesconsultant.

Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors, aswell 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 anendorsement of these websites. The materials at these websites are not part of the material for Pegasystems products, and use ofthose websites is at your own risk.

Information concerning non-Pegasystems products was obtained from the suppliers of those products, their publications, or otherpublicly 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, andother third-party publications. Such examples are fictitious and any similarity to the names or other data used by an actual businessenterprise or individual is coincidental.

This document is the property of:

Pegasystems Inc.One Rogers StreetCambridge, MA 02142-1209USAPhone: 617-374-9600Fax: (617) 374-9620www.pega.com

DOCUMENT: Pega Agile Studio Implementation GuideSOFTWARE VERSION: 7.4PUBLISHED: Monday, May 14, 2018

Feedback

If you have suggestions or comments for how we can improve our materials, send an email to [email protected].

http://www.pega.com/

mailto:[email protected]?subject=Documentation feedback

CONTENTS

Introduction 5

Post-install setup tasks 6Update the email account 6

Updating the email account 6Enable the work object search index 7Set up a connection to a development system 7

Configuring settings 9Build your organization structure 9Creating the structure 9Option 1 10Option 2 10

Add rulesets and an application rule 10Adding a customization ruleset 10Adding a reporting ruleset 11Temporarily add the customization ruleset to your access group 11Adding the application rule 12Remove the customization ruleset from the access group 13Creating the access groups 14Updating operators 15

Add project resources 15Removing operator access to Pega Agile Studio 16

Operator privileges 17Operator privileges by user 17Create menu 17Agile Studio menu 18Actions and privileges by work type 18Products (PRD) 18Releases (RLS) 19Goals (GOAL) 19Epics (EPIC) 20

Pega Agile Studio Implementation Guide 3

Project Teams (PROJ) 20Sprints (SPR) 21User Stories (US) 22Backlogs (BL) 22Tasks (TASK) 23Bugs (BUG) 23Issues (ISSUE) 24Feedback (FDBK) 25

Integration 26Integrating with external systems 26


IntroductionThis guide provides system administrators with detailed instructions about how to perform post-installation setup and configuration tasks that should be completed before users begin working in thePega Agile Studio application. It is not intended to describe all Pega Agile Studio capabilities.


Introduction

Post-install setup tasksUser: System Administrator

After installation, the following setup tasks are required to prepare Pega Agile Studio for acceptancetesting and general use. These tasks allow you to fully demonstrate and run through the variousfeatures, functions, and processes supported in the application.

n Update the email account

n Enable the work object search index

n Set up a connection to a development system

When you have completed these setup tasks, perform the configuration tasks outlined in Configuringsettings on page 9.

Update the email accountUser: System Administrator

Agile Studio uses an Email Account instance named PegaProjMgmt-Work to define the emailserver and account it uses to send email notifications to resources when new work is assigned tothem and when work for their project team is updated.

To enable this function, update the instance with your organization's outgoing email account host,email address, and sender information.

Updating the email account1. Log in to Agile Studio as the AgileStudioSysAdmin operator using the password install.

2. Select the Designer Studio > Integration> Email > Outbound Email landing page option.

3. In the PegaProjMgmt-Work Work Pool row, click the gear icon to edit the account details.

4. Update the following fields:

Full Name - enter text that you want to appear as the full name of the sender.


Post-install setup tasks

From - enter the email address associated with this email account using the format recognized byyour (SMTP) host. Typically, the format is [email protected]. If your SMTP host requiresauthentication, include one @ character.

Host (SMTP) - enter the Internet IP address or the domain name of your SMTP host. For example:youremailserver.mydomain.com

5. Click Submit.

Agile Studio also supports Pulse notifications. For more information, see Configuring Pulse emailnotifications.

Enable the work object search indexUser: System Administrator

The Agile Studio Search Tool, located on the header of the user portal, provides full text searchcapability. Users can enter text strings to search for, locate, and display project work objects such asprojects, sprints, user stories, tasks, and more. We recommend that you enable search indexing forwork, data, and rules. For information on enabling search indexing, see Enabling and disablingclasses for search indexing.

Set up a connection to a developmentsystem

User: System Administrator

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

You can establish a connection between Pega Agile Studio and one or more Pega Platformdevelopment systems built on Pega Platform.

This connection allows users to create, view, and update user stories and bugs within the AgileWorkbench feature of their Pega Platform development system and allows developers to associaterule changes with their Agile Studio user stories and bugs.



https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#pulse/pulse-configuring-email-notifications-tsk.htm

https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#pulse/pulse-configuring-email-notifications-tsk.htm

https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#engine/search/eng-enabling-indexing-tsk.htm

https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#engine/search/eng-enabling-indexing-tsk.htm

All connection setup tasks are performed in your development system. Repeat the setup processin each development system where you are planning to track and monitor project work. Forinformation on connecting a Pega Platform development system to Agile Studio from the Integration& security tab of your application, see Integrating Agile Workbench with Pega Agile Studio.

For information on connecting development systems on earlier versions of Pega Platform to AgileStudio, seeWorking with Development Systems on Previous Pega Platform Releases on the AgileStudio product page.

Pega Agile Studio to Pega Platform integration provides an operator for authentication. For the SOAPServices, this operator ID is PM_ SOAPOper and for REST it is AS_RESTOper. For added security,before you put Pega Agile Studio into production, you may want to change the password on thisoperator ID in Pega Agile Studio and in the authentication profiles in the development environment.The authentication profile used by SOAP is PM_Integration_AuthProfile and REST uses PM_AgileStudio_AuthProfile. To enable an OAuth 2.0 connection for the REST connections, add a clientregistration data instance and update the service package as specified in Accessing the Pega API byusing OAuth 2.0.

On the Pega development side, create an OAuth provider and delete and recreate the PM_AgileStudio_AuthProfile Authentication Profile as specified in Accessing protected API resourcesby using OAuth 2.0.



https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#project delivery/agile-workbench/proj-integrating-proj-mgmt-app-tsk.htm

https://pdn.pega.com/pega-agile-studio

https://pdn.pega.com/accessing-pega-api-using-oauth-20/accessing-pega-api-using-oauth-20

https://pdn.pega.com/accessing-pega-api-using-oauth-20/accessing-pega-api-using-oauth-20

https://pdn.pega.com/accessing-protected-api-resources-using-oauth-20/accessing-protected-api-resources-using-oauth-20

https://pdn.pega.com/accessing-protected-api-resources-using-oauth-20/accessing-protected-api-resources-using-oauth-20

Configuring settingsUsers: System Administrator, Senior Project Manager, Project Manager

After you complete the post-install setup, there are several configuration tasks that you perform tocomplete the typical configuration setup before users begin to access the system for testing and startto customize it as a production environment.

Although these tasks can be performed at a later time, it is a recommended practice to perform themafter you have completed the post install setup tasks.

l Build your organization structure

l Add rulesets and an application rule

l Add project resources

l Operator privileges

Build your organization structureUser: System Administrator

Pega Agile Studio includes a basic organizational structure that provides a working sample fordemonstration and learning purposes. To configure and prepare for production use, you can build astructure that emulates your corporation and its divisions and departments. When pulled intoreports, this structure enables you to view work that is complete or in-process by the units in yourorganization.

As an administrator, you can view a tree of the installed organization and its branches by selectingthe Designer Studio > Org & Security > Organization> Organizational Chart landing pageoption.

Creating the structureYou can create your structure using one of two options.


Configuring settings

Option 1

Update the Organization tree directly in Designer Studio. For more information, seeOrganizationlanding page.

Option 2

Integrate Pega Agile Studio with the Pega Platform Single Sign-on features that synchronize theorganization chart with your LDAP directory. For more information about this option, seeAuthentication Services or talk to your Pega Platform implementation team.

Add rulesets and an application ruleUser: System Administrator

Adding new rulesets and an Application rule enables you to store and package the configuration andrules you create when you customize Pega Agile Studio without impacting your installed rule base. Italso allows users to create and save custom reports using the Report Wizard and Report Browsertools.

This process entails:

n Adding two rulesets - one for configuration customization and one for reporting

n Adding an Application Rule that references the rulesets

n Creating Access Groups

n Updating operators

Adding a customization ruleset

This ruleset is intended to hold your Pega Agile Studio configuration customizations and its extensionpoints separating them from the installed PegaRULES database.

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

Do not create the ruleset using a Save As option on an existing ruleset such as PegaProjectMgmt.These are password protected. The Save As function carries over the protection into the newruleset. Before you use this ruleset in a production environment, you should lock it. You can thenincrement the version and create new unlocked versions for additional customization.



https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#basics/v6portal/landingpages/orgsecurity/organization.htm

https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#basics/v6portal/landingpages/orgsecurity/organization.htm

https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#data-/data-admin-/data-admin-authservice/main.htm

2. Enter a RuleSet Name for the ruleset and move to the next field.

The system provides default values in the Version and Description fields.

3. Click Create and open. Then click Save.

Adding a reporting ruleset

This ruleset is intended to hold the custom categories and reports created by users using the ReportBrowser. If you choose not to add this ruleset and reference it in the access group of users who canaccess the Report Browser tab, those users will be unable to add a new report or report category. Anerror message displays, preventing them from completing the action.

To add the reporting ruleset, complete the following steps:

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

Do not create the ruleset using a Save As option on an existing ruleset such asPegaCustFoundation or PegaProjectMgmt. These are password-protected rulesets. TheSave As function carries over the protection into the new ruleset. This ruleset shouldremain unlocked with Check-Out disabled in your production environment to allow usersto customize reports.

2. Enter a RuleSet Name for the ruleset and tab to the next field.

The system provides default values in the Version and Description fields.

3. Click Create and open.

4. On the Security tab, clear the Use Check-out? check box.

5. Click Save.

Temporarily add the customization ruleset to your access group

In order to add a custom application to Pega Agile Studio, you must add the ruleset to your currentAccess Group, which is the Pega Agile Studio system administration access group installed with theproduct.

1. From your name in the header of the portal, select the Access Group menu option to open theaccess group you are currently using.

2. On the Advanced tab of the Access Group, add your customization ruleset to the PRODUCTION



RULESETS list.

3. Click Save. The rule form will display a warning due to the production ruleset.

Adding the application rule

1. From the Records Explorer, expand the Application Definition category. Right-click Application andselect Create.

2. Enter a Label and Version. In the Context section, select the customization ruleset you created.

3. Click Create and open.

4. Enter the following information on the Definition tab:

a. In the Built on Application field, select AgileStudio and its highest version.

b. Add the customization and reporting rulesets you created to the APPLICATION RULESETSlist.

c. Set the skin to AgileStudio.

5. Click Save.

6. Set up the Cases & data tab as shown below:



7. Click Save.

Remove the customization ruleset from the access group

1. From your name in the header of the portal, select the Access Group menu option to open theaccess group you are currently using.

2. On the Advanced tab of the Access Group, click the trash icon to delete the customization rulesetfrom the PRODUCTION RULESETS list.

3. Click Save.



Creating the access groups

Pega Agile Studio is installed with five preconfigured access groups that you can copy, rename ,andset up to reference the custom application you created while maintaining the access and privilegesthat have already been associated with the groups.

1. Select the Designer Studio > Org & Security > Security > Access Groups landing pageoption.

2. Select one of the AgileStudio access groups and click Save as.

3. Give it an Access Group Name that represents access to your custom development application andthe user's role.

The following screenshot provides a best practice example of naming an access group using thesample Agile Studio:SrProjManager access group where the application name is followed by theuser role separated by a colon (:).

4. On the Definition tab, select the custom Application Name and Version you created.

5. On the Advanced tab, add your reporting ruleset and Version to the PRODUCTION RULESETSand DESIGN TIME CONFIGURATION lists. This allows users to create custom reports.

6. Click Save.

7. Repeat these steps for each access group.



Updating operators

Pega Agile Studio is also installed with sample operators that you can use to create your ownoperators. You can update them to reference the access groups you created in the previous step andthen use these operators to create your project resources.

1. Select the Designer Studio > Org & Security > Organization > Operators landing pageoption.

2. Select an operator.

3. In the APPLICATION ACCESS section of the Profile tab, click the plus icon to add a row to theACCESS GROUP list.

Select the radio button next to the custom access group you created to make the application thedefault application.

4. Click Save.

5. Repeat these steps for each operator you want to update.

Add project resourcesUsers: System Administrator, Senior Project Manager, Project Manager

Project resources are operators that are assigned to create, manage, and complete project work. PegaAgile Studio is installed with five sample operators that represent the typical project administrativeand team roles with different levels of security and privilege associated with their project role andfunction.



l System Administrator - performs technical and operational tasks; has access to the Pega AgileStudio developer portal

l Senior Project Manager - performs a combination of administrative, product management andproject management functions

l Project Manager - performs day-to-day project management functions to create, oversee, track,and manage projects

l Lead Architect - oversees and leads the application development effort; performs developmenttasks and bug fixes

l System Architect - performs development tasks and bug fixes

This table lists the operators configured in Pega Agile Studio and their associated access groups,access roles, and portal. Passwords are set to install. You can use them as models and starting pointsto assess your resource needs and add your own project resources.

If you are connecting Pega Agile Studio to a 5.5, 6.1, or 6.2 development environment, the operatorIDs must be identical in Pega Agile Studio and the development system in order to correctly pull theuser’s Pega Agile Studio worklist into Designer Studio.

Operator ID Access Group Access Role PortalAgileStudioSysAdmin AgileStudio:SysAdmin PegaProjectMgmt:SrProjectManager Developer

SrProjectManager AgileStudio:SrProjManager PegaProjectMgmt:SrProjectManager WorkManager

ProjectManager AgileStudio:ProjManager PegaProjectMgmt:ProjectManager WorkManager

AgileStudioLeadArchitect AgileStudio:LeadArchitect PegaProjectMgmt:TechMgr WorkUser

AgileStudioSysArchitect AgileStudio:SysArchitect PegaProjectMgmt:User1 Work User

Removing operator access to Pega Agile Studio

If a user leaves your organization and you no longer want them to access Pega Agile Studio or appearin the list of resources, the best practice is to not delete their operator ID from Pega Agile Studio butto instead create and associate the ID with an access group with a name that includes the wordterminated. Pega Agile Studio automatically filters operators with an access group containing thisword from the various resource selection lists.

Example: Change the operator access group from CustomApplication:ProjManager toCustomApplication:Terminated.



Operator privilegesSample operators are configured with a set of privileges that are associated with their access role.The privileges define the processing actions that type of operator has security to perform andcorrespond to actions that display in the Agile Studiomenu on the operator's portal and the Actionsmenu associated with the processing of project work.

Example: All project resources can view a project and add tasks, but only a Project Manager cancreate a project.

To see a list of the actions and privileges for processing functions by operator role, seeOperatorprivileges by user.

Operator privileges by user

Users: System Administrator, Senior Project Manager, Project Manager

The following tables list the menu actions and privileges that are configured for the sample Pega AgileStudio users: Senior Project Manager (SPM), Project Manager (PM), Lead Architect (LA), and SystemArchitect (SA). There is also a separate Access Group and Access Role configured for each user.

Use the tables in this topic to help determine the access group and roles you want to assign yourresources based upon the functionality you want them to have the security to perform.

Operator privileges are associated with the actions that display on the menus accessed by the user.

CreatemenuWhen a privilege or action is available, the option displays on the Createmenu of the user portal.

Action Category Action Privilege Name SPM PM LA SACreate

Product AddProduct x

Project CreateProject x x

Epic AddEpic x x x x

Bug Item AddBug x x x x

Issue AddIssue x x x x

Feedback AddFeedback x x x x

Backlog CreateBacklog x x

User story AddUserStory x x x x



Agile Studio menuWhen a privilege or action is available, the option displays on the Agile Studiomenu of the userportal.

Action Category Action Privilege Name SPM PM LA SATools

MaintainResources

MaintainResources x x

MaintainEnvironmentData

MaintainEnvironmentData x x

BulkProcessing tabon Resources &Workbasketsoption

BulkProcessAssignments x x

View

Products x x x x

Releases x x x x

Goals x x x x

Epics x x x x

Projects x x x x

Backlogs x x x x

Feedback x x x x

Resources &Workbaskets

x x x x

Actions and privileges by work typeWhen a privilege or action is available for a work type, the option displays in the Create andAgileStudiomenus and in the list on the Actions tab of the work item.

The following tables lists the flow and local action privileges assigned to the Pega Agile Studio worktypes, as well as the sample operators who have been given the security to perform those actions.

Products (PRD)Action Privilege Name SPM PM LA SAAdd product AddProduct x



Action Privilege Name SPM PM LA SAUpdate product UpdateProduct x

Withdraw product Withdraw Product x

Retire product RetireProduct x

Add backlog for product Add Backlog x

Add release for product AddRelease x

Add product goal AddGoal x

Add note AddNote x x x x

Update team UpdateTeam x x

Add epic AddEpic x x

Associate tags AssociateTags x x x x

Reopen resolved product WorkReopen x

Add an attachment AddAttachment x x x x

Bulk process feedback items FeedbackBulkProcess x x x x

Releases (RLS)Action Privilege Name SPM PM LA SAAdd release AddProductVersion x

Update release UpdateProductVersion x

Withdraw release WithdrawProductVersion x

Retire release RetireProductVersion x

Manage setting ManageSettings x


Update trendline Rebaseline x

Update team UpdateTeam x


Reopen resolved release WorkReopen x


Add release goal AddGoal x

Add an epic AddEpic x x

Goals (GOAL)Action Privilege Name SPM PM LA SAAdd goal AddGoal x

Resolve goal Resolve x

Edit goal Edit x




Action Privilege Name SPM PM LA SAEnter status update TrackStatus x

Reopen a resolved goal WorkReopen x

Add epic AddEpic x x

Update team UpdateTeam x x



Epics (EPIC)Action Privilege Name SPM PM LA SAAdd epic AddEpic x x x x

Resolve epic Resolve x x x x

Edit epic Edit x x x x


Add/import user stories ImportStoriesFromExcel x x x x

Enter status update TrackStatus x x x x

Add user story AddUserStory x x x x

Update priority UpdatePriority x x x x


Reassign ReAssign x x x x

Reopen a resolved epic WorkReopen x x x x

Add a dependency AddDependency x x x x

Remove a dependency RemoveDependency x x x x


Update team UpdateTeam x x x x

Quick edit QuickEdit x x x x

Project Teams (PROJ)Action Privilege Name SPM PM LA SAApprove project ApproveProjects x x

Add/import task groups AddTaskGroups x x

Complete project CompleteProject x x

Manage resources ManageResources x x

Withdraw project ResolveProject x x

Update project UpdateProject x x

Create project CreateProject x x

Copy project CopyProject x x



Action Privilege Name SPM PM LA SAAdd/import bugs ImportBugsFromExcel x x x x


Update trendline Rebaseline x x

Add issue AddIssue x x x x

Add bug AddBug x x x x

Enter a status update TrackStatus x x x x

Add a sprint AddSprint x x x


Update team UpdateTeam x x x

Bulk process bugs BulkProcessBugs x x x x

Bulk process issues BulkProcesIssues x x x x

View definition of done ViewDefinitionOfDone x x x x

Update definition of done UpdateDefinitionOfDone x x

Sprints (SPR)Action Privilege Name SPM PM LA SAEdit Edit x x x x

Add/import bugs ImportBugsFromExcel x x x x


Update trendline Rebaseline x x x

Get additional stories from backlog MoveAdditionalChildItems x x x x

Bulk process user stories BuilProcessUserStories x x x x

Plan sprint PlanSprint x x x

Start sprint StartSprint x x x


Resolve sprint ResolveSprint x x x


Document sprint stories DocumentSprintStories x x x x

Document sprint status DocumentSprintStatus x x x x

Add a bug item AddBug x x x x

Withdraw sprint Withdraw x x x x


Update sprint team UpdateTeam x x x x

Bulk process issues BulkProcessIssues x x x x



Reopen a resolved sprint WorkReopen x x x x



User Stories (US)Action Privilege Name SPM PM LA SAEdit Edit x x x x

Resolve Resolve x x x x

Manage resources ManageResources x x x x

Add/import bugs ImportBugsFromExcel x x x x


Add issue to user story AddIssue x x x x


Copy user story CopyUserStory x x x x

Spin off related work SpinOffRelatedWork x x x x

Add bug to user story AddBug x x x x

Move to different parents Move x x x x




Withdraw Withdraw x x x x

Add task to user story AddTask x x x x

Reopen a resolved story WorkReopen x x x x


Add a dependency AddDependency x x x x

Remove a dependency RemoveDependency x x x x

Bulk process a story's bugs BulkProcessBugs x x x x

Bulk process a story's issues BulkProcesIssues x x x x

Quick edit story from list QuickEdit x x x x

Backlogs (BL)Action Privilege Name SPM PM LA SAEdit Edit x x x x

Resolve Resolve x x x x

Add/import bugs ImportBugsFromExcel x x x

Add/import user stories ImportStoriesFromExcel x x x x


Add issue to backlog AddIssues x x x x

Import stories from application profile ImportFromAP x x x x



Action Privilege Name SPM PM LA SADocument backlog stories DocumentBacklogStories x x x x

Add user story to backlog AddUserStory x x x x

Copy bug CopyBug x x x x

Add bug to backlog AddBug x x x x


Bulk process issues BulkProcessIssues x x x x

Reopen a resolved backlog WorkReopen x x x x




Bulk process stories BulkProcessStories x x x x

Export bugs to excel ExportBugsToExcel x x x x

Tasks (TASK)Action Privilege Name SPM PM LA SACreate/add task CreateNewTask x x x x

Approve task ApproveTask x x x

Complete task CompleteTask x x x x

Reject task RejectTask x x x x

Resolve task ResolveTask x x x

Update task UpdateTask x x x x

Verify task VerifyTask x x x x

Withdraw task WithdrawTask x x x x



Reopen resolved task WorkReopen x x x x




Bugs (BUG)Action Privilege Name SPM PM LA SAEnter/add bug EnterBug x x x x

Approve bug ApproveBug x x x x

Resolve bug ResolveBug x x x x



Action Privilege Name SPM PM LA SAVerify bug VerifyBug x x x



Spin off related work ActionSpinOffWorkItem x x x x

Update parent user story UpdateUserStory x x x x


Update parent release UpdateRelease x x x x

Request more information RequestMoreInfo x x x x

Edit bug Edit x x x x

Copy bug CopyBug x x x x


Reopen a resolved bug WorkReopen x x x x


Add dependency AddDependency x x x x

Remove dependency RemoveDependency x x x x


Quick edit bug from list QuickEdit x x x x

Issues (ISSUE)Action Privilege Name SPM PM LA SAEnter/add issue EnterIssue x x x x

Resolve issue ResolveIssue x x x x


Update issue UpdateIssue x x x x





Reopen a resolved issues WorkReopen x x x x


Quick edit an issue from list QuickEdit x x x x

Spin off related work ActionSpinOffWorkItem x x x x



Feedback (FDBK)

Action Privilege Name SPM PM LA SAEnter/add feedback AddFeedback x x x x

Update product association UpdateProductID x x x x

Triage Triage x x

Reject Reject x x


Edit Edit x


Reopen a resolved feedback WorkReopen x x x x






Integration

Integrating with external systemsUser: System Administrator

Pega Agile Studio contains a collection of SOAP and REST services that you can use to build andsupport integration with an external application to push and pull information to and from theapplication. For technical details on available Agile Studio services, see Integrating Agile Studio withOther Applications.


Integration



Date post:	07-Feb-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

Project Management Framework User Guide - Pega · ©2018 PegasystemsInc.,Cambridge,MA...

Documents