Internet Application Composer (IAC) renamed to Pega Web Mashup
Valid from Pega Version 7.1.9
The name of Internet Application Composer (IAC) has changed to Pega Web Mashup.
For more information, see Pega web mashups for embedding Pega Platform UI in external web pages.
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.
FTP server records enhanced for SSH FTP
Valid from Pega Version 7.1.9
When using SSH FTP (SFTP) in an FTP Server record, you can securely transfer files by using SSH keys. You can enable and configure SFTP by opening the FTP server record and completing the fields in the Protocol section.
For more information, see SSH FTP for FTP server records.
Accessibility support using WAI-ARIA roles
Valid from Pega Version 7.1.9
The Pega 7 Platform supports accessibility by using Web Accessibility Initiative Accessible Rich Internet Application (WAI-ARIA) roles. WAI-ARIA roles are a World Wide Web Consortium (W3C) ontology that specifies roles, states, or properties for each user interface element. Roles provide semantic information about features, structures, and behaviors that assistive technologies use to convey information to users.
- The dynamic container is marked as the main content area by default. When a user tabs through a page, the user can choose to follow a skip to the main content link by pressing the Enter key.
- WAI-ARIA roles are included by default on screen layouts, and each panel of the screen layout is assigned a role that is based on its position.
- Dynamic layouts can be configured with a specific WAI-ARIA role, depending on the function of the layout in the user interface.
New Business impact optimization dashboard
Valid from Pega Version 7.1.9
On the Analysis tab of the Application Profile landing page, you can now enable historical specification count and implementation progress by complexity and business impact. On the Business impact optimization dashboard, you can view counts of specifications by complexity and business impact. You can also view counts, by business objective, of specifications that have been implemented and for those not yet implemented. You can filter specifications by release and iteration.
For more information, see Viewing specifications by complexity, impact, and business objective, and Associating project specifications with business impact and complexity.
Database storage used for passivation in High Availability mode
Valid from Pega Version 7.1.9
When an application is running in High Availability mode, the value attribute for initialization/persistrequestor/storage in the prconfig.xml file or the Dynamic System Settings now defaults to "database."
Previously, applications running in High Availability mode required shared passivation, where either initialization/persistrequestor/storage was set to “OnTimeout” or a custom passivation mechanism was used. The change to using database by default provides persistent storage for passivation, and provides control for the landing page for High Availability.
For more information, see Understanding passivation and requestor timeouts and the High Availability Administration Guide.