Pega Foundation for Life Sciences

Implementation Guide
8.3
 ©2019 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 document is the property of:
Pegasystems Inc.
One Rogers Street
Cambridge, MA 02142-1209, USA
Phone: 617-374-9600 Fax: 617-374-9620
www.pega.com
Document: Pega Foundation for Life Sciences Implementation Guide
Publication date: September 06, 2019

Feedback
If you have comments for how we can improve our materials, send an email to AppDocBug@pega.com.

ii | Implementation Guide
 Contents

Contents

Application overview................................................................................................................................................................................. 5

Preparing for the implementation..........................................................................................................................................................6

Creating the application.............................................................................................................................................................................6
Generating specification documents........................................................................................................................................................7
Generating the Application profile............................................................................................................................................. 7
Generating the Application document...................................................................................................................................... 7
Generating the Specification document.................................................................................................................................... 7

Building features........................................................................................................................................................................................8
Implementing case types and attributes.................................................................................................................................................8
Adding case types.........................................................................................................................................................................8
Mapping case type or data type classes to a database table................................................................................................ 8
Application data model.............................................................................................................................................................................. 9
Adding properties to data types................................................................................................................................................ 9
Using the MedDRA data model.............................................................................................................................................................. 10
Updating the MedDRA database and tables.......................................................................................................................... 10
Configuring the MedDRA browse in cases..............................................................................................................................11
Configuring the Medicinal products data model................................................................................................................................. 11
Configuring database tables..................................................................................................................................................... 11
Configuring the Medicinal products browse UI......................................................................................................................12
Configuring WHODD format types...........................................................................................................................................12
Configuring Field-level auditing.............................................................................................................................................................. 13
Selecting field-level auditing flows........................................................................................................................................... 13
Configuring properties for audit functions to ignore............................................................................................................13
Additional field-level auditing configuration........................................................................................................................... 14
Configuring auditable notifications........................................................................................................................................................ 14
Generating external assignments.............................................................................................................................................14
Configuring external assignments............................................................................................................................................15
Using the PDF eForms Accelerator........................................................................................................................................................ 16
Using the Generate from Existing PDF eForms module....................................................................................................... 16
Using the Generate from New PDF eForms module.............................................................................................................16
Implementing the security model and organization structure.......................................................................................................... 17
Implementing your authentication scheme............................................................................................................................17
Authorization scheme................................................................................................................................................................ 17
Defining your access groups.......................................................................................................................................18
Defining access roles and privileges..........................................................................................................................18
Configuring your organization structure................................................................................................................................. 18
Operator attributes.................................................................................................................................................................... 18
Configuring the operator work group....................................................................................................................... 18
Configuring the operator skills................................................................................................................................... 19
Configuring the operator calendar............................................................................................................................ 19
Customizing the user experience...........................................................................................................................................................19
Designing an application skin and styles................................................................................................................................ 19
Designing for screen performance.......................................................................................................................................... 20

Implementation Guide | iii

Contents

Packaging a new application................................................................................................................................................................. 21

Merging application changes.................................................................................................................................................................. 21
Packaging an application for migration.................................................................................................................................................21
Importing the packaged application...................................................................................................................................................... 21

Testing a new application.......................................................................................................................................................................22

Testing your application in the Build environment............................................................................................................................. 22
Testing in the test or production environments.................................................................................................................................. 22
Testing in the UAT environment............................................................................................................................................................. 23

Production maintenance and monitoring............................................................................................................................................24

Business rule maintenance in the Production environment..............................................................................................................24
Application health monitoring................................................................................................................................................................ 24
Identifying and reporting issues.............................................................................................................................................................24

iv | Implementation Guide
 Application overview

Application overview
The Pega Foundation for Life Sciences application provides industry-specific modules for rapid
deployment of solutions across your organization. The following reusable modules automate and
optimize key business processes.

Medical Dictionary for Regulatory Activities (MedDRA) code data model

• Simplifies MedDRA coding in your application.
• Provides built-in support for MedDRA coding, which facilitates the development of safety and
pharmacovigilance solutions.
• Provides advanced search functionality to quickly retrieve and assign the accurate coding.
• Let's you use the industry-standard codes for medical terms when classifying adverse events that are
associated with the use of medical product.

Medicinal products data model

• Provides reusable, flexible, and extensible built-in support for browsing medical products.
It consists of the following features:
• Pluggable UI element, which added into your browse module to directly access the medical products
support.
• Conditional sourcing, which let's you conditionally source product data into the following categories:
◦ National Drug Code (NDC) and Unique Ingredient Identifier (UNII) products
◦ WHO Drug Dictionary (WHODD) products

Field-level auditing
• Supports the life sciences regulatory requirements for audit and authentication purposes in any Pega
application.
• Enables auditing and authentication support with integrated audit trails.
• Improves compliance and reduces the compliant applications development effort.

