Published Release Notes

New roles required for system management features and APIs after upgrade

The pzSystemOperationsObserver and pzSystemOperationsAdministator privileges are no longer used for accessing system management features in Admin Studio and for system management APIs. Pega Platform™ has new privileges for individual system management functions and new roles configured with these privileges. Use the following roles to access system management features and APIs:

• PegaRULES:SysOpsAdministrator – has all administrator and observer privileges
• PegaRULES:SysOpsObserver – has all observer privileges
• PegaRULES:SysAdm4 – has all administrator and observer privileges

After upgrading, you can include one or more of these roles in your access group or create a custom role. For more information about access roles, see Access roles.

Use spaces to collaborate with users

You can now collaborate with other users in your application on a specific area of interest by using spaces. By restricting the discussion of certain topics to the users of a space, you can avoid broadcasting irrelevant messages to all users in your application.

For more information, see:

• App Studio – Collaborating with users by using spaces
• Dev Studio – Collaborating with users by using spaces

Collaborate on shared content by using documents

You can now share additional information about cases with all users in your application by using documents. Documents enable you to view shared content on a landing page and collaborate on the content with other users in Pulse so that you can resolve cases more quickly.

For more information, see:

• App Studio – Collaborating on shared content by using documents
• Dev Studio – Collaborating on shared content by using documents

Ability to search case attachments in Pega Cloud Services

File repositories in Pega Cloud Services are now indexed. Indexing allows your application users to search case attachments from end user portals based on content and metadata.

Enabling access to upgraded help

After upgrading to Pega Platform ™ 8.1, the default URL to the upgraded help files might be incorrect. To enable access to the latest help files, reset the URL:

1. In the header of Dev Studio, click Configure > System > Settings > URLs.
2. Enter the Online Help URL:

   https://community.pega.com/sites/default/files/help_v81/

3. Click Save.
4. Log out and log back into Pega Platform.

WSDL generation error prevents invocation of SOAP services

Status

A Known Issue was introduced in the 8.4.2 Pega Platform patch release, which impacts both upgrades and new installations of that version.

Description

Due to changes introduced in the SOAP functionality for the case-mismatch error in SR-D98509/INC-119725, the WSDL is being generated for SOAP services with an incorrectly-capitalized element, which prevents the service from being invoked.  The element should be “name” instead of “Name”.

Workaround

Clients must perform the following workaround after they define a new SOAP connector in Pega Platform:

1. To download the WSDL from Pega Platform:
   1. After using the SOAP Wizard (Dev Studio > Configure > Integration > Services > Service Wizard) the WSDL URL is shown at the bottom right of the Dev Studio screen.
   2. Click the URL to display the XML.
   3. Save the WSDL file to your local system.
2. In the text editor of your choice, modify "Name" to "name" in every <element “name” = … > tag in the WDSL.
3. Save your changes to the local file.
4. To reload the WSDL into Pega Platform:
   1. In Dev Studio, open the Configure menu.
   2. Select Integration > Connectors > Create SOAP Integration.
   3. In the New SOAP integration wizard, select Upload WSDL from File.
   4. Complete the upload using the wizard prompts.

This is a design-time issue, not a run-time issue; therefore, clients only have to perform this workaround process once. Existing SOAP services should not be impacted; however, if clients modify an existing SOAP service definition by re-running the wizard, clients must reapply the workaround for Pega Platform to recognize the SOAP definition changes.  

Resolution

This issue will be addressed in the Pega Platform Patch Release 8.4.3.  Clients who upgrade to that version or later should not see this issue.