Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

COVID-19 Employee Safety and Business Continuity Tracker - FAQ

Updated on April 5, 2022

Why are maps visible, but not displaying data?

The Employee Safety and Business Continuity Tracker application accelerator does not ship with sample employee data. You can manually enter data into the records of the Employee Details data type, by using the full Country & State/Province names in the corresponding columns (for example, United States, California, France, Ile-de-France). For more information about working with Map reports, see Use a map to illustrate a report.

Why do colors on maps change based on the number of cases?

See the Customize the map section in Use a map to illustrate a report.

Why are maps not showing up in the Manager or Executive Dashboard?

The application accelerator ships with the Pega Maps version 1 component, which is certified for use on Pega platform 8.1. If you have installed the application accelerator on Pega Platform™ 8.2 or higher, you must download and install the Pega Maps version 2 component from the Pega Marketplace. When installing the version 2 Maps component, clear the import aged updates option.

What are the support options?

Use the Installation Guide and the Implementation Guide to get started.

Is the application HIPAA compliant?

Pega’s development platform and all strategic applications – including the Pega COVID-19 Employee Tracker for Safety and Business Continuity application accelerator – have standards-enabled data models to maintain compliance with standards and regulations within clients’ respective industries.

Pega also provides the necessary controls and parameters to configure applications to meet any regulatory requirements to help protect employees’ data. This includes federal and state laws such as HIPAA (Healthcare Information Privacy Act) and HITRUST, which help protect user data – specifically protected health information (PHI) from being used in ways it shouldn’t.

Each organization should deploy Pega COVID-19 Employee Tracker for Safety and Business Continuity in accordance with their own business and information management policies. The app also has the ability to enable employees to opt-out of questions.

Can I have the password to unlock the locked rulesets?

No, we do not provide passwords to locked rulesets. Create your own Implementation layer and proceed from there.

Is there sample data?

We are not providing sample data. For more information, see the Installation Guide.

Does the application work with MSSQL?

See the Pega Platform Support Guide on Pega Community for any questions related to what is supported by Pega Platform.

What versions of the Platform does the application run on?

The v. 1.0 and 1.1.2 version of the app was built on Pega Platform 8.1. That version has been tested to work on Platform v8.1, 8.2 and 8.3. The v. 8.4 version of the app was built on Platform 8.4 and requires Platform 8.4 to run.

We have also tested the Responsive UI on iPhone and Google Pixel mobile devices. For any questions regarding the technologies supported by Pega platform, see the Pega Platform Support Guide on Pega Community.

Is the COVID-19 application accelerator GDPR compliant?

Pega is committed to providing secure solutions that assist our clients to implement their data privacy and security strategy. We do so by allowing clients to configure Pega to implement their strategy for complying with data privacy and security best practices, including data processor obligations under GDPR and other data privacy laws. Currently, there is no official certification for GDPR compliance. Pega Platform clients can download our free GDPR functionality, a set of customizable templates and sample processes that enable companies to quickly stand up an automated GDPR request process and orchestrate their own interpretation of GDPR compliance across their enterprises. Pega Cloud complies with the applicable processor provisions under GDPR and other data privacy laws as a technology service provider. Pega deployed applications can be designed and deployed during the implementation of clients’ compliance strategies for a variety of regulations including EU Accounting Rules and GDPR. To learn more about our commitment to the GDPR, see the GDPR Strategy: Is your business GDPR-ready?whitepaper.

Is there an upgrade path from version 1.1.2 to version 8.4?

Both versions contain the same functionality. There is no upgrade path from v1.1.2 to v8.4. The v8.4 version was developed to highlight some of the new features available in Pega Platform v8.4 such as Pega App Studio and the Pega Express Delivery Approach.

After downloading the application and installing on-premises, the following error occurred: "There was an error while executing the report" (versions 1.0 and 1.1.2 only)

This issue shows up in any environment that has other applications installed that are using the pyCaseManager portal. To fix this issue, delete the DEFAULT!CMDASHBOARD!DEFAULT  instance of SYSTEM-USER-DASHBOARD to revert back to the out-of-the-box dashboard for the pyCaseManager7 portal. This problem only impacts v. 1.0 and v. 1.1.2.

I upgraded the application accelerator from 1.0 to the 1.1.2 version. The system is not displaying the cases for employees that had previously been created (versions 1.0 and 1.1.2 only)

This problem appears when you sign in as an employee for which cases have already been created in the application. To correct the problem you must optimize several properties in the customer database table related to the implementation layer Work-COVID19RiskAssessment class. Optimize the following properties:

  • .AssessmentDetails.Risk
  • .AssessmentDetails.AssessmentID
  • .EmployeeDetails.Name
  • .EmployeeDetails.EmployeeID
  • .EmployeeDetails.StateProvince
  • .EmployeeDetails.pyCountry
  • .EmployeeDetails.WorkSite
  • .EmployeeDetails.HRName
  • .EmployeeDetails.EmailAddress
  • .Day7
  • .Day28
  • .Day14

This guidance has also been listed in the new version of the Installation Guide available with the application. For more information, see Planning for property optimization For more information about exposing properties and populating database columns, see Exposing properties and populating database columns.

Helpful Links:

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us