PDF eForms Accelerator

• Reduces manual tasks, eliminates typing errors, speeds up the document review process, and
accelerates submissions.
• Directly maps Pega BPM application data with the PDF form templates and generates various types of
submissions and compliance reports.
• Provides you with enhanced eForm connector support for your common regulatory PDF eForms with
field mapping tools.

Implementation Guide | 5
Preparing for the implementation

Preparing for the implementation

To prepare the implementation environment and to create your application, complete the preparation
tasks.

Creating the application

Run the New Application wizard to create your application.

On the Organization landing page, create a customer organizational structure. The organization
structure is required so that the new application will have the appropriate class structure. For more
information, see the Organization chart tab on the Organization landing page.

Caution: If a Pega Foundation for Life Sciences application already exists in your system,
running the New Application wizard overwrites some existing application settings. This will cause
issues with your existing application. Having more than one active Pega Foundation for Life
Sciences application on the same Pega Platform instance is not supported. This includes custom
applications built by you and sample applications provided by Pega.

1. To create a new operator ID for running the New Application wizard, complete the following steps:
a. Log in to Dev Studio by using the operator ID administrator@pega.com and the password that
you specified for that operator.
b. Save a copy of the existing administrator@pega.com operator, and give it a name that identifies
it as an Application Setup operator.
c. Add the PegaLSIF:AppSetup access group to the new operator record, and then click the radio
button to the left of the access group to select it as the default access group.
When this access group is selected as the default access group, the New Application wizard opens
immediately when this operator logs in.
d. On the Work tab, update the organizational unit to point to the organizational structure created as
part of the prerequisite steps.
e. Save the new Application Setup operator.
2. Log in as the Application Setup operator.
3. Follow the New Application wizard instructions.
4. Click Go to app.

The New Application wizard creates a set of access groups for the application. Create your own operators,
and then apply the appropriate access groups.
The New Application wizard creates the application class structure for you. For more information, see
Class layers and class hierarchy and inheritance.

After you create your application, enable and extend configurable functionality and features to meet
your business needs. To learn more about the application, click Resources in the upper-right corner
of the Dev Studio or App Studio screen.

6 | Implementation Guide
 Preparing for the implementation

Generating specification documents

To avoid duplicating existing features, review the following documents to familiarize yourself with the
default rules and rulesets of your application. During the solution assessment, several requirements,
specifications, and other artifacts are captured to represent the scope of the work. If they are captured
in the Pega Platform, these artifacts can be reused to streamline the first production release scope
identification.
You can export application specification and requirements artifacts from the Pega Platform, and then
import them into your new baseline application so that you can build on the content that has already
been created. For more information, see Exporting specifications and requirements and Importing
specifications and requirements.
Follow these procedures to generate documents that define what is contained within your application:

Generating the Application profile

This document is created during the Sales stage and includes the process stages and steps, case types,
reports, requirements, specifications, participants, collaborators, and actors that are associated with the
implementation of your application. It is a document that defines the scope of the application, and it also
includes the results of the presale gap analysis.
When you generate this document, you can include process flow diagrams.
To generate the document, log into your application by entering your newly created credentials, and
follow the procedure in Generating an application profile document.

Generating the Application document

This document and its associated controls provide the ability to customize the presentation of the
application information based on the document's intended audience. When you run the Application
Document tool, you can include or exclude content by selecting and clearing various options.
During an implementation, this document reflects the current state of your application. The Application
Document tool automatically updates the content of your document as you modify and extend your
application to reflect additional requirements. If you have not yet built anything, the content of this
document is the same as the application profile.
To generate the document, log into your application by entering your newly-created credentials, and
follow the procedure in Generating an application document.

Generating the Specification document

This document shows all the specifications and linked requirements associated with your application
at the time that you generate the document. You can generate this document at any point during the
implementation life cycle to include any updates to the application's specifications and requirements.
Review this document before and after each sprint by using the available filters to tailor the content to
meet the business requirements of your implementation.
To generate the document, log into your application by entering your newly-created credentials, and
follow the procedure in Generating a specification document.

Implementation Guide | 7
Building features

Building features
The implementation team enables or extends features to meet your business requirements.
To configure application features, review the topics in the following sections:

Implementing case types and attributes

For a list of the case types, see the Product Overview on the Pega Foundation for Life Sciences product
page.

Adding case types

If you require a case type that is not similar to an existing case type, create a new one that meets your
business requirements. If you want to add additional request types to your change request, create them
as new case types.
For a list of the case types, see the Product Overview on the Pega Foundation for Life Sciences product
page.

1. In the navigation panel of Dev Studio, click Case types.

2. Click Add a case type.
3. Enter the Name for the new case type.
4. Optional: Review the Advanced Settings.
5. Click Submit.
6. Define the case life cycle.
7. Click Finish.

Mapping case type or data type classes to a database table

