Reports on pc_work_agile table fail in Pega 7.3 on MSSQL
Valid from Pega Version 7.3
This failure applies only to Pega® Platform 7.3 on systems running Microsoft SQL Server. In Pega 7.3, the capitalization for the column name pc_work_agile.pzPvStream is incorrect. The correct capitalization is pzPVStream. To prevent reporting failures on the pc_work_agile table, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column after you install Pega 7.3:
EXEC sp_rename ‘data-schema-name.pc_work_agile.pzPvStream', 'pzPVStream', 'COLUMN'
Submit application changes made in Pega Express to a continuous integration and delivery pipeline
Valid from Pega Version 7.4
After you make changes to your application in Pega® Express, you can submit these changes into a continuous integration and delivery pipeline that is configured in Deployment Manager. By using Pega Express to submit your application changes into staging, preproduction, and production systems, you can quickly start builds without involvement from IT.
For more information, see Starting a continuous delivery build.
Verify ML Readiness error: Upgrades from Pega 7.1.0 through 7.1.8 do not replace nonversioned rules
Valid from Pega Version 7.2
Upgrading from any Pega 7 Platform version between Pega 7.1 and Pega 7.1.8 to Pega 7.2 does not automatically replace nonversioned rules. If you revalidated and saved a Pega 7.1.x rule after the timestamp on the Pega 7.2 version of the rule, upgrading to Pega 7.2 does not overwrite the saved rule. You might see either of the following behaviors:
- The upgrade fails with the following error message:
Verify ML Readiness
- The upgrade succeeds, but you might be unable to open changed rule forms.
If the upgrade fails, see the Pega 7 Platform Upgrade Guide to force the upgrade.
This known issue does not affect Pega 7.1.9. After the upgrade has finished, apply Hotfix 27288. For information about obtaining and applying hotfixes, see Hotfix Manager.
Support for large binary data item storage in Pega Client for Windows
Valid from Pega Version 8.2
Pega Client for Windows can now store and synchronize large binary data items and their corresponding actions from the action queue. As a result, offline-enabled application users can view, attach, and delete data files from within a case view, whether the Windows-based device is online or offline. To use this feature, enable offline case attachment support, which allows offline-enabled applications to synchronize case attachments between Pega Platform™ and the device.
For more information, see Attach content support in offline mode and Enabling offline case attachments support.
Data schema error on z/OS split schema upgrades from versions before Pega 7.1.8
Valid from Pega Version 4.1
When upgrading to a split schema on Pega 7.x with IBM DB2 for z/OS, you see an error during the data schema upgrade when the system tries to drop the PRPC_Updatescache procedure. Because triggers on rules tables use PRPC_Updatescache, you must use the ZOSDisableTriggerScripts to disable these triggers before you update the data schema.
- Follow the instructions in the Pega 7 Platform Upgrade Guide to upgrade the rules schema, but stop immediately before you upgrade the data schema with the upgrade.bat or upgrade.sh script. The Pega 7 Platform Upgrade Guide is on the page.
- Copy the contents of the <distribution>\ResourceKit\ZOSDisableTriggerScripts directory into the <distribution>\scripts\ directory.
- Run fixZosTriggers.bat or fixZosTriggers.sh with the following arguments:
--action preupgrade
--dataschema
<data schema name>--oldrulesschema
<old rules schema name. If you are upgrading from a single-schema system, this is the data schema name.>--newrulesschema
<new rules schema name>--automaticddl
<Optional. Set to true to automatically apply the disable trigger SQL scripts.>For example:
fixZosTriggers --action preupgrade --dataschema pegadata --oldrulesschema pegarules --newrulesschema newrules --automaticddl false
- If you did not set --automaticddl to true in the previous step, run the <distribution>\schema/disable.sql script to manually disable the trigger SQL scripts.
- Run the data schema upgrade as described in the Pega 7 Platform Upgrade Guide.
New Schema Tools and Query Inspector landing pages for Pega Cloud
Valid from Pega Version 7.2
Two landing pages have been added for advanced database administration tasks for Pega Cloud customers who use a Pega-hosted instance. These landing pages minimize the operations that need to be performed outside of the Pega 7 Platform. They are available only for customers who use a Postgres database.
From the new Schema Tools landing page, you can view PegaRULES and PegaDATA database schemas, increase the size of a column, add a composite or function index, update database statistics for a table, and defragment a table.
From the new Query Inspector landing page, you can enter an SQL query and generate an explain plan.
To use these landing pages, you must have the new PegaRULES:DatabaseAdministrator role. You access the landing pages by clicking
or by clicking . The individual features that you can access are determined by the privileges that are assigned to you.For more information, see Schema Tools and Query Inspector landing pages for tuning and maintaining databases in the Pega Cloud.
Specify a queue of user operations in Pega Digital Experience APIs
Valid from Pega Version 8.3
You can now specify a queue of page instructions for user operations on embedded pages, page lists, and page groups in Pega Digital Experience APIs. The page instructions allow your client application to more accurately model users’ actions.
Pega Digital Experience APIs support the following operations:
- For embedded pages:
DELETE
,REPLACE
, andUPDATE
. - For page lists:
DELETE
,REPLACE
,UPDATE
,APPEND
,INSERT
, andMOVE
. - For page groups:
DELETE
,REPLACE
,UPDATE
, andADD
.
For more information, see Page-related operation queuing with page instructions in Pega APIs.
App Studio enhancements further support Pega Express methodology
Valid from Pega Version 8.6
App Studio now includes improvements that you can use to plan your Microjourney™ in a more convenient way. The Overview workspace now includes a button to edit application details, such as name, description, and business objectives, without having to switch to Dev Studio. You can also access relevant information faster, because Case Designer displays additional details about channels, data objects, and attachments associated with a case type directly in a properties pane. For improved management of your features, feature categories are now available in the application inventory so that you can clearly communicate to your development team what type of features need implementation.
For more information, see:
- Editing application details in App Studio
- Associating personas with channels
- Adding features to application inventory
- Creating a Microjourney for customer success
Extended support for Cosmos React tables in Pega Infinity applications
Valid from Pega Version 8.6
Cosmos React tables are now available to Pega Infinity™ pages. Previously, when you enabled Cosmos React UI for landing pages in your application, you could add the React-based tables only to landing pages. With this enhancement, you can also embed tables in a section that is part of your case view or dashboard page.
For more information, see Adding a React table to a section.
End of support for form-based rule forms in Pega 7.1.9
Valid from Pega Version 7.1.9
Rule forms that are configured to render as forms are no longer supported in Designer Studio or end-user applications. Form-based configurations are found on custom rule types that were created in earlier versions of Pega 7 and are characterized by pop-up windows that are rendered externally from Designer Studio.
Reconfigure Pega 7 applications that use such rule forms by using standard harnesses and sections.
- Open the class form.
- Click the Advanced tab.
- Select
Harness
from the menu. - Create a new harness and new sections that implement the logic of the custom rule, using standard user interface layouts and controls.
Migrating custom rule forms to harnesses and sections offers the following benefits:
- User interfaces become HTML5 WC3 compatible and responsive to different screen sizes.
- User interfaces become cross-browser compatible, rendered consistently in Google Chrome, Mozilla Firefox, Apple Safari, and recent versions of Microsoft Internet Explorer.
- Rendering performance on modern browsers is dramatically improved.
- User interface pop-up behavior is eliminated; all windows are rendered inside Designer Studio and end-user applications.