SR-129101 · Issue 195816
Smoothed error handling for operator password change process
Resolved in Pega Version 7.1.8
After the password change error screen appeared, the error popup showed again after dismissal and the the operator-id edit screen had to be closed and reopened, requiring entering the operator information again in order to proceed. This was due to incomplete clearing of the errors, and has been corrected.
SR-129101 · Issue 195933
Smoothed error handling for operator password change process
Resolved in Pega Version 7.1.8
After the password change error screen appeared, the error popup showed again after dismissal and the the operator-id edit screen had to be closed and reopened, requiring entering the operator information again in order to proceed. This was due to incomplete clearing of the errors, and has been corrected.
SR-129159 · Issue 196998
Replaced missing OperatorID page for LDAP tab thread
Resolved in Pega Version 7.1.8
The OperatorID page in the clipboard was not visible in the tab thread when logged in through LDAP though it was visible in other threads or when not using LDAP. This was an error, and has been corrected.
SR-129276 · Issue 194879
Replaced missing help search button
Resolved in Pega Version 7.1.8
When launching the Pega help contextually, the button to get to the search field in the Pega help was missing. This has been replaced.
SR-129687 · Issue 195885
Updated locale clock handling for Java 7 and PAL
Resolved in Pega Version 7.1.8
Java 7 changed how locales are handled, and the two different NumberFormat classes within PRPC were sometimes leading to errors including blocking access to PAL. In particular, the way PAL set wall clock time was not compatible, and the system has been updated to parse it correctly with the new format.
SR-129690 · Issue 197180
BIX extracts made consistent independent of run method
Resolved in Pega Version 7.1.8
The property format outputted by BIX was different when BIX was run via the command line versus running it from an extract rule in the application's user interface UI. This was traced to running from the UI the batch requestor as unauthenticated and properties created in application rulesets not having property information: the XML page did not have pxObjClass set, hence the property info was null and formatting was ignored. To resolve this, the current requestor will be used (which is properly authorized), and If it is null, then a new app requestor will be created.
SR-129714 · Issue 198126
Added ability to access operator with deleted division/org
Resolved in Pega Version 7.1.8
When an operator as associated with a division and that division was deleted, the existing operator record could not be opened in the developer portal due to a validation error (in this case, associated with a missing division). While there are validation checks associated with deleting organizational units and divisions that safeguard against deletion, it was still possible to delete a non-empty division directly. When this occurred, the operator ruleform could not be opened due to being in an invalid state. Handling for this has now been added, and an operator record can be opened in DS even if the corresponding org/org unit/div has been deleted.
SR-129725 · Issue 198663
Enhanced SLA reporting available
Resolved in Pega Version 7.1.8
In order to facilitate detailed reporting on bad SLA items, the following rules have been added: 1. Class to EMBED-QUEUEERRORDETAILS to contain error properties. 2. Page list type property .pxQueueErrorDetails in System-Queue- class. 3. Text type property pxErrorMessage in EMBED-QUEUEERRORDETAILS class. 4. Datetime type property PXERRORDATETIME in EMBED-QUEUEERRORDETAILS class.
SR-129768 · Issue 200019
Resolved error saving to lower version unlocked ruleset
Resolved in Pega Version 7.1.8
An error was encountered when attempting to save a rule in an unlocked lower version if a higher level locked version existed. This has been corrected by removing a redundant post condition in the activity Rule-RuleSet -> pzGetOpenRulesetVersions.
SR-129892 · Issue 196786
Error handling improved for BIX extraction called by an agent
Resolved in Pega Version 7.1.8
Running BIX extract from an agent (which calls activity runExtract) caused the BIX logfile to grow to enormous size due to an infinite loop after encountering a JDBC 'connection reset' error. Handling for this error has now been added to ensure smooth extraction from an agent.