When you run the New Application wizard to create your initial case types and data types, the system
creates a default class group mapping for each case type and data type. The wizard also creates
associated database tables. The wizard maps the new implementation class to the appropriate database
table.
Mapping a class to a physical database table affects data storage and security decisions. For example, if
you expect the volume of the case types to be low, consider sharing the table with other case types.
To update the default database table to a user-specified database table, perform the following steps:

1. In the navigation panel of Dev Studio, click App.

2. Expand the SysAdmin category, and then click Database Table.
3. Open the class that you want to modify.
4. Review the default database name and the table name that the class points to.
5. To point the chosen database table to your specific class, edit the database name and table name.
6. To confirm your changes, click Save.
7. Click Test connectivity to check if the configuration succeeded. If the test results display errors, for
example, missing properties, review the data and correct them.

8 | Implementation Guide
 Building features

8. Update the class to point to the table specified above:

a. In the navigation panel of Dev Studio, click App.
b. Right-click the class name that you referred to in the steps above and select Definition.
c. On the General tab, click Test connection to check if the configuration succeeded.
9. Perform the steps above for the other case type or data type classes, if needed.

Application data model

The application provides a set of data types, data pages, and sample data, which you can use to begin
implementing your application. You will need to use the data from your system of record instead of using
the sample data provided by the application.
Data modeling involves creating a conceptual model of how data items relate to each other in an
application. In Pega Platform, the data model refers to a set of rules that work together to populate the
data in your application. The system displays this data to help you process the information and can help
you make decisions in your sales processes. The following rule types constitute your data model:

Data types
Data type is another name for a class in your application. It holds data that the application uses. A data
type has one or more data pages and several property definitions associated with it.
Properties
Properties define the format and visual presentation of data in your application.

Data pages
Data pages define the content of a clipboard page. Data pages also control the loading of that data
from a source system, as shown here.

When planning your data model, work with the data modeling resource at your site to understand the
attributes of the data types that need to be supported by your application.

Adding properties to data types

Data types categorize the data that your application uses. The data types that come with your application
have one or more data pages associated with them. Add properties to a data type to further customize it,
for example, by adding contact information to a data type that represents a user of your application.

1. In the Dev Studio navigation panel, click Data.

2. Click the data type that you want to modify.

Implementation Guide | 9
Building features

3. On the Data model tab, scroll to the bottom.

4. To add a property, click Add field. Add as many properties as your application requires. Repeat these
steps for any other data types, as necessary.
For information about data pages, see Data pages.

Using the MedDRA data model

Use the MedDRA data model to support advanced search of your industry-standard medical terms and
corresponding codes.
To benefit from the data model and associated look up capabilities along with the licensed data, perform
the following steps:

Updating the MedDRA database and tables

Set up the MedDRA database to use the module. By default, MedDRA tables are located in the PegaDATA
database. These tables have the industry standard columns and structure but the names are not prefixed
with 1_. The licensed data can be inserted into the tables and used without any extra configurations.

If you need to fetch the data from an already existing MedDRA database, update the Data-Admin-
DB-Table instances for MedDRA tables.

1. In the Dev Studio Explorer panel, click Records.

2. Click SysAdmin > Database Table to review its instances.
3. Click the database table name, for example MD_HIERARCHY.
4. Update the database, database table, and schema names. Enter the updated database table name
1_MD_HIERARCHY. You need to update the name if your tables are named according to the industry
standards or any other corresponding name.
5. To confirm changes, click Save.
6. To ensure that the mapping works correctly, click Test connectivity.
7. Perform steps 3-6 for all the MedDRA database tables listed below.
• HLGT_HLT_COMP > 1_HLGT_HLT_COMP
• HLGT_PERF_TERM > 1_HLGT_PERF_TERM
• HLGT_PERF_COMP > 1_HLT_PERF_COMP
• HLT_PERF_TERM > 1_HLT_PERF_TERM
• LOW_LEVEL_TERM > 1_LOW_LEVEL_TERM
• PERF_TERM > 1_PERF_TERM
• SOC_HLGT_COMP > 1_SOC_HLGT_COMP
• SOC_TERM > 1_SOC_TERM

10 | Implementation Guide
 Building features

Configuring the MedDRA browse in cases

The BrowseMedDRACodes section rule is a part of the PegaLSIFCore ruleset in @baseclass. To include
the MedDRA feature in your application, drag this section into a desired place in your layout. By default,
the advanced Browse option is configured to search for terms and codes, as well as browse through the
MedDRA structure. After you select a Preferred Term or Low Term from the lookup, the corresponding
code and term is set to MedDRACode and MedDRATerm properties in that page context.
To familiarize yourself with MedDRA browse in the LS MedDRA codes landing page structure, perform the
following steps:

1. Click Dev Studio > Life Sciences > LS MedDRA Codes .

