SR-117815 · Issue 170081
Updated UUID generation to function with Ping Identity
Resolved in Pega Version 7.1.7
Issues were experienced in trying to achieve connectivity using SAML 2.0 for an SSO solution. Ping Identity imposes a constraint on the format of the Request ID that it receives, and fails if that ID does not start with a letter or underscore. This ID is a random UUID generated by java code, and it had no set leading character. In order to allow full interoperability, the UUID generation has been replaced with a custom implementation which generates unique IDs starting with "_".
SR-118305 · Issue 171562
Report definition reference columns expanded to include data type smallint
Resolved in Pega Version 7.1.7
Report definitions with reference columns of data type SmallInt in their database were not able to run as expected after migration due to missing support for that data type. This support has been added.
SR-118604 · Issue 175098
Externally mapped class hierarchy given precedence over default mapping
Resolved in Pega Version 7.1.7
If a series of properties in the same class hierarchy were explicitly mapped to columns in the external database table and shared the names of some of the database columns, the Obj-save failed. Sporadically when the system restarted, the properties that share the names of the database columns were mapped to those columns. The code has been updated to ensure that external mapping takes precedence over PRPC's default property-column mapping
SR-119148 · Issue 173101
MSSQL columns with spaces in the name will generate an error seeking correction before submission
Resolved in Pega Version 7.1.7
While Microsoft SQL Server (MSSQL) tables allow columns with spaces in their name, the PRPC engine does not allow such names at this time. In order to handle the incompatible name issues, the Integrator Wizard will detect that it is dealing with a table that has spaces in its column names, and fail up front with a targeted error message.
SR-109470 · Issue 166330
Listview joins corrected for multiple classes with the same name
Resolved in Pega Version 7.1.7
Running a listview with join which contains same name column in the "Get these fields" from Applies-to class and joined class was not working correctly; the property from the joined class was exposed whereas the one from Applies-To class was pulled from the blob column. To correct this, the SQL generation logic has been modified to maintain correct order (unexposed properties followed by exposed).
SR-117958 · Issue 166117
Alignment issues with IAC resolved
Resolved in Pega Version 7.1.7
When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.