Word merge support with Microsoft Silverlight plug-in
Valid from Pega Version 7.1.3
PRPC features that integrate with the Word merge capability are now cross-browser. ActiveX controls (which are only compatible with IE) have been replaced with Microsoft Silverlight. This plug-in must be downloaded separately from Microsoft, as it is not shipped with PRPC.
Some common PRPC features affected by this change include the Application Document Wizard, App Profile, Specifications Landing Page, Specification form, and Case Type Landing Page.
Prior to using these features, Users of PRPC 7.1.3 need to set up their client system(s) as follows:
1. Install Silverlight plug-in
Follow the PRPC prompt to install Silverlight when you attempt to use the Word merge feature:
Or download package directly: www.microsoft.com/silverlight/
2. Install PRPC prerequisites
Microsoft Internet Explorer (IE) browsers automatically detect the need for PRPC prerequisites and will prompt for install:
Non-IE browsers will load a pop-up window when the user attempts to use the Word merge feature. Use the link to manually download PRPC prerequisites:
Extract the .zip file, execute setup.exe and follow the install wizard:
Administrators setting up multiple clients at once may refer to the pzSLpreReqs.cab available in the PRPC 7.1.3 resource kit.
3. Restart browser
Log out of PRPC, close all open sessions and restart your browser.
The PRPC feature integrated with Word merge is now ready for use; Silverlight prompts are no longer displayed.
4. Troubleshooting
Silverlight installation requires access to your file system and a registry setting update to “trust” the associated Verisign certificate. Contact your administrator if you encounter any security or permission errors during this process.
See the PRPC Developer Help for more information on browser setup requirements.
Data Management
Valid from Pega Version 7.1.3
Improvements to data handling were made for the Data Pages, autopopulate properties, and reference properties. Lightweight lists were optimized.
- Property references are now maintained on the Work Page.
- PageList properties can reference a Data Page.
- Auto-populate properties can be used in a seciton to show results from a Data Page.
- Data Pages can run in “Page” mode as well as “List” mode
- The "Rules Not Using Lightweight List" report was enhanced.
- A PageList property that references a Data Page may be used to populate a grid.
- Related autopopulated properties can now be referenced.
Integration
Valid from Pega Version 7.1.3
Usability enhancements have been made to the integration wizards. The REST end-point integration has been improved, and XML parsing functionality has been enhanced.
- PRPC services can return Report or Listview data as XML.
- Work items may now be processed when accessing from a link in system-created emails.
- An SMTP outage will not cause an application to stop working.
- File listener will now read files using a leading asterisk (*).
- XML Parse rule will handle schema validation.
- PegaImageViewer will now work with Version 7.1.
- Security measures are enhanced for SOAP connections to web services.
- After generating rules using REST wizard, the Undo Generation button will delete all the generated rules.
- Email wizard has been improved.
Data Designer lets you explore, develop, and manage the data your application uses
Valid from Pega Version 7.1.7
The Data Designer, new in Pega 7.1.7, is the lens through which you create and manage your application data types, and create properties within the selected data type. The Create Properties wizard is retired, and you now create and manage properties in the Definition tab of the data type you are viewing. You can track how your application uses your data types, and which case types use which data, on the Usage tab. Review the sources for your data types on the Sources tab, and create and manage local data storage for records on the Records tab.
For more information, see About Data Types.
Explore the relationships between data types with the Data Visualizer
Valid from Pega Version 7.1.7
The Data Visualizer, new in Pega 7.1.7, provides a graphical display of the relationships among your application's data types and class types. The map view can help clarify how your application's data works together. When you hover the mouse pointer over an entity in the display, the Data Visualizer highlights the entities with which that entity has a direct relationship.
For more information, see About the Data Visualizer.
New Cassandra connector rules allow applications to use data in BigData stores
Valid from Pega Version 7.1.7
The new Connect Cassandra rule type provides the interface to leverage data in Cassandra data stores. This means that your applications can use large data sets stored in Cassandra data stores. For more information on this connector type, see About Connect Cassandra rules.
New Hbase connector rules allow applications to use data in BigData stores
Valid from Pega Version 7.1.7
The new Connect HBase rule type provides the interface to leverage data in HBase data stores. This means that your applications can use large data sets stored in HBase data stores. For more information on this new rule type, see About Connect HBase rules.
Your application can be a SAML service provider
Valid from Pega Version 7.1.7
You can quickly establish your application as a SAML service provider, with a web SSO profile, SOAP binding, and HTTP redirect binding to support single logout binding. The service is interoperable with Ping Identity, Tivoli Federated Identity Manager, and many other leading identity service providers (ISPs).
Cannot create new data tables after update
Valid from Pega Version 7.1.7
Data tables have been replaced by a new local data storage format. You can upgrade old-style data tables to use the new local data storage format, but the new format is not compatible with earlier versions of Pega 7 in which data tables could be created.
You can still edit legacy data tables by using the old data table functionality. However, to create new data tables, you must use the Data Explorer and Data Designer.
Service responses in HTTP and REST connectors are no longer modified
Valid from Pega Version 7.1.7
The Pega 7.1.8 release correctly leaves form service responses for HTTP and REST connectors unmodified. Upgrade to this release if you experience a problem in Pega 7.1.7 where service responses for HTTP and REST connectors are modified when the declared type in the Content-Type header is application/x-www-form-urlencoded
. In this case, the responses were modified to a base 64 representation of the bytes in the string. In Pega 7.1.8, responses of type application/x-www-form-urlencoded
are mapped to the property designated on the Connector record.