2. To select a preferable searching method, click Browse Codes.
3. Click Select from the directory to see the hierarchy of MedDRA codes and terms and drill down into
more specific instances of each code.
4. Click Search for Terms/Codes to search for the particular parameters and options by terms or codes,
or preferred term (PT) and low level term (LLT) codes, either individually or together. Define your Word
Search parameters.
5. Select the desired code name. You can select multiple codes to add more than one code under a
parent data grid.
6. To review the selected codes, click Review.
7. Click Add MedDRA codes.

Configuring the Medicinal products data model

The Medicinal products data model in Pega Foundation for Life Sciences supports IDMP National Drug
Code (NDC) and Unique Ingredient Identifier (UNII) substance registry as well as the industry standard
WHO Drug Dictionary (WHODD) data models.
To configure the medicinal product data model in your implementation layer, perform the following tasks:

Configuring database tables

Pega Foundation for Life Sciences provides you with database tables to maintain and retrieve data for
both IDMP and WHODD schemas.

For more information, refer to the following materials:

• National Drug Code (NDC) website
• Unique Ingredient Identifier (UNII) substance registry
• WHO Drug Dictionary website
You can insert the product data into the Pega -provided database tables or point to the site-specific
database tables by updating the table configurations. The structure of the product data needs to
match the industry standard model provided by Pega.
To change the schema and table names to point to a specific database table, perform the following
steps:

1. Click Dev Studio Explorer panel > Records > Sysadmin > Database Table and search for the
database table instance that you want to update, for example: PegaLS-FW-Int-UNIINames.

Implementation Guide | 11
Building features

2. Update the database, database table, and schema names if necessary.

3. To confirm your changes, click Save.
4. To ensure that the mapping works correctly, click Test connectivity.
5. Perform steps 1-4 for all the database tables listed below:
• PegaLS-FW-Int-NDCProduct
• PegaLS-FW-Int-NDCPackage
• PegaLS-FW-Int-UNIIRecords
• PegaLS-FW-Int-UNIISynonyms

To configure the WHODD tables, search for the PegaLS-Int-WHO-Drug-C- class in the Data-
Admin-DB-Table instances. All of the WHODD specific instances will be visible there.

Configuring the Medicinal products browse UI

Use the Medicinal products browse UI to search for products in the IDMP and WHODD repositories. To
include the medicinal product browse UI in your application, launch the SearchMedProduct flow action
rule in @baseclass.
For example, if you want to launch this as a local action, which is triggered on the click of a link or a
button, set the following properties in the same page context:
GenericName - Non-proprietary name
TradeName - Proprietary name
MPID - Medicinal Product ID and so on
To populate more properties to your case-specific page context, extend the PopulateSelectedProduct
data transform rule in @baseclass.

Configuring WHODD format types

By default, Pega Foundation for Life Sciences supports the WHO Drug Dictionary C-format. To implement
support for a WHODD format other than C, for example B2, perform the following steps:

1. Create database tables required for the B2 format. You can load the data into the tables from the flat
files using control files that are a part of the WHODD licensed data dictionary.
2. Click Dev Studio > Data Model > Classes & Properties > Database Class Mappings and create the
corresponding class and properties for each table, using the New External Database Class Mapping
wizard.
3. Fill in all the necessary fields in all the presented steps and click Submit.
4. In the Dev Studio header search field, enter WHODDFormatSetting and select the Code-Pega-List
map value from the results.
5. Save the rule into your implementation layer. For additional information about locked and unlocked
rulesets, see Copying a rule or data instance.
6. Set the WHO_DD_Format format type value to B2.
7. Click Save.
8. In the Dev Studio header search field, enter DPLoadProductResults and select the Code-Pega-List
activity from the results.

12 | Implementation Guide
 Building features

9. Extend the GetB2FormatResults stub activity to fetch the data from B2 format tables.

Configuring Field-level auditing

Field-level auditing is bundled in the PegaLSIFAudit ruleset installed with the Pega Foundation for Life
Sciences application. Review the following prerequisites before configuring the Field-level auditing feature.
• Complete the development of all user interfaces and flow actions for the target work type. Ensure that
all rules are checked in. Field-level auditing may be reconfigured, but it is recommended to complete
the UI development first.
• Make sure the flow actions and associated sections on which the field auditing is to be configured
are present in the unlocked rulesets. The automatic configuration is not possible if a flow action is
generated manually.
If some of the flow actions are not visible in the Auditing configuration wizard field, it is possible that these
flow actions are associated with ancestor classes.
To configure, perform the following steps:

Selecting field-level auditing flows

After you configured particular flow actions as audited flow actions, the following changes are
automatically made.

1. Click Dev Studio > Life Sciences > LS Field Auditing .

2. Select the Ruleset, Ruleset version and Case/Supporting Type in which you want to enable field-level
auditing.
Note: The selection list does not display the locked ruleset versions.

