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.
SR-132143 · Issue 201187
Enhancement added to allow setting extract directory for BIX
Resolved in Pega Version 7.1.8
An option has been added to override the output directory of the command line BIX extraction. The command line parameter -P allows specifying the desired path by saving a copy of the Extract Rule XML and setting appropriate pyOutputDirectory path value in it.
INC-211977 · Issue 713461
Handling added for large BIX Postgres data sets
Resolved in Pega Version 8.6.5
BIX extracts were causing timeouts or JVM out of memory errors. This was traced to the Postgres JDBC driver ignoring fetch size in auto-commit transaction mode, which led to everything being loaded into memory at once. To resolve this, changes have been added to support fetch size for large results when using PostgreSQL database for BIX Extraction.
SR-128676 · Issue 194416
Existing BIX pr_extract_time tables preserved during install
Resolved in Pega Version 7.1.8
In older versions of the software, the pr_extract_time table was created by the core PRPC installation. This table creation was recently moved to the installation of BIX, but the system was improperly dropping this table from the data schema if it already existed during installation. This has been corrected.
INC-217974 · Issue 715429
Handling added BIX extraction failure when called from custom activity
Resolved in Pega Version 8.6.5
After update, BIX extraction was failing but email from the schedulers indicated success. Investigation showed that when extract was called from a custom activity by calling pxExtractDataWithArgs, the stepStatusFail 'when' rule in the custom activity was not capturing all the exceptions specific to database extracts. This has been resolved by adding the necessary handling.
SR-130345 · Issue 199748
Added qualification to validation queue page creation
Resolved in Pega Version 7.1.8
After migration, executing custom business logic validation generated the error "There was a problem getting a list". This was due to the JS code generating an unqualified QueuePage, and has been resolved.
SR-123533 · Issue 187272
Corrected calculation of WO SLA Goal,Deadline based on calendar input
Resolved in Pega Version 7.1.8
The calculation of Goal,Deadline for WO SLA was not showing the expected results based on business days in the calendar. This was caused by not passing the appropriate parameter (CalendarName) to Work-.DefineSLATimesFromNewProperties so that BusinessCalendar.addTime function could evaluate the SLA based on the calendars, and has been fixed.
INC-185847 · Issue 668984
Handling added for disabling weekends when no weekends are available
Resolved in Pega Version 8.5.5
A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.
INC-178990 · Issue 663786
Added handling for reloading portal while ChatBot is active
Resolved in Pega Version 8.5.5
An issue was seen with UI rendering when a customer tried to reload the portal where the chatbot is deployed. Investigation showed that this was caused by the screen going to pyCreate harness instead of ChatPerform harness due tot he unexpected refresh, and has been resolved by updating the handling for the Chat Work page and the business case so that pyWorkPage is always Work-Channel-Chat.
SR-124451 · Issue 185472
Event based subscription processes corrected
Resolved in Pega Version 7.1.8
After migration, "Event" based subscription processes were not firing. In this case, when distributed search was enabled (via following DSS - Pega-SearchEngine . indexing/distributed/index_enabled) and if "Work indexing" was enabled, Business events stopped working. This was due to an incorrect check on the enqueueLightWeight() function and has been corrected to use a blob based table if events fire.