Skip to main content


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

Importing the application file

Updated on September 3, 2021

The system data and rulesets for Pega Customer Relationship Management are loaded during this task.

Pega CRM Update Guide
Note: Updating your application does not affect client-defined operators.
  1. Log in to Pega Platform (https://<hostname>:<port>/prweb) by entering the administrator ID, for example, [email protected] and the password that you used during Pega Platform installation.
  2. In the header of Dev Studio, click ConfigureApplicationDistributionImport.
  3. Select the Rules\PegaCRM.jar file from your distribution media, and then follow the wizard instructions.
    Note: If using a Microsoft SQL Server database, a server setting might cause the import to fail when the import is 99% complete. This is due to an orphan instance that is not used in any functionality and does not cause any functional issues. If this happens, repeat the import and select the File on server option. The Import wizard will install the remaining instances.
  4. Select the Enable advanced mode to provide granular control over the import process check box. When that check box is selected, the wizard displays all instances in the current environment that have a newer version of the RAP being imported. For each instance, you decide whether to override the instance or skip the import.
  5. For schema changes, depending on your site's requirements, select either Automatic or Manual, and then continue following the wizard instructions.

    If you select Manual, see Viewing and applying schema changes.

    Note:
    • For Pega Customer Service version 8.4.4 and later, if your application uses IBM DB2 z/OS, there are changes to the pca_work_service_table that require manual column changes. For information, see Importing schema changes with columns that require changes on IBM DB2 z/OS.
    • During the manual process, the wizard displays a Pre-existing rule conflict warning for rules that already exist in the system in a different ruleset. In the Pre-existing rule conflicts section, select the Replace check box for all of the rules that are listed to ensure that the rules are moved to the correct rulesets.
  6. When the import is complete, click Done.
  7. If a PegaCRM_Patch.jar file is present on the media, repeat steps 2 to 3 of this procedure to import the patch releases.
  8. Optional: Verify the application rules.
    1. In the navigation pane of Dev Studio, click RecordsApplication DefinitionApplication.
    2. Confirm that the following application rule or rules are displayed in the list:
      • CustomerService 8or CustomerService 8.5
      • PegaSalesAutomation.8 or PegaSalesAutomationCosmos.8

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us