3. Select the AUDIT? checkbox next to the flow action you want to configure auditing for.
4. Click Configure Auditing to confirm the assignment.

• Pre and post activities are automatically added to flow actions on the Action tab to capture audit
events.
• Audit buttons are added to all sections references in the selected flow actions to support audit
functions. For more information, see Additional field-level auditing configuration.
• The IgnoreFromAuditing data transform rule is added. For more information, see Configuring
properties for audit functions to ignore.

Configuring properties for audit functions to ignore

Use the IgnoreFromAuditing data transform to create a list of properties, that the audit functions
ignore.

1. In the Dev Studio header search field, enter IgnoreFromAuditing and select the Work- class data
transform from the results.
2. Save the rule into your implementation layer. For additional information about locked and unlocked
rulesets, see Copying a rule or data instance.
3. Add all of the properties that the auditing functionality ignores.
4. Click Save.

Implementation Guide | 13
Building features

Additional field-level auditing configuration

Pega Foundation for Life Sciences Field-auditing supports the following additional flexible options that you
can configure:
• Disable the electronic signature while confirming properties changes.
• Submit changes without entering changes reason.
• Bypass the confirmation dialog.
• Show or hide the audit buttons.
To configure, edit the LSFieldAuditSettings map value rule the following way:

1. In the Dev Studio header search field, enter LSFieldAuditSettings and select the @baseclass map
value from the results.
2. Save the rule into your implementation layer. For additional information about locked and unlocked
rulesets, see Copying a rule or data instance.
3. Configure each column and row based on your business requirements.

AuthenticationMode
Determines if the electronic signature is mandatory while making changes to the auditing
properties. Set to None to disable authentication, or leave as Simple Auth to use ID and password
for authentication.
ReasonsForChangeReqd
Determines if entering reasons is mandatory while making changes to the auditing properties. Set
to None to disable mandatory reasons field, or leave as All to enable.
BypassConfirmation
Determines if the modal dialog for changes confirmation is displayed or not. Set to false to
disable, or true to enable.
ShowAuditButtons
Determines if the View Audit History and Review and Confirm Audited Modifications buttons
are displayed or not. Set to false to hide, or leave as true to show the buttons.

4. Click Save.

Configuring auditable notifications

Use the auditable notifications to create multiple simultaneous assignments for a list of external users
that can branch for the main flow. The external interactions generates unique user IDs and passwords
that are sent through email to each user. User authentication and tracking can be used to support
regulatory requirements for interactions with various external parties.
To include auditable notifications in your application refer to the following procedures:

Generating external assignments

After the rules are generated, you can include them in the assignment shapes of the flows on which you
want to generate the external notifications.

1. Click Dev Studio > Life Sciences > LS Auditable Notifications.

2. Select a Ruleset, Ruleset version, Parent Work Type and Child Work Type for External
Assignment.

14 | Implementation Guide
 Building features

3. Add a row for each external assignment rule that you want to generate and enter the parameters
based on the suggestions given below:

External assignment name

Enter the name of the external assignment that you want to create.
Direct Web Access (DWA) flow action
The name of the flow action that sends the external assignment.
Local action
Automatically populated based on the generated rules.
DWA engage flow
Automatically populated based on the generated rules.
Configuration status
Indicates whether the generate process was successful or not.

4. To create rules and automatically populate the remaining fields on the display click Generate External
Assignment Rules.

Configuring external assignments

To successfully set up auditable notifications, configure external assignments by performing the following
steps:

1. Click Dev Studio > Org & Security > Organization > Operators and search for the Data-Admin-
Operator-ID instance External operator.
2. Double-click the External operator ID to open it.
3. On the Security tab, ensure that the License type value is set to Invocation.
4. In the Dev Studio Explorer panel, click Records > Integration Resources > Email Account.
5. Ensure that the Default instance of Data-EmailAccount is set up to successfully send the emails. You
can open this instance and click Test connectivity to check the configuration status.

The external assignment (local action that was generated by the landing page) should be included
in the appropriate assignment of the main process flow. The email IDs of all the external users to
whom the assignments are to be sent are provided in this local action. When the local action is
submitted, each external user receives a different instance of the external assignment. The Work-
class EngageExternalQuickMultiple flow is automatically invoked to send emails to the external
users.
Each external user receives two emails, one with a unique link to their assignment and a second
with a randomly generated password for authentication. The GeneratePassword function of
ExternalAssignmentsLS library generates the random password.
External user’s responses can be tracked using reports that are available upon completion status.
For more information about external assignments, see External assignments through Directed Web
Access.
To display the external assignments that have been sent as notifications for a work object use the
DisplayExternalAssignments section rule in the Work class.
1. In the Dev Studio header search field, enter DisplayExternalAssignments and select the
Work- section rule from the results.

Implementation Guide | 15
Building features

