Agile Studio WORKING WITH DEVELOPMENT SYSTEMS ON PREVIOUS PEGA PLATFORM RELEASES 7.3
|
|
- April Dawson
- 5 years ago
- Views:
Transcription
1 Agile Studio WORKING WITH DEVELOPMENT SYSTEMS ON PREVIOUS PEGA PLATFORM RELEASES 7.3
2 2017 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 USA Phone: (617) Fax: (617) Agile Studio Document: Working with Development Systems on Previous Pega Platform Releases Software Version: 7.3 Updated: July 2017
3 CONTENTS Introduction... i Working with Agile Studio from Pega 7, 7.1, and 7.2 development environments... 1 System administrators: Setting up a connection to a Pega 7, 7.1, 7.2 development system... 1 Connecting to a Pega 7, 7.1, 7.2 development system... 1 All users: Viewing your work... 2 All users: Recording your effort... 3 Working with Agile Studio from PRPC 6.3 development environments... 4 System administrators: Setting up a connection to 6.3 development systems 4 Task 1: Setting up the connection and enabling project tracking... 4 Task 2: Creating an access group and enabling feedback... 5 System administrators: Customizing Direct Feedback settings in all Pega versions (optional)... 5 Option 1: Changing the type of work object the feedback creates... 6 Option 2: Linking the feedback to projects... 6 Option 3: Adding validation... 8 All users: Viewing your work... 9 All users: Recording your effort All users: Using the pushpin to send feedback (Pega versions 7.2 and lower)12 Working with Agile Studio from PRPC 6.2 development environments System Administrators: Setting up a connection in a 6.2 development system14 Task 1: Specifying the Agile Studio URL Task 2: Creating a ruleset and application layer Task 3: Creating an access group and enabling feedback Enabling the operator to use Direct Feedback (optional) System administrators: Customizing Direct Feedback settings (optional) All users: Viewing your work All users: Recording your development effort All users: Using the pushpin to send feedback Working with Agile Studio from PRPC 6.1 development environments System administrators: Setting up a connection in a 6.1 SP1 or 6.1 SP2 development system Task 1: Specifying the Agile Studio URL Task 2: Creating a ruleset and application layer Task 3: Creating an access group and enabling feedback System administrators: Customizing Direct Feedback settings (optional)... 24
4 All users: Viewing your work All users: Recording your development effort All users: Using the pushpin to send feedback... 27
5 Introduction This guide is designed to help users developing on previous versions of the Pega Platform to effectively use Agile Studio 7.3. It assumes that you have installed Agile Studio 7.3 on Pega Platform 7.3. 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.3. 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, and 7.2 development environments Working with Agile Studio from PRPC 6.3 development environments Working with Agile Studio from PRPC 6.2 development environments Working with Agile Studio from PRPC 6.1 development environments Working with Development Systems on Previous Pega Platform Releases i
6 Working with Agile Studio from Pega 7, 7.1, and 7.2 development environments This section describes how to connect your development environment to Agile Studio 7.3, 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 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 development system Select the Designer Studio System > Settings > Project Management landing page option. In the Agile Studio CONNECTION DETAILS section, enter the URLs needed to establish connectivity between the application and Agile Studio. a. In the Agile Studio URL field, enter the URL of your Agile Studio instance. b. In the Agile Studio SOAP URL field, enter the SOAP URL that passes project tracking data to and from an application to your Agile Studio instance. Click Save Connection Details. Click Test Connectivity to test the connection. 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. a. On Pega versions 7.2 and lower, select the check box in the FEEDBACK column to enable feedback. On Pega versions and higher, leave the FEEDBACK check box unchecked and install Working with Development Systems on Previous Pega Platform Releases 1
7 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. b. 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. c. Use the Agile Studio 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 Agile Studio PRODUCT column is blank, the smart feedback will be assigned to PRD-1. 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 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 Agile Studio 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. 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 Agile Studio to launch an Agile Studio session in a new window. Working with Development Systems on Previous Pega Platform Releases 2
8 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: Recording your effort 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 Working with Development Systems on Previous Pega Platform Releases 3
9 Working with Agile Studio from PRPC 6.3 development environments This section describes how to connect your development environment to Agile Studio 7.3, 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 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. 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. 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. Select the Pega icon > System > Settings > Project Management. In the Connection Details section, enter the URLs needed to establish connectivity to Agile Studio. a. In the Agile Studio URL field, enter the URL of your Agile Studio instance. b. In the Agile Studio SOAP URL field, enter the SOAP URL that passes project tracking data to/from an application to your Agile Studio instance. c. Click Save the Connection. 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: a. Select the Project Tracking Enabled check box. b. Click the Save icon. If the application is locked, the Supply Password field appears in a window when you click Save. c. Enter the password and click OK to continue with the save. Repeat these steps for each application. Working with Development Systems on Previous Pega Platform Releases 4
10 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 From the Rules Explorer, select Security > Access Group. Select an existing instance or click New to create a new instance. Enter an Access Group Name that represents the development application you previously created. On the Layout tab, select the development Application Name and Version. Enabling the operator to use Direct Feedback (optional) 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. Click the Save icon. Add the access group to operators who require access to the development application. 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 to the 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. Working with Development Systems on Previous Pega Platform Releases 5
11 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. In the search field, type DetermineTargetClass. Select the PegaProjMgmt-Work class instance. Save it to your Custom Ruleset, but do not change the name of the rule. 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 Save icon. 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. In the search field of the Designer Studio, type DetermineInitialGroup. Select the PegaProjMgmt-Work class instance. Save it to your Custom Ruleset, but do not change the name of the rule. On the Results tab, enter your return values in the Allowed Results list. These will be referenced in the next step. Working with Development Systems on Previous Pega Platform Releases 6
12 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. 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. Working with Development Systems on Previous Pega Platform Releases 7
13 Property name GenericWorkForInt.BuildData.ApplicationName GenericWorkForInt.BuildData.ApplicationVersion GenericWorkForInt.Category GenericWorkForInt.ReportedByDivision GenericWorkForInt.ReportedByOrg GenericWorkForInt.ReportedByWorkgroup Description Name of the application on the sending server Version of the application on the sending server 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 Organization division of the operator who submitted the feedback Organization of the operator who submitted the feedback Work group of the operator who submitted the feedback Click the Save icon. Click the Help icon on the rule form for more information about configuring decision trees. Option 3: Adding validation When Agile Studio receives a feedback message, it sends an to the person who submitted the feedback. A decision tree named Valid AddressesforCorr in the PegaProjectMgmt ruleset specifies the logic that decides whether to send in response to the feedback based on the address of the sending operator. To change this default logic, create a customized version of the decision tree. In the search field, type Valid AddressesforCorr. Select the PegaProjMgmt-Work class instance. Save it to your Custom Ruleset, but do not change the name of the rule. On the Decision tab, update the circumstance logic for sending the feedback based on the address. Working with Development Systems on Previous Pega Platform Releases 8
14 You can enter specific addresses or use a contains evaluator to include or exclude domain names. For example, send an if the contains YourCompany.com; otherwise, do not send an . The Otherwise option is the default for any address that does not meet any of the criteria. Return true for circumstances where you want to send an . Return false for circumstances where you do not want to send an . Click the Save icon. Click the Help icon 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. Working with Development Systems on Previous Pega Platform Releases 9
15 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 Agile Studio 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. Working with Development Systems on Previous Pega Platform Releases 10
16 New and Save As example Check-In examples Working with Development Systems on Previous Pega Platform Releases 11
17 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. 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. Working with Development Systems on Previous Pega Platform Releases 12
18 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. Enter your feedback text describing the scenario or problem in as much detail as possible. 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. The address in your operator profile populates the From field. Click Send. 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 that the FDBK item was created Adds the screenshot to the item and a copy of the acknowledge 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 Working with Development Systems on Previous Pega Platform Releases 13
19 Working with Agile Studio from PRPC 6.2 development environments 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. 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. 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 3: Creating an access group and enabling feedback 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 Log in to the development system as a user with system administrator security. From the Class Explorer, click Data > Admin > System > Settings. Select the Pega-RULES.ProjectManagementFW instance. On the Settings tab, enter the URL of your Agile Studio SOAP Servlet in the Value field. Click the Save icon. 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 Working with Development Systems on Previous Pega Platform Releases 14
20 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 From the Rules Explorer, expand the Sysadmin category. Right-click RuleSet and select New. 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. In the Requires RuleSet and Versions section, replace the default value with the primary application's ruleset and version. Leave the Update your current application to include this new version check box blank. Click Create. Click the Save icon. Creating the application rule From the Rules Explorer, expand the Application Definition category. Right-click Application and select New. Enter a Name and Version. Select the name of the ruleset you created and click Create. On the General tab: a. In the Built on Application field, select the primary application and version. b. Select the Include Parent check box. c. Add the ruleset you created to the Application RuleSets list. Click the Save icon. Click the Help icon on the rule form for more information about configuring application rules. Working with Development Systems on Previous Pega Platform Releases 15
21 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. Open the Application rule. On the Advanced tab, select the Enable Project Management check box. Click the Save icon. 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. 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 From the Rules Explorer, select Security > Access Group. Select an existing instance or click the New icon to create a new instance. Enter an access group name that represents the development application you previously created. On the Layout tab, select the development Application Name and Version. Enabling the operator to use Direct Feedback (optional) 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. Click the Save icon. Add the access group to operators who require access to the development application. 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. Working with Development Systems on Previous Pega Platform Releases 16
22 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. Working with Development Systems on Previous Pega Platform Releases 17
23 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. Select the Task Group and the Task you are working on from the dropdown 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 task or bug. 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. 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 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. Working with Development Systems on Previous Pega Platform Releases 18
24 New and Save As example Check-In examples Working with Development Systems on Previous Pega Platform Releases 19
25 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). Working with Development Systems on Previous Pega Platform Releases 20
26 Working with Agile Studio from PRPC 6.1 development environments This section describes how to connect your development environment to Agile Studio 7.3, 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 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. 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. 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 3: Creating an access group and enabling feedback 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 Log in to the development system as a user with system administrator security. From the Class Explorer, select Data > Admin >System > Settings. Select the Pega-RULES.ProjectManagementFW instance. On the Settings tab, enter the URL of your Agile Studio SOAP Servlet in the Value field. Click the Save icon. 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 Working with Development Systems on Previous Pega Platform Releases 21
27 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 From the Rules Explorer, expand the Sysadmin category. Right-click RuleSet and select New. 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. In the Requires RuleSet and Versions section, replace the default value with the primary application's ruleset and version. Leave the Update your current application to include this new version checkbox blank. Click Create. Click the Save icon. Creating the application rule From the Rules Explorer, expand the Application Definition category. Right-click Application and select New. Enter a name and version. Select the name of the ruleset you created and click Create. On the General tab: a. In the Built on Application field, select the primary application and version. b. Select the Include Parent box. c. Add the ruleset you created to the Application RuleSets list. Working with Development Systems on Previous Pega Platform Releases 22
28 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. See the Installation and Upgrade guide on your distribution media for information about loading the PegaCESvcs ruleset. Click the Save icon. 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. Open the Application rule. On the Advanced tab, check the Enable Project Management box. Click the Save icon. 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. 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 From the Rules Explorer, select Security > Access Group. Select an existing instance or click the New icon to create a new instance. Enter an access group name that represents the development application you previously created. On the Layout tab, select the development Application Name and Version. Enabling the operator to use Direct Feedback (optional) On the Layout tab, add PegaRULES:Feedback as a Role. Working with Development Systems on Previous Pega Platform Releases 23
29 This access role activates the feedback feature. When users have this role in their access group, it adds the pushpin icon to their portal. Click the Save icon. Add the access group to operators who require access to the development application. 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 (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 Working with Development Systems on Previous Pega Platform Releases 24
30 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. Working with Development Systems on Previous Pega Platform Releases 25
31 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. 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 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. New and Save As example Working with Development Systems on Previous Pega Platform Releases 26
32 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). Working with Development Systems on Previous Pega Platform Releases 27
Pega Agile Studio USER GUIDE 7.4
Pega Agile Studio USER GUIDE 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks
More informationAgile Studio USER GUIDE 7.3
Agile Studio USER GUIDE 7.3 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks or
More informationPega Foundation for Healthcare
Pega Foundation for Healthcare COMMON CODES SOLUTION BUSINESS CASE USE CASE GUIDE 7.31 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered
More informationManaging the Burn Down Agent
Managing the Burn Down Agent Agile Studio 7.3.1 December 2017 Introduction Agile Studio 7.3.1 has several burn down charts that teams and managers can use to view the overall progress of a sprint, team,
More informationPega Foundation for Healthcare
Pega Foundation for Healthcare COMMON CODES SOLUTION BUSINESS CASE USE CASE GUIDE 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered
More informationAgile Studio IMPLEMENTATION GUIDE 7.3.1
Agile Studio IMPLEMENTATION GUIDE 7.3.1 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks
More informationPega Underwriting for Insurance
OPERATIONS Pega Underwriting for Insurance Implementation Planning Workbook 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks,
More informationPega Digital Software Delivery
Pega Digital Software Delivery USER GUIDE 1.00 [Type here] 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved.
More informationPega Agile Studio. Upgrade Guide 7.4
Pega Agile Studio Upgrade Guide 7.4 2018 Pegasystems Inc., Cambridge, MA. All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks
More informationProject Management Framework
Project Management Framework Release Notes Version 7.1.1 Framework Overview The Project Management Framework (PMF) is a powerful Project Management application designed for the management of Scrum projects.
More informationPega Field Marketing USER GUIDE 7.4
Pega Field Marketing USER GUIDE 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks
More informationIntegrating Agile Studio with Other Applications
Integrating Agile Studio with Other Applications Agile Studio 7.3.1 December 2017 Introduction Agile Studio is integrated with Pega Platform 7.3.1 to allow teams to change their application s records in
More informationVCR REST Connectivity
VCR REST Connectivity Pega Smart Dispute for Issuers 7.21 December 2017 Introduction This document explains how Pega Smart Dispute for Issuers connects to VCR using REST connectors. VCR supports POST method
More informationUser Guide. PegaSurvey 7.2.1
User Guide PegaSurvey 7.2.1 Copyright Copyright 2016 Pegasystems Inc. All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. Other brand or product
More informationPega Customer Service for Healthcare and Pega Sales Automation for Healthcare
Pega Customer Service for Healthcare and Pega Sales Automation for Healthcare INSTALLATION GUIDE Pega Customer Relationship Management for Healthcare 7.31 2017 Pegasystems Inc., Cambridge, MA All rights
More informationPega Customer Service for Healthcare and Pega Sales Automation for Healthcare
Pega Customer Service for Healthcare and Pega Sales Automation for Healthcare UPGRADE GUIDE Pega Customer Relationship Management for Healthcare 7.31 2017 Pegasystems Inc., Cambridge, MA All rights reserved.
More informationCapturing Interaction History
Capturing Interaction History Pega Marketing for Financial Services 7.31 November 2017 Introduction This document contains information about how Pega Marketing for Financial Services 7.31 captures Interaction
More informationMARKETING. Pega Marketing. Installation Guide 7.4
MARKETING Pega Marketing Installation Guide 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All
More informationPega Co-Browse. Installation Guide 7.4
Pega Co-Browse Installation Guide 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks
More informationTechnical Note. PegaCHAT 6.2 SP3. Installing and Configuring OpenFire
Technical Note PegaCHAT 6.2 SP3 Installing and Configuring OpenFire Copyright 2011 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc.
More informationPega Underwriting for Insurance
PEGA OPERATIONS Pega Underwriting for Insurance IMPLEMENTATION GUIDE 7.31 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks,
More informationHealthcare Common Codes Solution
Healthcare Common Codes Solution Version 3.2 SP1 Business Use Case Guide Copyright 2013 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems
More informationManaging the Burn Down Agent
Managing the Burn Down Agent Project Management Framework 7.1.2 May 2015 Introduction The Project Management Framework has several burn down charts that can be used by teams and managers to view the overall
More informationTechnical Note. Customer Process Manager. 7.1 Release 2. CPM Next Best Action Adapter
Technical Note Customer Process Manager 7.1 Release 2 CPM Next Best Action Adapter Copyright 2014 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems
More informationProject Management Framework
Project Management Framework 7.1.2 UPGRADE GUIDE Copyright 2015 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade
More informationVCR Batch Queue Processing
VCR Batch Queue Processing Smart Dispute for Issuers 7.21 February 2017 Introduction Visa claims resolution (VCR) provides various queues for members to download and process cases or transactions. The
More informationPRPC Personal Edition Installation Guide 6.3 SP1
PRPC Personal Edition Installation Guide 6.3 SP1 Copyright 2012 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade
More informationSystem Architect Essentials I. EXERCISE GUIDE (v. 7.1)
System Architect Essentials I EXERCISE GUIDE (v. 7.1) Copyright 2015 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain
More informationPega Knowledge. User Guide 7.4
Pega Knowledge User Guide 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
More informationDecision Strategy Manager
Decision Strategy Manager DMSample - Retention Predictive Model Version 7.1.8 2015 by Pegasystems Inc. All rights reserved This document describes products and services of Pegasystems Inc. It may contain
More informationX12 Message Processing
X12 Message Processing Pega Foundation for Healthcare 7.31 July 2017 Overview The Accredited Standards Committee (ASC) X12 message is used to transfer data across and between industries. Pega Foundation
More informationTechnical Note. Using the Net Promoter Framework 7.1
Technical Note Using the Net Promoter Framework 7.1 Copyright 2014 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain
More informationPega Chat. Installation Guide 7.4
Pega Chat Installation Guide 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks
More informationBusiness Intelligence Exchange (BIX)
Business Intelligence Exchange (BIX) Release Notes Version 2.3 And Version 2.3 SP1 February, 2012 Framework Overview The Business Intelligence Exchange (BIX) extracts information from a PRPC database into
More informationPegaCALL. Overview. About this Release. Release Notes for Version 6.3 August 2012
PegaCALL Release Notes for Version 6.3 August 2012 Overview PegaCALL provides computer-telephony integration (CTI) capabilities for applications built on PRPC, including Pega Customer Process Manager (CPM).
More information7.21 IMPLEMENTATION GUIDE
Pega Customer Service 7.21 IMPLEMENTATION GUIDE Copyright 2016 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved.
More informationEXAM BLUEPRINT PRPC Certified System Architect
EXAM BLUEPRINT PRPC Certified System Architect White Paper Copyright 2011 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain
More informationPega Foundation for Financial Services
Pega Foundation for Financial Services ACCOUNTING GUIDE 7.32 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved.
More informationProduct Designer for Financial Services
Product Designer for Financial Services IMPLEMENTATION GUIDE 7.22 Copyright 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks,
More informationPega Product Composer for Healthcare
Pega Product Composer for Healthcare IMPLEMENTATION GUIDE 7.31 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights
More informationManaging the Burn Down Agent
Managing the Burn Down Agent Agile Studio 7.4 May 2018 Introduction Agile Studio 7.4 has several burn down charts that teams and managers can use to view the overall progress of a sprint, team, or release.
More informationHealthcare FHIR API TECHNICAL SPECIFICATION 7.4
Healthcare FHIR API TECHNICAL SPECIFICATION 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All
More informationPega Call CONFIGURATION AND OPERATIONS GUIDE. CTI Link Server with Genesys CTI 7.31
Pega Call CONFIGURATION AND OPERATIONS GUIDE CTI Link Server with Genesys CTI 7.31 Copyright 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered
More informationEXAM BLUEPRINT PRPC Certified Reporting Specialist v6.2
White Paper EXAM BLUEPRINT PRPC Certified Reporting Specialist v6.2 Copyright 2011 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc.
More informationEXAM BLUEPRINT Certified CPM Architect
EXAM BLUEPRINT Certified CPM Architect White Paper Copyright 2011 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade
More informationMARKETING. Pega Marketing. Upgrade Guide 7.4
MARKETING Pega Marketing Upgrade Guide 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other
More informationDecision Manager Help. Version 7.1.7
Version 7.1.7 This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary information. The document and product are protected by copyright and distributed
More informationCertified Senior System Architect
White Paper Certified Senior System Architect EXAM BLUEPRINT Copyright 2017 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may
More informationFinancial Accounting for Financial Services Framework. Version 2.3. Installation Guide
Financial Accounting for Financial Services Framework Version 2.3 Installation Guide Copyright 2009 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of
More informationPEGA MARKETING. Pega Marketing IMPLEMENTATION GUIDE 7.31
PEGA MARKETING Pega Marketing IMPLEMENTATION GUIDE 7.31 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved.
More informationEXAM BLUEPRINT PRPC Certified Pega Business Architect
EXAM BLUEPRINT PRPC Certified Pega Business Architect White Paper Copyright 2014 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It
More informationEXERCISE SYSTEM GUIDE (v. 7.13)
EXERCISE SYSTEM GUIDE (v. 7.13) Copyright 2016 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary
More informationPega Knowledge Management
Pega Knowledge Management 7.1 USER GUIDE Copyright 2014 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade secrets
More informationPegaCALL CONFIGURATION AND OPERATIONS GUIDE FOR CTI LINK WITH AVAYA AURA CONTACT CENTER (AACC) VERSION
PegaCALL CONFIGURATION AND OPERATIONS GUIDE FOR CTI LINK WITH AVAYA AURA CONTACT CENTER (AACC) VERSION 7.1.3.3 Copyright 2015 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes
More informationWorking with PDF Forms and Documents. PegaRULES Process Commander 5.1
Working with PDF Forms and Documents PegaRULES Process Commander 5.1 Copyright 2006 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc.
More informationEXAM BLUEPRINT PRPC Certified Senior System Architect v 6.2
White Paper EXAM BLUEPRINT PRPC Certified Senior System Architect v 6.2 Copyright 2011 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems
More informationPegaRULES Process Commander. Certified Senior System Architect. Exam Blueprint
PegaRULES Process Commander Certified Senior System Architect Exam Blueprint Copyright 2009 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems
More informationDistributed Transactions and PegaRULES Process Commander. PegaRULES Process Commander Versions 5.1 and 5.2
Distributed Transactions and PegaRULES Process Commander PegaRULES Process Commander Versions 5.1 and 5.2 Copyright 2007 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products
More informationEXAM BLUEPRINT PRPC Certified Methodology Black Belt
EXAM BLUEPRINT PRPC Certified Methodology Black Belt White Paper Copyright 2011 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It
More informationPega Knowledge. Implementation Guide
Implementation Guide 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks or service
More informationCertified Pega Customer Service Business Architect
White Paper Certified Pega Customer Service Business Architect EXAM BLUEPRINT Copyright 2015 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems
More informationPTC Windchill Quality Solutions Extension for ThingWorx Guide
PTC Windchill Quality Solutions Extension for ThingWorx Guide Copyright 2016 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved. User and training guides and related documentation from PTC Inc.
More informationSAP BusinessObjects Live Office User Guide SAP BusinessObjects Business Intelligence platform 4.1 Support Package 2
SAP BusinessObjects Live Office User Guide SAP BusinessObjects Business Intelligence platform 4.1 Support Package 2 Copyright 2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this
More informationTHE LOGIN PAGE... 3 THE HOME PAGE... 4 REPORTS... 15
CheckTrack Web Reporting User guide 1 Contents THE LOGIN PAGE... 3 THE HOME PAGE... 4 REPORTS... 5 REPORT SCREEN FUNCTIONALITY... 5 CHECK DETAILS & CHECK IMAGE... 8 NEW CHECKS... 10 ALL ACTIVE CHECKS...
More informationPega Knowledge PRODUCT OVERVIEW 7.31
Pega Knowledge PRODUCT OVERVIEW 7.31 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks
More informationDocument Manager. Balance Point Technologies, Inc. Document Manager. User Guide. Certified MAX Integrator
Balance Point Technologies, Inc. www.maxtoolkit.com Document Manager User Guide 1 P a g e Copyright Manual copyright 2017 Balance Point Technologies, Inc. All Rights reserved. Your right to copy this documentation
More informationGuide to User Interface 4.3
Datatel Colleague Guide to User Interface 4.3 Release 18 June 24, 2011 For corrections and clarifications to this manual, see AnswerNet page 1926.37. Guide to User Interface 4.3 All Rights Reserved The
More informationRational Focal Point Technical Overview 2(15)
Copyright IBM Corporation 1997-2009 U.S. Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Rational Focal Point Technical Overview
More informationProcess Commander Installation Guide
Process Commander Installation Guide Version: 6.3 SP1 Database: Oracle Application Server: WebSphere 6 Copyright 2013 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products
More informationPega Call CONFIGURATION AND OPERATIONS GUIDE FOR CTI LINK WITH AVAYA AURA CONTACT CENTER (AACC) VERSION
Pega Call CONFIGURATION AND OPERATIONS GUIDE FOR CTI LINK WITH AVAYA AURA CONTACT CENTER (AACC) VERSION 7.1.3.4 Copyright 2016 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes
More informationMigration - V6.2 to V6.3
2012 by Pegasystems, Inc. All rights reserved. 2012 by Pegasystems, Inc. All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary
More informationAdministration Guide. Release
Administration Guide Release 13.3.00 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational
More informationIBM i2 Analyst s Notebook Quick Start Guide
IBM i2 Analyst s Notebook Quick Start Guide Provided with IBM i2 Analyst s Notebook 8.9 May 202 - - Copyright 0. This edition applies to version 8, release 9 of IBM i2 Analyst s Notebook (product number
More informationKnow Your Customer. Implementation Guide 7.1.1
Know Your Customer Implementation Guide 7.1.1 Copyright 2014 Pegasystems Inc., Cambridge, MA All rights reserved This document describes products and services of Pegasystems Inc. It may contain trade secrets
More informationBlackbaud Direct Marketing New Features Guide
Blackbaud Direct Marketing New Features Guide 05/09/2018 Blackbaud Direct Marketing 5.0 Blackbaud Direct Marketing New Features US 2018 Blackbaud, Inc. This publication, or any part thereof, may not be
More informationSupplier Instructions for Completing NAFTA Certificate of Origin in Trade Automation (TA)
Supplier Instructions for Completing NAFTA Certificate of Origin in Trade Automation (TA) Supplier Instructions for Completing NAFTA Certificate of Origin in Trade Automation (TA) I. INTRODUCTION When
More informationSpiraTest Quick Start Guide Inflectra Corporation
SpiraTest Quick Start Guide Inflectra Corporation Date: January 28, 2018 Contents Introduction 2 1. Logging In and Selecting a Project 3 2. Define the Requirements 5 3. Create the Release and Iteration
More informationCommPortal Portal Guide
CommPortal Portal Guide The User Portal is available at https://userportal.appiaservices.com. Please contact Appia Support at 877-277-4297, option 3, or support@appiaservices.com if you need login information.
More informationProficy* HMI-SCADA G ETTING S TARTED. ON THE A PPLE ipad OR i P HONE C LIENT
Proficy* HMI-SCADA G ETTING S TARTED ON THE A PPLE ipad OR i P HONE C LIENT July 2014 Disclaimer of Warranties and Liability The information contained in this manual is believed to be accurate and reliable.
More informationReadyTalk for Marketo User Guide
ReadyTalk for Marketo User Guide Revised 11/24/2015 Contents Configuring ReadyTalk & Marketo... 3 Setting Up Your Event in ReadyTalk... 5 Setting Up Your Event in Marketo... 7 Creating a New Program...
More informationPEGA PLATFORM. Business Intelligence Exchange (BIX) 7.4 User Guide
PEGA PLATFORM Business Intelligence Exchange (BIX) 7.4 User Guide 2018 Pegasystems Inc., Cambridge, MA. All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights
More informationFocus University Training Document
Focus University Training Document FOCUS Training: Nurses/Health Training Agenda Basic Navigation of SIS Searching for Students More Search Options Student Record and Sub menus o General Demographics o
More informationSupplier SAP SNC User Guide
Supplier SAP SNC User Guide Version 1.0 July 29, 2014 AGCO Corporation Page 1 1 Introduction AGCO has chosen SAP Supplier Network Collaboration (SNC) to improve visibility and capability in North America
More informationManaging the Directory
Managing the Directory 2016 - Winter Edition User Guide - Table of Contents Overview Use Case(s) Accessing the Tool Directory Tabs for Admins/Editors Club Members Staff Tab My Profile Search Tab Export
More informationGetting Started With the Cisco PAM Desktop Software
CHAPTER 3 Getting Started With the Cisco PAM Desktop Software This chapter describes how to install the Cisco PAM desktop client software, log on to Cisco PAM, and begin configuring access control features
More informationRESOLV EDI CONTROL. User Guide Version 9.2 for HANA PRESENTED BY ACHIEVE IT SOLUTIONS
RESOLV EDI CONTROL User Guide Version 9.2 for HANA PRESENTED BY ACHIEVE IT SOLUTIONS Copyright 2011-2016 by Achieve IT Solutions These materials are subject to change without notice. These materials are
More informationUser Guide Product Design Version 1.7
User Guide Product Design Version 1.7 1 INTRODUCTION 3 Guide 3 USING THE SYSTEM 4 Accessing the System 5 Logging In Using an Access Email 5 Normal Login 6 Resetting a Password 6 Logging Off 6 Home Page
More informationCA Agile Vision and CA Product Vision. Integration Guide
CA Agile Vision and CA Product Vision Integration Guide Spring 2012 This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation
More informationBANNER 9 QUICK NAVIGATION GUIDE
Application Navigator Application Navigator provides a single interface to navigate the Banner 9 JAVA pages. It is a tool that allows you to go back and forth between the current Banner forms and the new
More informationElectronic Appraisal Delivery (EAD) Portal. FHA EAD General User Guide
Electronic Appraisal Delivery (EAD) Portal FHA EAD General User Guide Last Updated: October 2015 FHA EAD General User Guide Page 2 of 87 Version 1.3.1 TABLE OF CONTENTS INTRODUCTION... 6 WHAT IS THE ELECTRONIC
More informationHP Project and Portfolio Management Center
HP Project and Portfolio Management Center Software Version: 9.30 HP Demand Management User s Guide Document Release Date: September 2014 Software Release Date: September 2014 Legal Notices Warranty The
More informationCisco UC Integration for Microsoft Lync 9.7(4) User Guide
First Published: August 05, 2014 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
More informationINSTITUTE BUSINESS SYSTEMS IMSS COGNOS REPORT STUDIO GUIDE
INSTITUTE BUSINESS SYSTEMS IMSS COGNOS REPORT STUDIO GUIDE Table of Contents Logging into Cognos... 3 Viewing Summary Information... 6 Running a Report... 6 Rerunning a Report... 9 Comparing Summary Information...
More informationSecureAssist IntelliJ Plug-in User Guide June 2016
SecureAssist IntelliJ Plug-in User Guide June 2016 Copyright 2016 by Codiscope, LLC. All rights reserved. No part or parts of this documentation may be reproduced, translated, stored in any electronic
More informationPega Call CONFIGURATION AND OPERATIONS GUIDE FOR CTI LINK SERVER WITH ENGHOUSE INTERACTIVE CT CONNECT CTI VERSION
Pega Call CONFIGURATION AND OPERATIONS GUIDE FOR CTI LINK SERVER WITH ENGHOUSE INTERACTIVE CT CONNECT CTI VERSION 7.21.1 Copyright 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For
More informationPowerSchool 7.x Student Information System
PowerSchool 7.x Student Information System Released May 2012 Document Owner: Documentation Services This edition applies to Release 7.2 of the PowerSchool software and to all subsequent releases and modifications
More informationBatch and Import Guide
Batch and Import Guide 06/13/2017 Blackbaud Altru 4.96 Batch and Import US 2017 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means,
More informationSecureAssist Eclipse Plugin User Guide December 2015
SecureAssist Eclipse Plugin User Guide December 2015 Copyright 2015 by Codiscope, LLC. All rights reserved. No part or parts of this documentation may be reproduced, translated, stored in any electronic
More informationPowerSchool Student and Parent Portal User Guide. https://powerschool.gpcsd.ca/public
PowerSchool Student and Parent Portal User Guide https://powerschool.gpcsd.ca/public Released June 2017 Document Owner: Documentation Services This edition applies to Release 11.x of the PowerSchool software
More informationPegaDISTRIBUTION MANAGER (IOS) for PegaRULES Process Commander. Installation and Configuration Guide
PegaDISTRIBUTION MANAGER (IOS) for PegaRULES Process Commander Installation and Configuration Guide Version 3.3.5 August 2006 Copyright 2006 Pegasystems Inc., Cambridge, MA All rights reserved. This document
More information