Support for custom pre- and post-JavaScript processing for offline flow actions
Valid from Pega Version 7.1.9
Developers of an offline-enabled mobile app can execute basic business logic before and after a flow action is rendered by adding their own JavaScript code into a custom user scripts bundle. Its functions must be called within a try
/catch
clause. The JavaScript code, to be executed before a flow action is rendered, is always called afterClientCache is called and before DisplayHarness is called.
Conditional online and offline map display
Valid from Pega Version 7.1.9
The way an Address Map control behaves in a offline-enabled mobile app has changed. When a mobile app is online, a live Google map is loaded as expected. If the mobile app goes offline, a predefined image of a map is loaded instead.
Troubleshooting Pega Mobile Client on the login screen
Valid from Pega Version 7.1.9
An offline mobile developer can now troubleshoot issues that are not related to incorrect credentials when signing in to the Pega Mobile Client app. On the app login screen, an alert box displays where the user can click a link to examine current log files to troubleshoot the issue. The contents of the displayed log file can be filtered.
For more information, see Troubleshooting Pega Mobile Client.
New Pega Mobile Client debugging options
Valid from Pega Version 7.1.9
The Mobile tab on the Application form contains two new options: a check box for enabling debugging in the Pega Mobile Client app, and a drop-down field for setting the log level to one of the following levels: Silent, Error, Warning, Info, or Debug.
For more information, see Mobile settings reference.
Ability to view a PDF file while offline
Valid from Pega Version 7.1.9
Users of offline-enabled mobile apps can now tap a button to view a PDF file, regardless of whether the user is online or offline. The associated button, link, or icon must have a Run Script action defined that calls the pega.ui.pdf.view()
function with two parameters: applicationName
and pdfName
. The PDF file itself must be uploaded to a Rule-File-Binary rule.
For more information, see How to set up viewing of PDF file while offline.
Building a Pega Mobile Client with custom modules
Valid from Pega Version 7.1.9
When you build a Pega Mobile Client mobile app using the Pega 7 Platform, you can now include Android or iOS custom modules. The custom modules must be included in the assets.zip
file that contains the Pega Mobile Client branding and customization details.
For more information, see Building a mobile web app into a hybrid mobile app.
Addition of Data Access Tab to access control policy condition rules
Valid from Pega Version 8.6
You can now select associations and declarative index classes when creating access control policy condition rules. The C field in the policy condition can now accept properties from available associations and indexes. For ease of reference, the selected associations and indexes are available on the new tab.
Using the new tab, you can build complex authorization models in which access restrictions for a class depend on the attributes present in the associated and indexed classes, along with the attributes in the current class. For example, a project management application can now separately maintain project lists for each operator and use that information to restrict read/write access to unique projects.
The information available on the new Data Access tab reflects rule form changes, which are similar to the existing functionality of the Report Definition in the Application Data Model.
For more information, see Creating an access control policy condition.
Addition of Servlet Management
Valid from Pega Version 8.6
Pega Platform™ now has Servlet Management in Pega Cloud® Services, which provides a simple and secure way to make changes to Pega Platform servlet definitions.
Servlet Management provides Pega Cloud Service clients with solutions to manage servlet configurations with self-service options. This reduces the cycle time for delivering configuration changes in Pega Cloud Service installations while also improving upgrade reliability.
For more information, see Servlet management.
Upgrade impact
Clients with no application servlet customizations will not experience an impact. If you upgrade from Pega Platform version 8.5 or earlier and, prior to the upgrade, the Pega Cloud team provided your application servlet customizations, then following the upgrade, you must manually add, remove, or modify your servlet customizations in your upgraded application using this servlet management landing page in Pega Platform.
What steps are required to update the application to be compatible with this change?
To manually move your pre-upgrade servlet customizations as appropriate or add new ones to your upgraded application using the new servlet management landing page, follow the steps in Adding a servlet.
Cosmos React-UI supports custom authentication
Valid from Pega Version 8.6
Pega Platform™ now supports custom authentication in applications that use Cosmos React-UI. Depending on the needs of your users and the functionality of your application, you might need to write custom authentication schemes to meet specific requirements.
Clients that use custom authentication in their applications can now take advantage of the Cosmos React-UI.
For more information, see Securing Cosmos React-UI applications.
Integration and security tab now divided into two tabs
Valid from Pega Version 8.6
The Integration and Security tab is now two separate tabs on the form: Integration and Security. While the content of these two tabs are related, they function more effectively as separate tabs. The Security tab now includes the Authentication section, so you can add existing authentication services to your Application Definition to more effectively manage the security of your application.
For more information, see Security tab of the Application Definition.