2. Save the rule into your implementation layer. For additional information about locked and
unlocked rulesets, see Copying a rule or data instance.
3. Click Save.

Using the PDF eForms Accelerator

Use the PDF eForms Accelerator to generate and maintain activities required to create and attach PDF
reports to a desired work object.
To configure, choose one of the following modules depending on your business needs:
• Generate from Existing PDF eForms to update the existing activity rule
• Generate from New PDF eForms to create a new activity rule

Using the Generate from Existing PDF eForms module

Use the Generate from Existing PDF eForms module to add and update properties to the existing PDF
eForm sections and repopulate the existing activity rule that can be referenced in the application flow or
processes. The activity rule can be invoked from a desired location to attach a PDF report to a work object
repository.

1. Click Dev Studio > Life Sciences > LS Reports > Generate from Existing PDF eForms .
2. Fill in all the required fields, such as: Ruleset, Ruleset version, Applies to Class, and PDF Report
Name associated with your work object.
3. From the Activity Applies to Class list, select where you want to create the activity.
4. Enter the new activity name.
5. For each of the listed eForm Field name instances, enter the appropriate Mapped Application
Property value to populate the form fields.
Normal string formatting operations, such as concatenation (+) and new line character (\n), are
supported. Surround these characters with double quotes, for example: "+".
6. To create the activity in your selected class, click Generate eForm Activities.

Using the Generate from New PDF eForms module

Use the PDF eForms reporting module to upload a PDF sample report based on the new activity rules.

1. Click Dev Studio > Life Sciences > LS Reports > Generate from New PDF eForms .
2. Fill in all the required fields associated with your work object.
• New Data Class Name (Data-)
◦ If you enter xyz as a class name, the new data class will be named Data-xyz.
• Ruleset
• Applies to Class
◦ The eForm file and Map eForm rules are created in the class you select. Choose this class at the
class group level to use the same rules across the work types.
• New Page Property Name
◦ A form page property name.

16 | Implementation Guide
 Building features

• Ruleset version
3. Click Browse and search for the template in your local directory.
4. Click Upload PDF and Continue.
5. Select the Activity Applies to Class based on where you want to create the activity.
6. Enter the new activity name.
7. For each of the listed eForm Field name instances, enter the appropriate Mapped Application
Property value to populate the form fields.
Normal string formatting operations, such as concatenation (+) and new line character (\n) are
supported. Surround these characters with double quotes, for example: "+".
8. To create the activity in your selected class, click Generate eForm Activities.

Implementing the security model and organization

structure
Define the authorization and authentication strategies for your application.

Authentication
Proves to the application that you are who you say you are.
Authorization
Determines the functions that you can perform in the application. This corresponds to an access group
and role configuration.

Security planning also involves setting up the organization structure and operator attributes. The
application provides security in the form of access settings and denial rules. Many integration rules also
incorporate authentication.
For more information about the additional aspects of security, enroll in the Lead System Architect course on
Pega Academy and cover the Security lessons that correspond to the following topics:

Implementing your authentication scheme

Your site can use a centralized, automated means of maintaining operator data instead of maintaining it
manually in your application.

1. Discuss Authentication schemes with your site's security and application server teams.
2. Determine the appropriate authentication type.
For more information on authentication scheme planning, see Authentication in Pega Platform.

Authorization scheme
Pega Foundation for Life Sciences comes with a predefined set of access groups, roles, and privileges.
You can use the application roles as a starting point, but you should create your own application-specific
access groups and roles to avoid any future problems when upgrading.
Other rule types such as sections, flow actions, and activities use roles and privileges to allow access to
these rules at run time.

Implementation Guide | 17
Building features

Defining your access groups

Define the access groups that you want to add to your application.

1. Identify additional access groups that are needed for your application.
2. Identify portals associated with these access groups.
For more information, see Viewing access groups and operators.

Defining access roles and privileges

You can associate one or more roles with an access group. Roles are additive. The more roles that you add
to an access group, the more authorization there is. Privileges can be associated with one or more roles.

1. Determine which roles are needed for your application.

2. Determine which privileges to associate with each role.
3. Associate each role with an access group.
For more configuration information, see Groups and roles.

Configuring your organization structure

Use the organization structure for routing and reporting within the application. Typically, the application
organization structure does not map operators exactly to the site's organization chart but instead, it maps
the work that those operators do.
Tip: For design guidance, see Organization landing page.

1. In the header of Dev Studio, click Configure > Org & Security > Organization > Organizational Chart.
2. Review the existing structure.
3. Determine the organization, division, and unit levels of the hierarchy.

Operator attributes
An operator's access group affects what the operator can do in the application. In addition to the access
group, the following fields in the operator record influence how the application handles assignment of
work to the user:
• Work group
• Skills
• Calendar
Tip: In many implementations, it is more efficient for the application to set values in the operator
record during the authentication process than it is to have an administrator manually maintain
these records. These rules must be configured as part of the authentication mechanism for your
site. For more information, see Authentication services.
For more information, see Operators.

