SR-125548 · Issue 195950
Corrected masking of screen by busy indicator
Resolved in Pega Version 7.1.8
Only a portion of the screen was being masked by the busy indicator, allowing modifications to be made on the other visible portions of the screen. This has been corrected.
SR-121828 · Issue 179859
Localization added for the "Loading" text of the busy indicator
Resolved in Pega Version 7.1.8
Previously, the 'alt' values of the "Loading" text for the pega_ui_busyIndicator (pxThrobber) were hard-coded to English. This has been changed to allow localization.
SR-122387 · Issue 183319
Expanded BIX error codes
Resolved in Pega Version 7.1.8
When BIX is executed through the command line, it may not return an error code even if BIX has stopped processing because of a failure (for instance when the -f flag has been used). That is, the $? system call may return 0 when an extract has failed. The system has been updated to offer more information thorough error code returns, but when trying to programmatically capture whether a particular run of BIX was successful or not, it would still be advisable to check $? in the script, as this may be returned due to other reasons (such as a java/network/database related problem). This may be augmented by performing a parse on the PEGABIX log file and specifically checking for the text: 'Instances not extracted due to errors: 0'. At the end of each BIX this line will appear with a summary of how many extracts failed. After the BIX portion of the script has completed, it's possible to check how many occurrences of this error appear in the file. If it is one, then this meant none of the extracts produced errors. And if there are none, then either some exports did contain errors, or it didn't reach the part of the code that produces this line (hence an earlier error). This can be incorporated into a script using something like: errorfree='grep "Instances not extracted due to errors: 0" PEGABIX.log | wc -l'
SR-120654 · Issue 179938
Made busy indicator location consistent in SFA portal
Resolved in Pega Version 7.1.8
The 'loading' icon (aka "Throbber") was not being displayed in a consistent location in the SFA Portal. This was traced to the busy indicator being registered in reference to the workarea gadget, causing the busy indicator to appear in an unexpected place if the gadget was hidden. This has been corrected by showing the indicator directly on the portal window.
SR-126092 · Issue 189635
Enhanced logging for SQL exceptions with BIX
Resolved in Pega Version 7.1.8
In order to enhance diagnostics while using BIX, logging has been added to print the stack trace for an SQL Exception while fetching the last updatedatetime.
INC-178923 · Issue 660887
Resolved startup error related to business calendar object
Resolved in Pega Version 8.5.5
An error recorded in the log file when the server started was traced to a cache update that removed the old business calendar object and added the new business calendar object to the business cal list. This has been resolved by updating the system to replace the business calendar object instead of removing the old one from the cache first.
SR-126746 · Issue 189633
Added schema qualification to BIX / DB2 extract rules
Resolved in Pega Version 7.1.8
When using a Business Intelligence Exchange (BIX) extract rule which included writing the manifest details to external database tables, running the extract rule generated errors for the insert into the pr_extract_summary and pr_extract_details tables. This issue existed both when running from the command line and from the User Interface (UI). This was traced to the extract code not schema qualifying the pr_extract_summary and pr_extract_details tables in the insert statements, so it is expecting those tables to be in the schema of the user who is defined in the Database rule. This has been corrected through code changes for DB2 external databases that includes currentSchema=YourSchemaName in the URL connection to the external database.
SR-126746 · Issue 185231
Added schema qualification to BIX / DB2 extract rules
Resolved in Pega Version 7.1.8
When using a Business Intelligence Exchange (BIX) extract rule which included writing the manifest details to external database tables, running the extract rule generated errors for the insert into the pr_extract_summary and pr_extract_details tables. This issue existed both when running from the command line and from the User Interface (UI). This was traced to the extract code not schema qualifying the pr_extract_summary and pr_extract_details tables in the insert statements, so it is expecting those tables to be in the schema of the user who is defined in the Database rule. This has been corrected through code changes for DB2 external databases that includes currentSchema=YourSchemaName in the URL connection to the external database.
SR-128063 · Issue 193580
Added schema qualification to BIX / DB2 extract rules
Resolved in Pega Version 7.1.8
When using a Business Intelligence Exchange (BIX) extract rule which included writing the manifest details to external database tables, running the extract rule generated errors for the insert into the pr_extract_summary and pr_extract_details tables. This issue existed both when running from the command line and from the User Interface (UI). This was traced to the extract code not schema qualifying the pr_extract_summary and pr_extract_details tables in the insert statements, so it is expecting those tables to be in the schema of the user who is defined in the Database rule. This has been corrected through code changes for DB2 external databases that includes currentSchema=YourSchemaName in the URL connection to the external database.
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.