Configuring the operator work group

The work group setting in the operator record affects how your application delivers work to the operator.
Review the Operator record and determine the rules for assigning a work group to an operator or the role
that multiple operators hold.

1. In the header of Dev Studio, click Configure > Org & Security > Organization > Operators.

18 | Implementation Guide
 Building features

2. Select an operator ID.

3. On the Work tab, review the work group information for the operator record.
4. Determine your policy for assigning a work group to an operator or the role that multiple operators
hold.
For more information, see Fields for operator work groups, work queues, and schedules.

Configuring the operator skills

Skill settings in the operator record affect how the application routes work to the operator. Skill settings
also affect how the application gets the most appropriate work when using the Get Next Work feature.
You must determine the skills that are appropriate for your application and operators.

1. Define the skills that are needed for the application.

2. Determine which operator records or roles should be associated with those skills.

Configuring the operator calendar

The application calendar affects date calculations within the application, such as the date between
business days calculation, and the SLA goal and deadline date calculation. The calendar on the operator
record is relevant only if you have users who are not working in the same time zone as the rest of the
organization. Otherwise, the application uses the calendar on the organization record and you can skip
this step.
Operator calendars will have an impact on chat availability. If a chat request comes in after or before
the business hours defined in the specified calendar, then the requestor receives "Off-hours behavior"
message.

1. Determine the calendar instances that are needed for your application.
2. Determine which operator roles need a distinct calendar.
3. Determine the operator location.
For more information, see More about Calendar data instances.

Customizing the user experience

While Pega Foundation for Life Sciences is fully functional immediately after installation, you might change
portions of the user experience (UX) to meet the needs of the users at your site.

Designing an application skin and styles

Your site very likely has user experience (UX) standards for the appearance of your applications. Your task
is to determine which styles have to change to adhere to those standards. Determine which application
appearance styles have to change to match your organization standards.

1. In the header of Dev Studio, click Configure > User Interface > Skins, interfaces, & templates.
2. On the Skins tab, double-click the pyEndUser skin.

3. Click the Component styles tab.

4. Review each component.
Note: As you plan your application styles, consider using mixins to provide incremental style
changes. For more information, see Using mixins in the skin to drive consistency and efficiency.

Implementation Guide | 19
Building features

Designing for screen performance

You want your application to respond immediately as your end users interact with customers. As you
design your user interface, complete the following steps:

1. Review transactional service level agreements.

The customer details must be available in one second or less while a representative is on the phone
with the customer.
2. Review service performance, such as how long it takes back end systems to gather the data needed to
display customer details.
3. Review data requirements to determine which fields contain the information that the representatives
absolutely need for the task that they need to perform.
4. Determine if any network configuration could cause latency.
Representatives who are logged in through a corporate VPN or in a remote location might cause an
issue.

20 | Implementation Guide
 Packaging a new application

Packaging a new application

To migrate a new application to a different environment, you must first package the application so that it
can be imported to the new environment.

Merging application changes

If you developed your application features in separate branches, use the Merge Branches wizard to
merge the branches before you package the application. The wizard shows any merge conflicts so that
you can correct them before you merge the branches.

Packaging an application for migration

Before you can migrate a new application to a different environment, you must package the relevant data
instances and rulesets into a product rule. The product rule is an instance of Rule-Admin-Product, and
it is referred to as the RAP file.

1. In the header of Dev Studio, click Configure > Application > Distribution > Package to start the
Application Packaging wizard. For information about using the wizard, see Product rules.
2. Complete each page of the Application Packaging wizard.
3. On the last page of the wizard, click Preview.
4. Review the contents of the generated RAP file.
5. On the last page of the wizard, click Modify to make any changes.
6. When the RAP file is complete, click Export.
The wizard creates a .ZIP file in the ServiceExport directory on the current application server node.

Importing the packaged application

To deploy a new application to a different environment, import the .ZIP file that contains the packaged
application to the new environment.

1. In the header of Dev Studio, click Configure > Application > Distribution > Import.

2. Use the Import wizard to import the target .ZIP file. For more information, see Importing rules and data
from an archive by using a wizard.
For information about how to swap the database connection pointers to your production database
after an import to a production environment, see the Pega Platform Upgrade Guide at Deployment
Guides.

Implementation Guide | 21
Testing a new application

Testing a new application

Testing a new application involves testing in different environments.

Testing your application in the Build environment

Test a new application in the Build environment before migrating the application to a test or production
environment. Testing in the Build environment enables you to verify that basic functionality and interfaces
work correctly and that performance is acceptable.

1. Run functional tests to test specific features from the end-user perspective.
2. Use the Performance tool to measure the performance of the application. For more information, see
Track system utilization for a requestor session with Performance Analyzer.
• Prior to extending your site-specific Pega implementation, establish a performance benchmark
(baseline) by using the Performance tool. This allows subsequent, iterative performance tests
against the baseline to help identify any degradation in performance resulting from development
efforts.
• Use the Performance tool to check the performance of the following features:
◦ Search
◦ Account selection
◦ Loading of components
◦ Kickoff of all service intents. For this unit testing, automated scripts are recommended but not
required.
• Save the test results so that you can compare them to future test results to determine whether an
application update has a performance impact.
3. Verify that the Pega-provided reports and your custom reports run successfully, and that they show
your implementation layer data, rather than the default demonstration data. This can be an automated
test.
4. Test all integrations, both independently and with associated integrations. 
Test integrations for any optional Pega Foundation for Life Sciences components and other
applications that you plan to use. See the product documentation for the component or application to
determine which product components to test.

5. Test security. Test the most common roles to ensure that the required access groups are configured
and point to the correct software version.

Testing in the test or production environments

After you import the application to a test or production environment, test the application in the new
environment to verify that it works correctly in that environment.

1. Verify that the source and the destination files are the same.
2. Run functional tests to test specific features from the user perspective.
3. In the test or production environment, run the Application Guardrails Compliance Score to ensure that
the application meets guardrails.

22 | Implementation Guide
 Testing a new application

4. Verify that the Pega-provided reports and your custom reports run successfully, and that they show
your implementation layer data, rather than the default demonstration data. This can be an automated
test.
5. Test all integrations, both independently and with associated integrations.
Test integrations for any optional Pega Foundation for Life Sciences components and other
applications that you plan to use. See the product documentation for the component or application to
determine which product components to test.

6. Verify that the integrations point to the correct system of record, and not to the system of record for
the Build environment.
7. Test security. Test the most common roles to ensure that the required access groups are configured
and point to the correct software version. Use these common roles in your smoke tests (see next step).
8. Run a smoke test to compare the source and destination environments. Verify that all tests that pass
in the Build environment also pass in the test or production environment. If anything fails, compare
the environments to determine whether a difference in environment could cause the test to fail. If
the environment caused the failure, either fix the issue that caused the failure or adjust the test as
appropriate for the new environment.
9. Run performance tests to verify that performance meets expectations. Pega recommends automated
performance testing. Save the results so that you can compare them to future performance test results
to determine whether an application update has a performance impact.

Testing in the UAT environment

After you complete testing in a Test environment, it is common to perform User Acceptance Testing (UAT)
in a designated UAT environment, which could be a pre-production environment. UAT ensures that users
will be able to successfully complete work and meet business objectives.
Note: Organizations that use Scrum for application development will complete less formal UAT as
part of each sprint cycle.

1. Verify the integrity of the UAT environment.

2. Have the end-users (or business analysts acting the role of end-users) run scripts to test all scenarios
including boundary and exception testing. The end-users (that is, the trainers, managers, and
directors), perform the following steps during UAT:
a. Verify that there are no major issues.
b. Review changes to understand the features.

Implementation Guide | 23
Production maintenance and monitoring

Production maintenance and monitoring

Production maintenance and monitoring include the following procedures:

Business rule maintenance in the Production

environment
As a manager, you can update Dialogs, and Coaching Tips in the production environment by using
the Tools > Configuration option available in each process action of the case type. This feature allows
managers to change these options without having to wait for a rule deployment. Managers must have the
same privileges associated with the PegaCA:Manager role in order to maintain these rules.
You can give managers the ability to update other rule types in the production environment. For example,
managers can update the Goals and Deadline for a certain case type. These rules must be delegated in
Dev Studio first. For more information on rule delegation, see Delegating a rule or data type.

Application health monitoring

Pega Autonomic Event Services is an application that automatically monitors, retrieves, and organizes the
alert data from one or more clustered systems throughout the enterprise. Pega also provides the Pega
Predictive Diagnostic Cloud, which allows you to benefit from Pega Autonomic Event Services without
installing it locally. Pega Predictive Diagnostic Cloud is a Software as a Service offering of Pega Autonomic
Event Services.
Implementing the following best practices in your application can help to ensure optimal response times
and overall application health:
• Segment application agent processing to a dedicated JVM (Java Virtual Machine). This configuration
ensures that end users do not have to share resources with background processes.
• Monitor integration response time. Over time, slow integration points can cause average handle times
to increase. When queues start to grow, it becomes very difficult to recover, which might require usage
of offline services or a backup application.

Identifying and reporting issues

As with any application, your users will encounter issues that they need to report as they begin to use
the application. When deploying your application to the production environment, complete the following
steps:

1. Identify operational staff who will be responsible for responding to issues reported in the production
environment.
2. Establish procedures with those resources to triage, respond to, and escalate issues.
3. Determine procedures for delivery of changes to the production environment.

24 | Implementation Guide