Published Release Notes

Upgrading to Pega 7.1.7 with an Oracle database requires new role permissions

When upgrading or updating from a prior version to Pega 7.1.7, if your system uses an Oracle database, an additional role is required to support the Reversability functionality. In addition to the Oracle privileges specified in the Install Guides, the role SELECT_CATALOG_ROLE is required. Verify that this role is present before beginning the upgrade or update.

IBM WebSphere Application Server V8: Edit the URL for Enabling System Management Application

WebSphere 8 does not correctly resolve the URL to enable System Management Application. As a workaround, when you configure the application server, you can do either of these actions:

• Enter the full URL in the format:
  ​http://hostname:port/prsysmgmt/getnodes.action

• Set the com.ibm.ws.webcontainer.redirectcontextroot property to true.

Add additional columns to customized work history tables

The standard work history table, pc_history_work, contains two new columns that return the latitude and longitude coordinate location of the action that prompted the history. Mobile devices can display this location as a street address. If you have a customized work history table, add these two columns to it:

• <decimal name="pxLatitude" size="19" scale="9"/>
• <decimal name="pxLongitude" size="19" scale="9"/>

Flow import functionality is limited to Microsoft Internet Explorer Version 9 and Version 10 in Pegasystems Public Format

Importing a flow in the Rule-from-File wizard is limited to Microsoft Internet Explorer 9 and Internet Explorer 10 in the Pegasystems Public Format .

Improved cross-browser support

All rule forms are now harness-based and open in the work area of Designer Studio. This means that you can develop in the browser of your choice, free from pop-up distractions and incompatibility messages. Many rule forms have been upgraded to use the latest layouts, styles, and design best practices, giving you a consistent development experience.

Viewing a Word Template in Pega 7.1.7 compared with Pega 7.1.6

Previous restrictions still apply to any deprecated or custom rule forms in your application that remain form-based. Refer to the Deprecated features list for guidance on how to upgrade these forms and recommended alternatives.

Changes to archive.info in Pega 7.1.7

In Pega 7.1.7, the contents of the archive.info file have changed.

• In versions Pega 7.1.6 and earlier, the archive.info file displays the build number of the Pega installation.
• As of Pega 7.1.7, the build number no longer appears in the archive.info file.

In Pega 7.1.7, the archive.info file only displays a status message indicating whether or not the system is running, and the build number no longer appears. Instead, if the system is operational, the message “status=Running” displays in the archive.info file.

If there are any automated tests, scripts, or applications that rely on the archive.info file displaying the build number, those may fail and produce an error. It is recommended that any automation that relies on the build number displaying in the archive.info file be changed to look for the “status=Running” message.

Quickly see what's new in Pega 7.1.7

A new home page panel gives you centralized access to Help and the PDN, eliminating the need to leave Designer Studio. Use the buttons in this panel to learn about new features quickly and stay connected to product announcements.

What’s new panel as it appears on the Designer Studio home page

After you are finished reviewing new features and enhancements, you can dismiss the What’s new panel. This hides the panel from your operator in future sessions without impacting the home page for other application users.

Resolved Issues for 7.1.7

Fusion now shows tooltips for stacked data points of the same value

SR-82384             ISSUE:  93497

Previously, FusionCharts did not support the feature of showing all the series names and values in tooltip if all the series have same value for a single category. While there was a workaround of providing the all series names with values as text in the "toolText" attribute of the <set> element of the XML Data or by using stacked bar charts, FusionCharts now displays the tooltip for a single category series with the same value. _______________________________________________________________________________________________________

AddChildWork updated to allow child case creation from step flows

SR-94370             ISSUE:  119519

When attempting to create nested sub cases for rows in a page list with a Split for Each sub flow by calling the pyCreateSubCases flow, an error was generated. There was a workaround of using a utility shape to call pxAddChildWork instead of a split for each calling pyCreateSubCases, but pxAddChildWork has been updated in order to allow creating child cases using the step page as the primary page and not always defaulting to pyWorkPage. _______________________________________________________________________________________________________

Rule-Service-Java authentication in a stateless session re-enabled

SR-103429           ISSUE:  136984

When exposing Rule-Service-Java through a service package, a proxy jar file is created. If the 'Requires Authentication' option was checked on the service package, the generated java did not contain the required code to pass through the username/password and authentication failed. This method of passing credentials via proxy method parameters was previously withdrawn for the stateless processing mode, but the java code has been reinstated to enable authentication for a stateless session if this method is desired. _______________________________________________________________________________________________________

Added support for skipping explicit validation in tabbed screen flow

SR-106939           ISSUE:  176612

When using a tabbed screen flow harness in the application and uploading a file using the "FilePath" control, there is a check in the post activity of the flow action of the first screen to see if the user has browsed a file. When the user proceeds to the next screen by clicking 'next', the file is validated and attached to the work object. However, if instead of clicking the Next button the user clicked on the tab to go to the next screen, the validation failed and the file was not attached. This problem was traced to the 'GoToPreviousTask' activity failing to pass the parameter page in this scenario, and has been fixed by adding a new step to update the existing parameter page with necessary parameters to allow validation and attachment when skipping the 'next' button. _______________________________________________________________________________________________________

Execution plan reuse on SQL Server 2008 R2

SR-108009           ISSUE:  154664

Due to the way a SQL server treats execution plans, each decimal bind value with a different scale is treated as a different type. To optimize the execution, the scale value for the execution plans will now be set the same as the table definition for obj- methods. _______________________________________________________________________________________________________

Corrected purging for History and Attachments

SR-108346           ISSUE:  166436

A problem was found with purging the History and Attachments for cover and folder items. This was traced to history tables using datetime columns as key properties: many databases round these values to less precision than PRPC uses, and the keys did not match. The purgeitems function has been updated to delete the instance specifically and bypass recalculating the InsKey. _______________________________________________________________________________________________________

Help updated to explain When Rule "ALL" Evaluation behavior

SR-108805           ISSUE:  149539

A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries. _______________________________________________________________________________________________________

Increased limit for Rule_Obj_CaseType

SR-108838           ISSUE:  154989

Previously, Rule_Obj_CaseType was encountering a byte limit of 65535 in the JVM that impeded the ability to create a desired large number of coverable work types (54+). The system code has been modified to store the rule types differently to avoid generating extra lines of java code for each coverable case type. _______________________________________________________________________________________________________

CSS generation fixed for attaching files after validation failure

SR-109455           ISSUE:  172370

After a validation had failed, uploading a file (through the filePath Control) and submitting the flow action resulted in the page loading with no CSS applied. This has been corrected by changing how the uploading wrapper is applied in cases of validation failure. _______________________________________________________________________________________________________

Listview joins corrected for multiple classes with the same name

SR-109470           ISSUE:  166330

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). _______________________________________________________________________________________________________

WorkPage now properly deleted after rule checkin

SR-110773           ISSUE:  160105

There was an issue with rule check-in where it created the WorkPage with the obj-class Work-ProjectManagement-CheckIn, but it did not delete WorkPage when the check-in was complete. To address this, protective code has been added that checks the class of WorkPage for the existence of expected properties in order to properly handle the related clipboard pages. _______________________________________________________________________________________________________

Improved consistency with multiple class inheritance rules

SR-111606           ISSUE:  163137

A gap in the handing of multiple class inheritance was causing an issue with the consistency in picking the correct rule from a cache. If the entry was placed in a class where the applies-to class of the rule could not see it, that entry was missed from invalidation later on during the save. This could be temporarily remedied by clearing the cache, but the rule handling has been updated to consistently choose the correct rule from the cache under multiple inheritance. _______________________________________________________________________________________________________

Some SOAP calls with WSTRUST generated exceptions in customized environments

SR-111889           ISSUE:  157259

In some heavily customized environments, a SOAP connect call using the WSTRUST <wst:tokentype> element generated an exception. This was due to uneven handling of the local custom elements in the SOAP STS request, and has been resolved by adding a method to pick up all custom code based on the tag in policy document. _______________________________________________________________________________________________________

Closing Lucene search popup in Firefox corrected

SR-111945           ISSUE:  157966

When using Firefox, it was not possible to close the popup box generated by a Lucene search unless a work object was selected first. This was caused by an error the the method used to access the document id, and has been corrected. _______________________________________________________________________________________________________

Missing buttons from modal dialogues after manual resize

SR-112147           ISSUE:  162872

After a launching a modal dialog from a local action and manually resizing it to make it smaller, selecting another layout from the dropdown menu was causing the re-size icon and OK/Cancel buttons to disappear. To eliminate this problem, the system has been modified to properly reset the height and width of the modal container before displaying the second layout was displayed. _______________________________________________________________________________________________________

Corrected 'Top Performers' report

SR-112203 / SR-114573   ISSUE:  156906 / 162421

The "Top Performers" report in the Case Manager portal was returning incorrect values in the 'Avg. Velocity' column due to an incorrect calculation based on the number of days in the selected period. This has been corrected. _______________________________________________________________________________________________________

Dynamic Select while editing Data Table instances

SR-112357           ISSUE:  163326

When using DynamicSelect in a few properties under DataTable instances, editing or adding new rows in the DataTable failed to show a list of values from ReportDefinition and generated the error "Select element SwitchboardCategory is missing DSCaption". This was traced to HTMLPropertyParams not being properly passed on to DynamicSelect control, and has been fixed. _______________________________________________________________________________________________________

Portal rendering errors under z/OS

SR-112535           ISSUE:  164337

Under z/OS, new installations were missing the login icon and the portal was not rendered correctly. This did not impact system performance. The problem was traced to an index setting in the DDL generation, and has been fixed. _______________________________________________________________________________________________________

Updated Datetime extraction with BIX to ensure consistent time zone output

SR-112684           ISSUE:  166387

When extracting Datetime values from BIX, the time zone returned in that datetime value was inconsistent. This was caused by variations in the save points of the extractions that resolved property types, and the function has been modified to use a consistent save point. _______________________________________________________________________________________________________

Repeating grids enhanced to allow the '&' character as text

SR-112935           ISSUE:  166182

When values in a repeating grid contained the character ‘&’, the ReloadSection activity failed with an illegal argument tracer and no values were passed to a second Repeating Grid Page List. This was traced to '&' being used by the system to perform a split of value string. In order to allow use of the '&' character in the list values field, it will now be encoded so it is passed without evaluation. _______________________________________________________________________________________________________

Ensured tabbed section refresh for new sessions

SR-113149           ISSUE:  168421

When a new session had only 2 tab groups configured with dynamic container, the first tabbed section refresh was not working as expected. This was caused by a missing null check, and has been corrected. _______________________________________________________________________________________________________

Localized ENTER key behavior for IMEs

SR-113173           ISSUE:  163073

Previously, hitting the ENTER key during field entry created a new row and moved the cursor to it. However, this was not optimal in environments using IME where the ENTER key is typically used to confirm the input of a character for words (such as using Japanese characters). In order to facilitate input while using IMEs, the system now distinguishes whether or not IME is enabled and changes the result of hitting ENTER while entering text fields to confirm alphabet -> character conversion if IME is in use. If IME is NOT enabled (the user intends to input alphanumeric characters), the default behavior remains as creating a new row and moving the cursor to it. IMPORTANT NOTE: this IME feature is not available using Internet Explorer 8, as Internet Explorer 8 does not support the necessary composition events required for this handling, and hitting ENTER will create a new row as before. _______________________________________________________________________________________________________

Resolved review harness showing a collapsed work object

SR-113288           ISSUE:  176797

If a review harness was configured with a pxTextArea and TextArea control along with other embedded sections, opening a work object in review mode showed the content of work object as collapsed or shrunk. Clicking the tab representing the work object to refresh displayed the whole content. This was traced to the TextArea control throwing a JavaScript error which was stopping the resize execution. A null check has been added to prevent this. _______________________________________________________________________________________________________

Explicit schema mapping could cause migration script errors

SR-113384           ISSUE:  162788

While running the migration script, the presence of a custom rule table that explicitly mapped the Data-Admin-DB-Table schema could cause the script to fail. This was caused by the GRANT statements in the SQL script not having the proper assignment for the user name with the "USER" keyword; a group name that is the same as the user name that we are trying to GRANT rights to was ambiguous. The workaround was to temporarily map the custom table to an empty schema, then manually copy this table to the RULES schema afterward, but this issue has been addressed by updating how privileges are granted for the table, procedure and function elements in a split schema. _______________________________________________________________________________________________________

Smoothed background Bulk Processing processing

SR-113396           ISSUE:  162534

If the setting for BPUnitsToProcessForeground is given as 0 in all cases, attempting to run Bulk Processing in the background failed and logged an “Index out of bound” exception in the system logs. To cover this condition, a check has been added to handle zero items in the foreground processing when running background Bulk Processing. _______________________________________________________________________________________________________

Modal dialog box closing correctly from repeating rows

SR-113411           ISSUE:  172581

When adding and removing data from a repeating row, the Popup Modal dialog was not closing when the corner (X) button was clicked. This occurred if there was an active grid in the document and flowaction buttons were hidden: the closemodalflowaction api, which is responsible for closing the flowaction modal on click of close icon, assumed the modal was launched from the grid and incorrectly called the grid's cancelModal. This has been corrected. _______________________________________________________________________________________________________

Corrected use of Navigation URLs in Detailed view

SR-113431           ISSUE:  161621

The detailed view drilldown from a summary view was not passing the correct set of filters down to the server when the breadcrumb trail link was clicked, causing any included Navigation URLs to fail. There was a workaround of using list view in place of detailed view, but the HTML has been updated to pass the proper parameters to the activity and show the correct information. _______________________________________________________________________________________________________

Localization added for previously hard-coded popup

SR-113506           ISSUE:  163412

The popup message generated by opening a resolved assignment was previously hard-coded to appear only in English. The message will now reflect the proper localization. _______________________________________________________________________________________________________

Dynamic Select correctly expands drop downs with Internet Explorer

SR-113557           ISSUE:  167227

While using the WorkBasketGadget with dynamic select, drop downs were not expanding to the full width of the field value and parts of the values were hidden. This was caused by an Internet Explorer bug. The WorkBasketGadget rule has been modified to overcome the issue. _______________________________________________________________________________________________________

Fixed ability to use 'disable work processing' in the dashboard

SR-113597           ISSUE:  163512

Setting 'disable work processing' to true caused an NPE when opening a modal window via a Local action from dashboard (assign page class). This was caused by the process attempting to assign properties from a null page, and has been corrected. _______________________________________________________________________________________________________

Enabling OOTB Security Policies now redirects immediately

SR-113624           ISSUE:  167070

When enabling OOTB Security Policies, it was not immediately redirecting to the change password screen but instead requiring the timeout interval to expire before redirect happened. This has been corrected. _______________________________________________________________________________________________________

Custom root certificate support added to Connect-REST

SR-113703 / SR-115779  ISSUE:  163067 / 167907

Configuring a Connect-HTTP/REST rule that connects to a server using custom root certificates caused the error "javax.net.ssl.SSLPeerUnverifiedException". To remedy this, REST / HTTP now supports the merging of custom and jvm trust stores and runtime support for SSL in REST connectors. _______________________________________________________________________________________________________

Added tenantID checking for multi-tenant import of access groups

SR-113714           ISSUE:  173122

When attempting to overwrite an existing access group by importing the Client Access groups in the tenant layer, an error was generated and the access groups were not overwritten. This occurred when the SQLs were not Tenant-qualifying for operator records but were being imported into a tenant; as a result, operator record updates were marked as inserts. To correct this, the behavior has been updated to query for current tenantId and always tenant-qualify the query if it's an overridable instance and not in a shared context. _______________________________________________________________________________________________________

Page names for specialty components correctly generated as JSON

SR-113720           ISSUE:  167454

When using a specialty component that accepts input parameters of type page list, the necessary page list parameter names were not being passed as a JSON object due to the system's inability to reference each of them. To correct this, logic has been added to create page name in cases of page list. _______________________________________________________________________________________________________

Problems exporting Requirements/Specifications to Excel using JBOSS 6.1

SR-113726           ISSUE:  162821

When using the JBOSS 6.1 EAP Application server, exporting Requirements/Specifications to Excel using the 'Export to Excel' action generated the message "Error in parsing Excel file". This was caused by a change in the JBOSS class loading mechanism that resulted in a class cast exception due to multiple class loaders loading the same class from different sources. The handling of .jar files has been tuned to ensure proper class loading.
_______________________________________________________________________________________________________

Smoothed handling of rulesets with duplicate names

SR-113830           ISSUE:  164768

When doing a "Save As" of a rule, the ruleform converts the entry in the description field to uppercase. If there is already a previous version of the rule with a name in lowercase, it was possible for the rule to exist with both a lowercase and uppercase name. While Rule Resolution worked, this case difference could cause a scenario where not all versions of the rule were visible when doing a rule search, viewing rule history, or looking up previous versions of the rule. The rule retrieval logic previously used RuleName; to ensure proper rules are being picked up, this has been changed to use the rule ID. _______________________________________________________________________________________________________

Made page displays consistent between Java versions

SR-113919           ISSUE:  170809

pxFlow pagegroup values in pyWorkPage were being placed differently depending on the version of Java used in the environment. This was caused by a handling error in situations where there is no classname, and has been fixed. _______________________________________________________________________________________________________

Corrected Connect-Java ability to run in parallel

SR-114109           ISSUE:  164313

Using connect-java in RunInParallel mode was failing with the error "couldn't resolve the required java object". This was found to be an error in copying objects from the primary page in RunInParallel mode that did not properly retain the references for the Java wrapper objects. There was a workaround to use the "If possible, use a valid object handle" option, but this error has been fixed. _______________________________________________________________________________________________________

Enhanced keyboarding accessibility

SR-114154           ISSUES:  162063 / 169785 / 170194

Several enhancements were made to improve accessibility. While developing an application for visually impaired users who use the keyboard (rather than mouse) to navigate the screen, it was found that certain input elements did not correctly receive focus under Internet Explorer 8 when tabbing. One issue was that when an element is focused and the parent element is scrollable, the focused element was not being displayed if it was beyond the scroll area. Additionally, some elements were not receiving visual focus with WAI ruleset enabled upon focus. To aid in keyboard navigation, if the WAI ruleset is used, an element receiving focus will also be made visible by scrolling to its position. When the accessibility ruleset is enabled, all elements will now properly receive visual focus. In order to enhance the accessibility of dropdowns in Audit windows, Filter panel width has been increased in Accessibility Mode to display all the dropdowns in the window at once without requiring use of the scroll bar. Furthermore, Accessibility mode for Audit windows has been updated to include the use of the spacebar to toggle settings in the checkboxes. _______________________________________________________________________________________________________

Withdrawn non-empty classes caused JVM restart issues

SR-114184 / SR-114543   ISSUE:  162116 / 163265

After withdrawing non-empty classes, attempting to restart the JVM system resulted in a null pointer exception due to the system trying to map the withdrawn classes. The system has now been updated to prevent the deletion of a class if it is not empty. _______________________________________________________________________________________________________

Check added to handle invalid input in the year field for datetime

SR-114312           ISSUE:  174692

Previously, when a date time property was provided with an invalid year containing more than four characters (such as 20142014), the date defaulted to 12/20/8963 when the form was submitted. A check has been added to catch dates of more than four digits when attempting validation. _______________________________________________________________________________________________________

System scanner performance enhanced

SR-114353           ISSUE:  166997

When working with a large number of hotfixes, the system scanner can become very slow. Performance enhancements have been incorporated to increase speed by changing how ID and key comparisons are performed. _______________________________________________________________________________________________________

Inbound mail processing for work creation refactored for subject line checking

SR-114438           ISSUE:  168461

Some issues were found with the handling of inbound emails for work object creation. The activity CreateAndManageWorkFromEmail was incorrectly checking for an email subject line pre-condition and creating a new work object if the condition was not met. The CreateAndManageWorkFromEmail function has been refactored to correct this. _______________________________________________________________________________________________________

Corrected locking for custom Access Roles

SR-114479/SR-118589     ISSUE:  165273/171900

After adding a custom Access Role to an Object in the WO class with an Access When rule defined to allow opening a instance, Obj-Open-By-Handle failed to lock the work item correctly and two operators could have it open simultaneously. This was caused by the custom stack inheriting parent state for all members, and has been changed. _______________________________________________________________________________________________________

Increased limits for Bulk Processing

SR-114545           ISSUE:  164887

When attempting to filter cases for Bulk Processing, the Property-List LookupList activity only requested a maximum of 2500 records. This caused an issue with class inheritance chains that contained more than 2500 property records, as those excess properties were not being used to filter within Bulk Processing area. To remedy this, the activity now allows a maximum of 10,000 records for Bulk Processing. _______________________________________________________________________________________________________

Search criteria passed to Report Definition

SR-114575           ISSUE:  168078

The values entered in search criteria fields were not being passed to report definition, so the results were not shown in the Grid layout report. This was caused by an additional check on the classname of the parameters page while resolving filter values which are parameters, and has been resolved. _______________________________________________________________________________________________________

Check added for property with blank value

SR-114596           ISSUE:  164687

If a property is left blank in the SelectTierOverride section, updating that section showed the message "'pega' is undefined" and a JavaScript error was generated. This was traced to the filePath control included in the section, which along with refreshing the section submitted filepath data to the server: if messages are set on page using Page-Set-Messages/Property-Set-Messages, then it will try to include pega_ui_textarea js file and fail. To correct this, a check has been added for blank properties. _______________________________________________________________________________________________________

JMS MDB listener updated to support JMS 1.1

SR-114670            ISSUE:  166258 / ISSUE:  169790

A compatibility issue with SonicMQ generated the error "Caused by: javax.jms.JMSException: [JMSPool:169823]Failure occurred on createQueueConnection" during initialization of the response connection. To remedy this, PRPC has been updated to support JMS 1.1.

_______________________________________________________________________________________________________

Accessibility enhanced for keyboard access to accordion tabs

SR-114673           ISSUE:  135949 /139984 /140386 / 170001

With a design structure that has nested items, keyboard navigation was not shifting focus to the correct elements for nested items. Clicking with a mouse activated the nested item, then allowing use of the arrow keys to navigate, and tab could be used to move to the next item along with shift-tab to go back to the tab group.

All items in the top Layout Group Accordion now correctly take focus and can be activated with keyboard arrow keys. Tabbing from the active accordion takes the focus into the content of the active element within the accordion. _______________________________________________________________________________________________________

Space no longer reserved in the header for hidden custom icons

SR-114690           ISSUE:  169172

After upgrading, custom icons hidden based on visibility conditions were presenting as empty occupied space in the perform screen flow harness instead of allowing the other icons to consolidate as expected. This was caused by the cell of the harness header icon remaining in place even though the icon was not being populated, and has been corrected. _______________________________________________________________________________________________________

Portal calendar display corrected

SR-114723           ISSUE:  166462

No data was visible for the daily or weekly view when displaying the Calendar on the Portal. This was caused by the height of the time frame for Daily/Weekly being set to a fixed value, causing events which fall under 11PM-12AM to not be displayed properly. In addition, the cell width for monthly view was also set to a fixed value, causing it to show only 4 events and hiding the 'show more' option. To correct this, the Day/Weekly view now includes double height to show all events, and the Monthly view displays 3 events and correctly includes the 'show more' option. _______________________________________________________________________________________________________

Resolved locking problems with doubled flow submissions

SR-114728           ISSUE:  166514

If a Page validation message was present and an additional flow action was submitted through a second action menu, a "Lock Lost" message was generated. This was traced to the "Release on Commit" checkbox defaulting to 'on', and it has been set to a default condition of 'off'. _______________________________________________________________________________________________________

Error messages from CPM displaying correctly

SR-114757           ISSUE:  169899

When CPM Intent has Page Messages, the horizontal scroll bar and the User interface fields overlapped with a default bar at the bottom of the screen. This was caused by resizing the HARNESS_CONTENT div when the error table was present and has been corrected. _______________________________________________________________________________________________________

OOTB "Transfer to an Operator" dynamic list was not sorted

SR-114807           ISSUE:  162848

OOTB "Transfer to an Operator" dynamic list was not sorted, while the OOTB "Transfer work from" dynamic list was. This was caused by different function calls in the system, and has been corrected so the lists sort properly by property name. _______________________________________________________________________________________________________

Start times for repeating grids check for appropriate auto-refresh

SR-114816           ISSUE:  166068

If the date/time field was set only to time, entering a start time in a repeating grid caused an auto-refresh that would lose the entered time. To prevent this, a new API was added to verify whether the opened element is from grid, and if it is from grid then there is no need to auto submit. _______________________________________________________________________________________________________

Validation error display corrected for screen flow harness

SR-114882           ISSUE:  164513

Inconsistencies were appearing in the error display on the harness of the screen flow. The issue was due to the "Allow errors" value being set to true even when "Save on last step" was unchecked. While there was a workaround of unchecking both “Allow errors” and “Save on last step” options, this has been fixed. _______________________________________________________________________________________________________

ActionAutoSubmit HTML rule corrected

SR-114896           ISSUE:  168564

A flaw in the ActionAutoSubmit function caused it to require manual submission once all files were loaded. This has been corrected. _______________________________________________________________________________________________________

Radio button focus corrected

SR-114898           ISSUE:  167508

Focus was not being properly set for radio buttons, including a scenario where a section refresh on click of a radio button moved the focus to the first element within the radio button group instead of to the radio element which was clicked. This was traced to missing logic for the radio buttons, and has been fixed. _______________________________________________________________________________________________________

Corrected error message display for dynamic layouts

SR-114913           ISSUE:  165658

Multiple validate error messages for a particular field in a dynamic layout were displaying on the same line at run time and appearing as a single error message text. This was caused by error messages being directly appended, and has been changed to display each error as separate string in every span. _______________________________________________________________________________________________________

Alignment issues with IAC resolved

SR-114917 / SR-117958 / SR-118050           ISSUES:  166117 / 169612

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. _______________________________________________________________________________________________________

Operator substitutions restored to the availability settings

SR-115000           ISSUE:  165234

The operator availability setting links for Case Manager portal and Case User portal were missing substitute assignee details. These have been restored. _______________________________________________________________________________________________________

Exceptions logged for PegaAESRemote with split schema

SR-115026           ISSUE:  164316

In a split schema environment, the SPPR_POPULATE_INDEX_DATA stored procedure operates on the AES-related table PR_INDEX_INFO and is used to get index information. This stored procedure does not work with split schema because the stored procedure is not in the same schema the request is run in and the stored procedure is not schema-qualified. This issue only causes an exception in the log periodically when AES asks for index info. To avoid this, PegaAESRemote will not attempt the call to the stored procedure causing the exception, and all Connect SQLs are being updated with class reference in place of refer tables. _______________________________________________________________________________________________________

IAC functionality enhanced for secure environments

SR-115104           ISSUE:  165556

In order to ensure IAC functionality in a secure environment, the following updates were made: HTTPOnly support has been enabled for prGatewaySESSIONID cookies; encryption and obfuscation have been set up for web nodes; added a check for login-config.xml to add default-users.properties and default-roles.properties to the other application-policy. _______________________________________________________________________________________________________

Viewing generated Java code with Tracer

SR-115127           ISSUE:  163700

Previously, Tracer automatically returned the source for generated Java. This functionality was inadvertently removed, and has been restored. _______________________________________________________________________________________________________

Localization added for column section summaries in Report Definition

SR-115133           ISSUE:  166141

The summarize column section displayed while running the Report Definition now accepts localization. _______________________________________________________________________________________________________

Embedded list views enabled in IAC

SR-115166           ISSUE:  169266

While using IAC to render a PRPC harness via a gadget, the embedded list view was not being displayed and autocomplete was not functioning. This was traced to a rule defect that failed to carry over the ‘Web Enabled’ checkbox for the content tab shortcut listview. _______________________________________________________________________________________________________

Last row delete in Grid Repeat generated an error

SR-115242           ISSUE:  164582

If a Grid Repeat contains only one row, hitting 'delete' properly removed the row, but the java script error "this.rightBodyTbl.rows[...].cells is null or not an object" appeared. This error was caused by a missing null check inside the focusing api, and has been fixed. _______________________________________________________________________________________________________

Cleanup improved for resolved work-items

SR-115268           ISSUE:  166797

An error in the logic for Stage Flows caused improper cleanup of resolved work items, leading to outsized assignment tables. This has been corrected. _______________________________________________________________________________________________________

Corrected clipboard mismatch for refreshed Repeating Grid pages

SR-115272           ISSUE:  167336

When using Repeating Grid pagination in Screen Flow, refreshing the screen by choosing that option from the context menu displayed with a right-click followed by selecting 'Next' on the repeat grid caused a NPE. This was caused by a mismatch with the clipboard page, and has been corrected. _______________________________________________________________________________________________________

Japanese character support added to Report Definition PDFs

SR-115308           ISSUE:  173906

When Report Definition contains Japanese characters in its report name, column, value, etc., the exported PDF was not showing the Japanese characters incorrectly. This was due to a missing font-family for the PDF export mode, and has been corrected. _______________________________________________________________________________________________________

BIX execution history did not update all Extracted rules

SR-115313           ISSUE:  164520

If a BIX (Business Intelligence Exchange) extract was run with two extracts from the same shell script, the execution history was updated for only one of the extract rules. This was caused by the entry in the execution history (pr_log) is being overridden when the -i command line option is used. To ensure complete logging, the system has been updated to add a new entry to pr_log for every value when invoking the -i option. _______________________________________________________________________________________________________

Corrected horizontal scroll bars for listviews with custom searches

SR-115378           ISSUE:  168818

Horizontal scroll bars were not appearing when using custom search section in a list view. This error was caused by missing logic for resizing the window width, and has been corrected. _______________________________________________________________________________________________________

Flow Action support tuned for MenuBar keyboard navigation

SR-115387 / SR-112785   ISSUE:  164437 / 166486/166507

Using the MenuBar setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouse click was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected. _______________________________________________________________________________________________________

Added customization for PDF page numbers

SR-115392           ISSUE:  164192

Previously, it was not possible to designate the initial page number in the PDF generated by HTMLToPDF activity. Two parameters have been added to allow for greater customization: "header" activates page number support in the document header, and "startPage" is used to set the initial page number for the document. The "startPage" parameter can be used for both the header and footer. _______________________________________________________________________________________________________

Obj-save and commit working for fully-exposed classes

SR-115492           ISSUE:  169327

If an exposed class was implemented by creating an underlying database table, trying to perform an Obj-Save (or commit) on an exposed class generated errors regarding some properties not having corresponding database columns. This happened when one of the Page names was also the beginning part of a name of one of the simple types, and was caused by a flaw in the logic used to determine if the property is an embedded reference. This has been corrected. _______________________________________________________________________________________________________

Application Express Wizard updated to correctly bind rulesets

SR-115511           ISSUE:  168772

New Rule-Access-Role-Obj (RARO) rules created using Application Express wizard were being bound to specific ruleset versions vs. ruleset names. This caused failure to any modification to those RAROs, since modifying a RARO with a ruleset version would mean the save-as would fail if the validation found a RARO already present for that ruleset. In order to ensure proper binding and aid migration, a RARO with ties to a ruleset version will have that the version information removed automatically upon saving of the RARO. _______________________________________________________________________________________________________

Repeat Grid navigation enhanced for 'Expand Pane' edit mode

SR-115521           ISSUE:  166317

If a Repeat Grid in a section was set to 'Expand Pane' as the Edit Mode , the 'previous' and 'next' buttons on the modal dialog were not working. The logic was missing for the Next and Previous APIs when using 'Expand Pane', and has been inserted to fix this issue. In addition, the Next and Previous APIs were enhanced to be appropriately disabled when the first and last rows are reached. _______________________________________________________________________________________________________

Expanded width of Dates dropdown when using WAI

SR-115653           ISSUE:  166301

When WAI rule-set is enabled, the Dates drop down was not wide enough to display the full dates information. This was a problem with the field width being fixed, and has been changed to use an auto-set width. _______________________________________________________________________________________________________

Vertical scrollbar fixed for expandable rows in Repeating Grids

SR-115687           ISSUE:  165814

When using a Repeating Grid layout with pagination, expandable rows, a fixed size, and frozen header, expanding the row during run time caused the vertical scrollbar to disappear. The API has been updated to properly display the scrollbar for this setting combination. _______________________________________________________________________________________________________

Flow Action class correctly retrieved for subprocesses

SR-115711           ISSUE:  165363

When running a Process Flow in a Data- class that is called from a Work- process flow via a SubProcess, the error "Failed to find a 'RULE-OBJ-WHEN' with the name 'CANMAINTAINCASEREPORT'" was being generated. This was caused by incorrect handling for the class: the flow action and WHEN rule are in a WORK class, but when the sub-flow is executed it looks in the DATA class of the embedded page instead of the WORK class relevant to the overall case. There was a workaround of saving the WHEN rules into the Data- classes, but the system now uses workPage instead of interestPage for localcase to ensure the correct class is retrieved. _______________________________________________________________________________________________________

Rearranging columns in multi-tab sections corrected

SR-115717           ISSUE:  168256

When using a multi-tab section, re-arranging the columns was only effective in the first tab. This was caused by the tabs lacking individual global variables to give them unique IDs, and has been fixed. _______________________________________________________________________________________________________

WebSphere WorkManager pool setting correction

SR-115719           ISSUE:  165692

Due to a coding defect, the WorkManager thread pool setting configured through WebSphere was not being utilized. As a consequence, a large number of daemon threads could be created during certain scenarios and the ability to make connections could be reduced. This has been fixed, and the system will now use the WebSphere WorkManager setting. _______________________________________________________________________________________________________

Read-only value validation messages now appear in-line

SR-115742           ISSUE:  166472

By design, validation error messages were not displayed next to read-only values but rather displayed at the top of the harness. As this is no longer the preferred behavior, an enhancement has been added to display these read-only validation messages in-line as is seen in edit mode. _______________________________________________________________________________________________________

Support added for custom filtering and refresh inside a Repeat Grid

SR-115749           ISSUE:  167027

If a dropdown control was placed in the column header of a repeating grid to work as a filter and perform a section refresh for the list (based on a column present in the list, but not displayed in the grid), checking the option to freeze the column headers (and use a fixed height/width) caused the dropdown to no longer work and no refresh action could be triggered. This was caused by a second hidden dropdown in the grid with the fixed header configuration that overwrote the selected value in the ASYNC request that is sent when the dropdown value changes. To remedy this, changes were made in the HTML generation to make the hidden header input disabled. This works only when configured as "auto": the control generation logic overwrites all read-only conditions to true if the dropdown is configured as "Editable". _______________________________________________________________________________________________________

Improved definition of Remote Work Objects

SR-115776           ISSUE:  164938

Previously, a work object was considered remote only when it was from a different system than the Master. This caused an issue in cases when the Master and Remote Applications existed on the same PRPC instance, and the behavior has been changed to consider the WO to be remote when it is from a different application even if it is from same system. _______________________________________________________________________________________________________

Improved handling for abstract case classes

SR-115798           ISSUE:  167885

An extra hyphen was being inserted into a newly created case's class when the parent class was an abstract class already indicated by '-'. To correct this, a check has been added to avoid appending a dash if the parent class name ends with "-". _______________________________________________________________________________________________________

Instantiation logic enhanced

SR-115808           ISSUE:  169924

In an application with a parent case (CaseInstancePOC) and two lower levels of cases (Case_Level2 and Case_Level3), the top level case starter flow CaseInstancePOC creates multiple subcase instances of type Case_level2. This is caused by automatic case instantiation of Case Level3 based on Case level2 Work Status - Open being configured. In some cases, this may not be the desired behavior. For example, when there are two Case_Level2s and one work status is changed to Open, the user may want a child case to be instantiated for only that particular Case_Level2and not the other Case_Level2. To allow more flexibility, an enhancement has been added to limit scoping through the AddChildWork setting. _______________________________________________________________________________________________________

Corrected radio button visibility behaviors

SR-115839           ISSUE:  166347

Previously, some erroneous behaviors were seen with the visibility of a mandatory radio button when used in conjunction with a conditional read-only option. This has been resolved by a recent change that makes the "Required" checkbox a dropdown, fixing the design time issues. _______________________________________________________________________________________________________

Corrected flow handling for failed tickets

SR-115896           ISSUE:  167002 / 167322

Raised flow tickets using pre-existing flow-ticketed utility shapes were intermittently failing to transfer to the expected place in the flow. This was found to be an improper copy action in the task, and has been corrected. The error message has also been clarified. _______________________________________________________________________________________________________

Updated failure handling for Word editing with Internet Explorer

SR-115912           ISSUE:  168208

When using Internet Explorer, failure to load correspondence for editing in Word generated the message "Error: Loading Open Authoring Control". This was caused by the carried-over use of a span tag that is not valid under HTML5, and has been corrected with updated JavaScript. _______________________________________________________________________________________________________

Fixed read-only cascading dynamic select in Chrome

SR-115931           ISSUE:  169804

The cascading dynamic select was not working in Chrome with Read-only Mode. This was traced to an error in the dynamicselect.js, and has been corrected. _______________________________________________________________________________________________________

Corrected deadline escalation for reassigned work

SR-115934           ISSUE:  170092 / 170387 / 174331

When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queue page being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queue page is attached to reassigned work. _______________________________________________________________________________________________________

Enhanced task queue handling for custom applications

SR-115955 / SR-118567 / SR-119432           ISSUE:  167257 / 175615

In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found. _______________________________________________________________________________________________________

System updated to handle partially encrypted URLs

SR-115985           ISSUE:  169316

With URL encryption enabled, certain work types could not be loaded due to an inability to process the partially encrypted URLs. The JavaScript has been updated to correctly handle these URLs. _______________________________________________________________________________________________________

Corrected ability to add rows to a Row Repeat Grid Layout

SR-116025           ISSUE:  174180

Previously, an error was generated when attempting to add more than 51 rows to a Row Repeat Grid Layout with two more layouts containing other fields. This was caused by a duplicate call to invoke the list section, and has been fixed. _______________________________________________________________________________________________________

Update Manager performs version checking before installation

SR-116041 / SR-116439   ISSUE:  165468 / 166256

An enhancement has been added to Update Manager to prevent installation of a HFIX meant for a different release of PRPC. _______________________________________________________________________________________________________

Updated newline character for HTML

SR-116042           ISSUE:  170124

On click-submit, some text paragraphs were being displayed without breaks between them. This was caused by a missing HTML tag and has been corrected. _______________________________________________________________________________________________________

Improved handling of multipart data input

SR-116101 / SR-114595   ISSUE:  166813 / 164792

HTTP Service uses a Parse XML to map message data, but issues were found with the handling of the "multipart/form-data" format. For example, not all of the parameters were made available in the Parameter page: while the multipart data was parsed, causing the name value pair to not be properly set. To better handle multipart data, changes have been made to the Fileupload method of the HttpUtilities java file. _______________________________________________________________________________________________________

StackOverflow errors during passivation remedied

SR-116130           ISSUE:  168010

An issue was found with StackOverflow errors thrown by the passivation daemon, requiring a restart of the JVM. This was found to be related to the AutoPopulate API, and has been updated. _______________________________________________________________________________________________________

CreateUniqueID enhanced to allow custom instances

SR-116146           ISSUE:  169058

The OOTB PopulateReport activity previously used shorthand notation when referencing the CreateUniqueID function instead of referencing the function using the RuleSet or library name. This caused an issue with systems that contained a custom version of CreateUniqueID in the CMSUtilities library, resulting in "Multiple suitable instances found" errors. In order to accommodate custom instances of CreateUniqueID, long hand notation will be used for matching in place of shorthand. _______________________________________________________________________________________________________

CaseTypeValues correctly created for child cases

SR-116153           ISSUE:  165729

CaseTypeValues were not being properly set on the child case when it was added to the cover through agent creation, causing the trigger not to execute because the change was not detected. Manual creation was detected properly. This inconsistency was traced to the agent using the AddToCover activity vs. the manual creation using AddChildWork, and has been corrected. _______________________________________________________________________________________________________

Improved crash recovery in a complex system

SR-116157           ISSUE:  165994

During crash recovery in a clustered, load balanced system, attempting to recover a user's progress displayed a message that the session was recovered but the page did not then properly load the recovered data. To ensure proper crash recovery failover on complex systems, the user is now authenticated on the STANDARD thread instead of a work thread when restoring work in progress. _______________________________________________________________________________________________________

Backslash '\' now showing as expected in autocomplete and search

SR-116209           ISSUE:  166698

The AutoComplete control was filtering out backslash '\' characters when displaying the values in the list of matches, causing failures with search and autocomplete. The Rule-Utility-Function for the getProperty has been corrected to allow '\' to be handled properly. _______________________________________________________________________________________________________

Report drill downs for embedded summary charts open in a new window

SR-116220           ISSUE:  168848

If a Summary View chart has a drill down to another summary view and then to a list view, when the section is launched, clicking the pie of a summary chart in the portal gets drilled down to the next level. However, when the chart was maximized (opened in a pop up), it was not drilling down. This was traced to the way actions were configured: when reports were maximized, the main window was set to the parent window and drilling down refreshed the main window and not the maximized window. To remedy this, report drill downs now open in a new window instead of modifying the parent window. _______________________________________________________________________________________________________

Work item correspondence loading fixed for Internet Explorer 11 Enterprise

SR-116242           ISSUE:  171896

When trying to view correspondence attached to a work item, using Internet Explorer 11 in Enterprise mode, an error "Error: Loading Open Authoring Control" is generated. This was caused by the Open Authoring ActiveX control APIs used by the correspondence viewing functionality: the currently used method of verifying that an ActiveX control has been successfully loaded into the HTML page was not working in IE11 Enterprise mode, and has been updated. _______________________________________________________________________________________________________

Java error resolved for Smartinfo in list view

SR-116272           ISSUE:  168880

A JavaScript error was being generated in Internet Explorer 8 after viewing the Smartinfo popup with a list view. This was caused by calling the focus API on top of an invisible element, and has been fixed. _______________________________________________________________________________________________________

Extra Characters removed for Hot Key button labels

SR-116274           ISSUE:  164985/167730

Hot keys configured buttons were showing extra characters appended to the button label. These buttons have been deprecated, but this issue has fixed by removing the cross site scripting added for button caption. _______________________________________________________________________________________________________

Corrected a race condition with Lock Manager

SR-116286           ISSUE:  168017

In some cases, attempting to open an existing Work Object that was assigned to a workbasket with a SLA on it generated the error "The flow this assignment corresponds to has been removed". This was due to a race condition with the Lock Manager where two threads attempted to update an instance at the same time, and has been fixed. _______________________________________________________________________________________________________

Added display expansion capabilities for accessibility mode

SR-116300           ISSUE:  167205 / 169067

Previously, expanding displays with "+" in the listview category headers required a mouse click. An enhancement has been added to additionally allow use of the enter key at this location to expand and display the attachments of that category type (Notes, Files, Emails, etc.). _______________________________________________________________________________________________________

Corrected file generation using Rule Base Comparison for product

SR-116331           ISSUE:  171181

Running the Rule Base Comparison wizard on any product rules that have applications rules / data instances included caused a FileNotFound exception error. This was found to be a coding error where the system exported a .jar file but then looked for a .zip file. The export utility has been modified to correctly export a .zip file. _______________________________________________________________________________________________________

Error resolved for adding Stage Step Specifications using RTE and Chrome

SR-116347           ISSUE:  166799

While configuring a stage behavior in Chrome, if a user had focus within the Rich Text Editor for a specification and submitted the modal, an error was generated. This was caused by an invalid post-value check, and the unnecessary post value has been removed. _______________________________________________________________________________________________________

Dynamic select modified to use display value instead of property value

SR-116359           ISSUE:  169895 / ISSUE:  174215

If two different properties were used for display and values in Dynamic select, the value property was shown instead of the display value. This has been corrected. _______________________________________________________________________________________________________

Autocomplete enhanced for JAWS Accessibility Mode

SR-116379           ISSUE:  167270

When using "Auto-Complete" functionality with the accessibility framework, the "Label For" field was not being read aloud by JAWS. For example if the property's label was defined as "Station Code" , the user only heard "Auto complete edit" instead of "Station Code Auto Complete Edit", causing the user confusion as to where they are on the screen. This issue was traced to the labels for the attribute and ID of the input element not being the same, meaning JAWS was not able to find the label for the autocomplete field. To fix this, the function setAriaLabelForAC has been created in pega_ui_doc to collect all of the autocomplete inputs and choose the attribute by figuring out corresponding label. This will work only if the label is in the previous or next cell to autocomplete, and accessibility mode is enabled. _______________________________________________________________________________________________________

Ensured cleanup utility does not unexpectedly remove rulesets

SR-116397           ISSUE:  166042 /  166235

When the rule cleanup utility ran the statement "DELETE FROM pr4_rule_ruleset WHERE PYRULESETVERSIONID < '07-10' AND PXOBJCLASS LIKE 'Rule-%' AND PYRULESET LIKE 'Pega-%';", there were a few Rule-RuleSet-Name instances with pyRuleSetVersionID values that caused them to be deleted by the utility. The Cleanup script generator has been modified to add an additional where clause to exclude Rule-RuleSet-Name instances. _______________________________________________________________________________________________________

Fixed display of harness validation errors

SR-116409           ISSUE:  170363

When using TabbedScreenFlow with a section containing a repeating grid with enough data to need a scrollbar, checking the "Keep fixed header/footer visible" option and refreshing the section causes the display to shift and render the section buttons behind the harness buttons. This was caused by a misaligned display of validation errors, and has been fixed. _______________________________________________________________________________________________________

SOAP settings updated to work with IBM JDK 1.7

SR-116445/SR-116448/SR-114971               ISSUES:  169717/164164/165871/166844

When calling Service SOAP hosted on WebSphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated. _______________________________________________________________________________________________________

Elapsed Time reporting corrected

SR-116479           ISSUE:  170952

Two out-of-the-box reports, Elapsed Status Time Trend and Average Elapsed Time Per Status, were causing the browser to freeze and stop responding if there were more than 1000 records. This was caused by an invalid value for the datetime units on the category for the chart causing looping behavior. This has been corrected. _______________________________________________________________________________________________________

Large flow handling improved for Internet Explorer 8

SR-116508           ISSUE:  170253

When opening a large flow in Internet Explorer 8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on Internet Explorer 8, and has been remedied by turning on the asyncProcessing parameter for Internet Explorer 8. _______________________________________________________________________________________________________

Handling corrected for testing rulesets with multiple versions

SR-116510           ISSUE:  171699

If two rulesets with multiple versions were moved to a test environment, when the product rule was created only one of the version's instances was in the .jar file. This issue was caused by incomplete clearing of the ruleset spec after collecting the rules, and has been corrected. _______________________________________________________________________________________________________

AllLinksForParticularRule changed from Final to Available

SR-116556           ISSUE:  170813

The list view reporting limit AllLinksForParticularRule has been changed from a Final rule to an Available rule in order to allow an increase in the number of links shown in the Application Profile. The default is 500. _______________________________________________________________________________________________________

Screen flow previous button repaired in obfuscated IAC

SR-116585           ISSUE:  167063

When using IAC with obfuscation enabled, the screen flow 'previous' button was not responding. This was caused by the '\' at the end of the URL parameter being accidentally obfuscated as well, and has been fixed. _______________________________________________________________________________________________________

Clarified default values for Create Class

SR-116587           ISSUE:  170222

The Create Class screen was offering default values that had the potential to lead to classes being created in an incorrect / invalid part of the Class Structure. This has been corrected. _______________________________________________________________________________________________________

Correct report name displaying on chart reports

SR-116597           ISSUE:  169929

In Case Manager reports, maximizing a report containing a chart showed the URL as the report name if the report title parameter did not have a value. This field has been updated to default to the report's title if the name has not been explicitly set. _______________________________________________________________________________________________________

Error display settings improved for modal windows

SR-116606           ISSUE:  169617

If a flow was run in a modal window, the Field-level error display setting on the harness was not being accurately reflected,
i.e. if the field level error display option is set to "Full Text", a validation icon is displayed instead or in addition to the text. This has been corrected. _______________________________________________________________________________________________________

Removed periods after page numbers to improve accessibility

SR-116608           ISSUE:  173164

In some cases the JAWS screen reading software was reading out page numbers for paginated grids including a trailing period / full stop character, such as "2." reading as "two point". Since the page number will always be a whole number, the period/point character has been removed. _______________________________________________________________________________________________________

JAWS no longer reads out table structures

SR-116613 / SR-117230                  ISSUE:  170409 / 172209

When JAWS encountered tables, it considered them to be data tables if there were no aria labels or roles defined on it and proceeded to read out the table structure to the user. If one of the td had '&nbsp;' it read out as blank.
Table tags being generated for layouts are now given a "role" attribute as "presentation" for accessibility compliance: this will mark the table structure not to be read out by JAWS. In addition, JAWS will read out any html <LABEL for> associated to the input rather than the aria-label format information. _______________________________________________________________________________________________________

Form level messages retained by parameter for Tree layout

SR-116648           ISSUE:  170323

Error messages were not retained when "Select On Load" option was selected for the Tree control. By request, an enhancement has been added through the parameter pega.u.d.KeepMessages, and the clearing of page messages will be done depending on this parameter, both in client and server. _______________________________________________________________________________________________________

TrackSecurityChanges enhanced to capture index information

SR-116661           ISSUE:  169635

While the properties of a pagelist are displayed in the TrackSecurityChanges history tab, the corresponding index of what was changed on the page list was not included. In order to more accurately track what is being changed, an enhancement was added with new field values for tracking the index history. _______________________________________________________________________________________________________

"Save preferences" button visibility corrected

SR-116679           ISSUE:  169078

The ability to save report filtering preferences for Summary View was only appearing if the report included an interactive chart. The system has been updated to present the 'Save Preferences' button in all report types. _______________________________________________________________________________________________________

BIX Column length increased

SR-116681           ISSUE:  169378

At runtime BIX checks the target DB metadata for column length. If it could not find the metadata with schema associated with the BIX DB user, it was setting the length at 32 characters even if a larger column length was specified in PRPC and SQL. This was due to a mismatch in the stored value location, and has been corrected so BIX will reflect the length specified on the Extract rule form. _______________________________________________________________________________________________________

Execute RDB runs in batch mode for very large data sets

SR-116716           ISSUE:  167507

The executeRDB query was not able to handle very large large data sets, resulting in an OOM error after clicking "Create Prior Authorization". ExecuteRDB (which is a select query) has been modified to run in batched mode, i.e. run the same query with limit on max rows, so as to avoid OOM when copying the whole result set into the memory object (similar to Report Definition paging). _______________________________________________________________________________________________________

Added handling for SOAP elements with empty case types

SR-116719           ISSUE:  167427

If customers created a SOAP element with an attribute like <CaseStatus ID="Key">Text</CaseStatus >, the generated WSDL from services wizard did not have a type for the element "CaseStatus" and failed validation with the error "Element 'CaseStatus' with empty content type cannot have text or element content." The XML has been updated to correctly handle this use case. _______________________________________________________________________________________________________

FormatNumber use clarified

SR-116761           ISSUE:  169833

Attempting to use the pxFormatNumber function in an activity step generated the error message "com.pega.pegarules.session.internal.mgmt.Executable cannot be cast to com.pega.pegarules.pub.runtime.StreamBuilderToolKit". Formatter RUF were not intended to be called directly from activities, but RUF has been enhanced to work with reduced functionality in case it is called from activity. The documentation has also been updated to reflect preferred usage. _______________________________________________________________________________________________________

Case narrative ordering enhanced

SR-116769           ISSUE:  174513

The Case Narrative ordering appeared incorrectly when the events are very close together (multiple events within the same second), though the History items displayed in the correct and expected order. When more than one event occurred within the same second, the DATE datatype did not provide a lower level of distinction to allow more granular sorting or ordering. To resolve this, the time value for sorting is now extracted from InsKey. _______________________________________________________________________________________________________

JavaScript error resolved for repeat grids in Internet Explorer 8

SR-116778           ISSUE:  168295

When using Internet Explorer 8 and Master / Detail editing with a modal window, hitting the enter key to submit a button attached to a repeat grid caused a JavaScript error. This was traced to tabbing forward from the header of a grid: if the grid has no records, the 'no results' message was getting selected as a row and causing a miscalculation. The code has been updated to ensure the 'no results' message is not selected. _______________________________________________________________________________________________________

Focus highlighting added to sub-tabs when they receive focus

SR-116805           ISSUE:  175879

Focus highlighting was not appearing around sub-tabs when they received focus. There was a CSS workaround for this, but it has been resolved. _______________________________________________________________________________________________________

Corrected swim lane routing with shapes

SR-116818           ISSUE:  167121

While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, and has been corrected. _______________________________________________________________________________________________________

Corrected browser display errors for large decision tables

SR-116893 / SR-117937                  ISSUE:  169075 / 173922

A browser logic flaw with Internet Explorer 9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected. _______________________________________________________________________________________________________

Edit validation displays literal characters

SR-116899           ISSUE:  169326

If a property with edit-validate defined on it is included in a section with the control TextArea used, an error message is shown on top of the property if the edit validate returns false. However, the error was not shown as literal but rather displayed the encoded characters and was difficult to understand. This was traced to double encoding of characters like ">" in the displayed string, and has been changed so the literal character will appear. _______________________________________________________________________________________________________

Recent Explorer item handling corrected

SR-116903           ISSUE:  167940

When opening a Scheduled item from Recent Explorer, an incorrect flow was being called and the Review Harness buttons (which are based on flow parameters) were incorrect. This was traced to a missing TaskWrapper activity, and has been corrected. In addition, a process was added to check property as well as parameter in the Review Harness. _______________________________________________________________________________________________________

When rules now display all text fields for function aliases

SR-116908           ISSUE:  168347

Creating a new Access When rule failed to show the text fields for most available function aliases when a condition was added to the rule. This was an error in the passing of the classname to the function, and has been fixed. _______________________________________________________________________________________________________

Discarded threads set to properly clear on refresh or tab close

SR-116936           ISSUE:  167898

When the browser was refreshed or an inactive recent tab was closed on the client side, the discarded threads were not getting properly cleared at the server end. To remedy this, the JavaScript has been updated to cleanly remove the threads. _______________________________________________________________________________________________________

Improved performance for sending queued messages

SR-116941           ISSUE:  168143

LogToSpecifiedAppender was experiencing poor performance in some situations caused by duplicating locking attempts while processing an appender to send queued messages. To improve this, code changes have been made to smooth locking and avoid searching appenders when dynamic appenders are configured. _______________________________________________________________________________________________________

Rule name validation checks relaxed for draft mode

SR-116950           ISSUE:  167458 / 168328

In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode. _______________________________________________________________________________________________________

XSS alert resolved for integer type property in Edit Data Table

SR-116989           ISSUE:  170784

The presence of an integer type property in Edit Data Table was generating an XSS alert. This was caused by changes in the html- getMessagesAll that rendered the property value directly, and has been updated to an XSS-safe API. _______________________________________________________________________________________________________

Cookies only generated if IAC enabled

SR-117020           ISSUE:  167867

IAC cookies were being generated in environments where IAC was not deployed, causing the application be flagged in a security audit due to missing Secure attributes. To correct this, the system has been updated to bypass cookie generation if IAC is not in use. _______________________________________________________________________________________________________

Standardized class display options for App Explorer

SR-117039           ISSUE:  169671

Inconsistencies had appeared in how Application Explorer handled switching the display between name and label (short description) in the class hierarchy display. The App Explorer menu now shows the option to toggle between Class labels and Rule names, with a default setting of displaying Rule names. In addition, the short description display will not include the rule purpose. _______________________________________________________________________________________________________

Thai characters now working in eform generated PDFs

SR-117047           ISSUE:  173480

PDFs generated using OOTB Map-eForm rules worked when data was entered in English, but data entered using the Thai keyboard was not reflected in the generated PDF. The root cause of this problem was a third-party product integrated with PRPC. iText is used to convert eForm data into PDF, but it was not honoring the appearances set to the acrofield. To remedy this, the included version of iText has been updated to version 2.1.7, and the NeedAppearance setting for the AcroFields now 'true' by default. _______________________________________________________________________________________________________

Corrected property inheritances in the XML assembler

SR-117085           ISSUE:  169328

An error was noted where some attributes for IdentifierType elements were not being created in parse XML for the WSDL consumed. All attributes should passed down from the base type to the derived [restriction] type, but a Parse XML assembler issue combined with a defect in XML Rule Builder caused the Parse/Stream rule nodes to not inherit attribute nodes from the parent type(s). This has been corrected. _______________________________________________________________________________________________________

Added localization formatting for date values (YYYY-MM-DD)

SR-117114           ISSUE:  171740

In Sweden, dates are given with a hyphen “-” and not slash “/” as the date separator as per ISO-8601. The SV localization has been changed to follow this style. _______________________________________________________________________________________________________

Corrected Rule cleanup utility

SR-117131           ISSUE:  167711

The Rule Cleanup utility deletes instances from pr4_rule_ruleset that contain old ruleset versions. Some Rule-RuleSet-Name instances have rulesets and were deleted incorrectly. To correct this, the utility has been modified with an additional 'where' clause to restrict deleting Rule-RuleSet-Name instances. _______________________________________________________________________________________________________

Corrected inclusion of "Other Specifications" in Document Wizard

SR-117158           ISSUE:  169361

The 'Other Specifications' section of the application doc was being included regardless of whether the checkbox was selected in step 4 of the Document Wizard. This has been corrected to ensure 'Other Specifications' are documented only when they are selected. _______________________________________________________________________________________________________

Tightened vertical privileges

SR-117164           ISSUE:  169821

If a User with lower rights accessed the cookie of a Manager, it was possible to update the Operator Details. A privilege check has been added when saving the operator record to resolve this issue. _______________________________________________________________________________________________________

Dynamic system settings for address map control updated

SR-117173           ISSUE:  168365

Due to an error, the dynamic system settings for address map control had a value pre-set instead of a blank default. This has been corrected. _______________________________________________________________________________________________________

Error message logging improved for DB2

SR-117204           ISSUE:  168225

During normal development activities, a console log was showing a large volume of Integrity Constraint Violation Exceptions that seemed to correlate with the level of activity of users and the number of concurrent active users. The system uses infoForced to make sure "real" errors are reported, but attempts to suppress those deemed to be "noise". In this case, the system was lacking an additional "if" test for DB2, and this has been added. _______________________________________________________________________________________________________

Corrected datetime calendar validation on forms with messages

SR-117205           ISSUE:  171200

When messages were present on a form (validation, etc.) and the date selector was used, the screen blanked after selecting the date. This was caused by an error in the datetime calendar popover and has been resolved. _______________________________________________________________________________________________________

Validation corrected for Case Manager portal types

SR-117216           ISSUE:  168600

After migration, changing the application header text for the Case Manager portal was throwing the error "pySkinType: ** You must specify a skin to use or select "Default to Application Skin" upon checkout. To correct this, the validation activity step has been updated with a 'when' expression to skip this validation for mobile portals _______________________________________________________________________________________________________

Resolved issues with Flow shapes distributed across Swim Lanes

SR-117228           ISSUE:  168249

Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions. _______________________________________________________________________________________________________

Modified SaveAs function for reports to avoid duplication

SR-117252           ISSUE:  174014

After using "SaveAs" on an existing report, subsequently using "Save" caused two instances of the report to be saved into the database with the same key. The SaveAs function has been modified to correct this. _______________________________________________________________________________________________________

Required fields corrected for repeating grids in accessibility mode

SR-117255           ISSUE:  174772

When using a repeat grid with required fields in accessibility mode, the field displayed multiple asterisk symbols instead of one. This problem was with workform_accessibility.css, and was resolved by changing the background image url to "transparent". The "REQUIRED" text was also not showing with Internet Explorer 8: this was noticed only in Internet Explorer 8 Standards mode, and an accessibility check was added to generate the span containing REQUIRED text in the html stream. _______________________________________________________________________________________________________

Clarified "time" display for Calendar

SR-117265           ISSUE:  169903 / 170246

While using pxCalendar in a section to display task time, '?' was displayed near the current time in Daily and Weekly view. To avoid confusion, the '?' symbol has been replaced with the text 'Time' in a field value, which can be overridden accordingly. _______________________________________________________________________________________________________

Prompt Select modified to properly handle XSS functions

SR-117266           ISSUE:  173481

A selection made in Prompt Select was not retained after refresh when special characters were present in the selected value. This was caused by XSS filtering functions that compared an encrypted value with the prompt value and negated it when it wasn't equal. To fix this, PromptSelect has been modified to call the crossScriptingFilter API before appending strDefaultValue to the stream. _______________________________________________________________________________________________________

Improved submit flow for better accessibility with JAWS

SR-117307           ISSUE:  171895

When the Create or Submit button on a flow action is clicked, dismissing the "You are about to change the current window" popup would sometimes cause JAWS to read extraneous messages such as "Create button unavailable" and "Main region end". This behavior was sporadic and depended on how quickly the popup was dismissed. In order to avoid this, the button function calls have been modified. _______________________________________________________________________________________________________

Export to Excel replaces embedded control characters in APW

SR-117391           ISSUE:  170006

In Application Profile Wizard, attempting to Export to Excel would fail if any specifications text contained an embedded control character (such as might appear after cutting and pasting from a Word or text file). To prevent the exporting failure, any control characters introduced into the generated data are now replaced with spaces during the export process. _______________________________________________________________________________________________________

Accessibility expanded to cover OOTB controls and dynamic layout

SR-117393 / SR-117836   ISSUE:  171186 /171042

Previously, OOTB controls like DropDown, DateTime, and Icon were not marked as accessible. These controls have been updated to be included in the accessibility framework. In addition, the accessibility report was erroneously flagging dynamic layouts as not accessible: properties that only freeform layouts use, which would be legitimate reasons for flagging accessibility issues, are flagged for dynamic layouts if they happen to be present. This has been corrected. _______________________________________________________________________________________________________

Corrected handling of double quotes in work objects

SR-117421           ISSUE:  137938 / 168331 / 168940

If the subject (.pyLabel) property in a work object contained a double quote character at the end of the text string, the error "Null Pointer Exceptions in SafeURL" would occur in the Case Manager portal. This was caused by a double-call to the escape encoding for these characters, and has been corrected to encode them properly. _______________________________________________________________________________________________________

Resolved performance issues when R-D-E referenced a data page

SR-117428           ISSUE:  169351 / 170976

If a declare expression referenced a data page, loading or refreshing a section in update mode caused Rule-Declare-Expression to check whether inputs had changed. The R-D-E then loaded the data page (but didn't pass any parameters), causing the data page to load the max number of pages allowed. Subsequently, a series of other R-D-Es fired on that data page as inputs had changed, ending up with a large number of R-D-E’s firing that weren't required for a section. As a result, the elapsed time was higher than expected for every screen where this was happening and CPU consumption was high. Auto Population should only trigger on reference to a non-key and non-param property, and this has been implemented. _______________________________________________________________________________________________________

Delete All Links' button disabled if rule is read-only

SR-117461           ISSUE:  169210

When an Application Requirement rule is read-only due to being in a locked ruleset etc., the Delete All Links button was offered as an option. In order to avoid confusion, the Delete All Links button is now read-only when the rule is not editable. _______________________________________________________________________________________________________

Tuned positioning of 'Party Role' by eliminating white space

SR-117509           ISSUE:  168620

The displayed Party Role in Work Parties was poorly positioned due to unnecessary white space. This has been fixed. _______________________________________________________________________________________________________

History Audit information corrected for validation failures

SR-117513           ISSUE:  169033

Following a validation failure in a flow action where validation is done in the post-processing activity, one line of history was being written for each validation failure in addition to one for the successful Submit. This was caused by the activity writing the history for a local flow action prior to calling the RunFlowActionActivity in which the validation occurs. This has been corrected to avoid history entry for error cases. _______________________________________________________________________________________________________

Smoothed flow action migration

SR-117559           ISSUE:  173118

Two incorrect behaviors were seen when using upgrade utilities:
First, the "Convert Flow Action" utility did not automatically reference the new section it created for each flow action on the updated flow action. Additionally, Visible When Conditions on layouts in the flow action were incorrectly adopted to control the visibility of sections defined on the updated flow action. These issues were caused by inconsistent population of certain values within the rule data for upgraded flow actions, and have been resolved. _______________________________________________________________________________________________________

Fixed disappearing menu in modal dialog for Internet Explorer 11

SR-117573           ISSUE:  171739

After launching a local action in a modal dialog from a Navigation rule while using Internet Explorer 11, dismissing the local action caused the navigation rule to disappear until the browser was manually refreshed. This was caused by a routing issue with the menubar call that failed to correctly reload the menu, and has been corrected. _______________________________________________________________________________________________________

Draft Mode now includes referenced rules for shape sub-processes

SR-117583           ISSUE:  170260

If a a flow was created in Draft Mode and shapes were added, adding subprocess shapes and implementing one of the subprocesses created a list of Referenced Rules that did not include the sub-flow rules. This was caused by dangling connectors, and has been corrected by a call that will generate the Java for the flow even when this condition is present. _______________________________________________________________________________________________________

Improved Bulk Action checkbox handling

SR-117591           ISSUE:  171917

In Case Manager Portal, when multiple work items (>3) were selected and transferred with Bulk Action, some were deselected and are not processed. This was traced to the select of checkbox calling an activity, followed by parent section refresh with refreshed all checkboxes. If checkboxes were selected while the refresh was in progress, the value for the next selection was not posted even though it appeared to be checked. This has been corrected to ensure all selected checkboxes are posted properly. _______________________________________________________________________________________________________

Increased limit for Application Document flows

SR-117604           ISSUE:  169493

Application Document previously limited the number of flows to 50 and would not list those exceeding the limit. This limit has been removed. _______________________________________________________________________________________________________

Fixed portals enhanced for Internet Explorer 10 and Internet Explorer 11

SR-117606           ISSUE:  173816

An enhancement has been added to the system to ensure portals will render accurately in Internet Explorer 10 and Internet Explorer 11. _______________________________________________________________________________________________________

Smart Shapes use properly limited to work class

SR-117674           ISSUE:  170571

An error in the code made Smart Shapes visible when creating a data-class flow. Attempting to include them by dragging them into the flow design pane resulted in an "empty" utility shape that was missing many of the options normally offered. Because Smart Shapes are designed only for work classes, Smart Shapes will not be visible in shape menu when a flow is created in data class. _______________________________________________________________________________________________________

BodyVisibleWhen updated for repeating tab layouts

SR-117744           ISSUE:  172508

Previously, repeating tabbed layouts had the option of BodyVisibleWhen in the properties of the layout for referring to a 'when' condition of the pagelist property. After migration, attempting to use the 'when' condition took the class of the section and not the class of the pagelist. The ValidateSection and its includes have been modified to properly consider the tabbed/column repeat 'when' condition validation. _______________________________________________________________________________________________________

WebSphere WorkManager enabled and thread handling improved

SR-117750           ISSUE:  174755

An enhancement has been added to allow the use of WebSphere’s WorkManager and correctly handle the generated threads. _______________________________________________________________________________________________________

Changed decimal values to comma values for NL/SE localization

SR-117752 / SR-119243   ISSUE:  171493 / 175219

The Dutch and Swedish convention for decimals is to use a comma as the separator instead of a dot. This use was not included in the localization so clicking submit caused the comma values to be converted with a decimal point that multiplied the value by 100. (1200,00 is twelve hundred euros; the value became 120,000.00 - one hundred and twenty thousand euros) This has been fixed so the values are correctly handled with commas when localized to NL or SE. _______________________________________________________________________________________________________

Support added for Alternate Domain URLs

SR-117788           ISSUE:  160084 / 172850

Open URL' in a window action configured in a navigation rule was not passing on configured parameters in the alternate domain URLs. Support has been added to pass on the parameters if an alternate domain is used with openUrlInWindow action in an old menu. _______________________________________________________________________________________________________

Corrected Internet Explorer handling of date picker in Report Definition custom sections

SR-117805           ISSUE:  173117

A report definition configured to use a custom section for filtering caused a JS error in Internet Explorer browsers when selecting dates from the date picker multiple times. In Internet Explorer only, the DOM object containing the popup is removed from the DOM after refreshing, but the reference, _container, is not nulled. As a result, Internet Explorer was trying to reuse a DOM object that wasn't present on the screen. This has been corrected. _______________________________________________________________________________________________________

Updated UUID generation to function with Ping Identity

SR-117815           ISSUE:  170081

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 "_". _______________________________________________________________________________________________________

Autopopulate correctly set/disabled in the CSR portal

SR-117840           ISSUE:  170516

Switching to some clipboard pages caused a null pointer error in the CSR portal for the operator. This was caused by an autopopulate call being made even when autopopulate was disabled. This has been corrected. _______________________________________________________________________________________________________

Auto-refresh only available for Section Tabs

SR-117844           ISSUE:  170991

When the "Refresh when active" checkbox was checked in a harness used in the Case Manager dashboard, creating or closing a WO did not update this page automatically. This is because auto-refresh is unsupported in the harness; it is better to use Section Tabs (the best practice statement explains why) and they are encouraged over using Harness tabs. In order to make this use clear, the auto-refresh checkbox will not be displayed in harness tabs. _______________________________________________________________________________________________________

Handling enhanced for custom system names

SR-117847           ISSUE:  172996

If the system.name property in setupDatabase.properties was updated to reflect a custom System Name during ruleset migration, the value was not being used by the software update process and the resulting error caused a batch failure. There was a workaround of explicitly setting the system name in the field env name="Identification/SystemName" value=, but this has been updated to fetch the name from the db. In addition, the query that fetches the system name has been modified with a check to make sure that there is at least one requestor for the name it fetches. _______________________________________________________________________________________________________

Resolved NPEs during case creation

SR-117855           ISSUE:  171394

If a null pointer error was generated during the case creation process, all subsequent records being processed also generated the error. This issue occurred when adding and later removing work party data, and was found to be related to a stack trace not being generated for the reported issue and an attempt to index a change to a page that’s no longer available. To correct this, a code change now handles the condition which caused the NPE (writes an index for a non-existent page and then skips it) then logs information for analysis. _______________________________________________________________________________________________________

Warning message displays for ruleset save in lower version

SR-117921           ISSUE:  174204

If a developer tried to save a rule in lower ruleset version while the same rule is already in a higher ruleset version, this was allowed with no warning. This behavior has been corrected. _______________________________________________________________________________________________________

Remedied spurious size alert from the attachments viewer

SR-117923           ISSUE:  171578

When listing attachments from History & Attachment display, the work object was re-read for each attachment. If the work object had many attachments, the alert "PEGA0004 alert (50MB DB threshold)" would appear regardless of the actual attachments' size. This has been adjusted so the RUF attachment access makes use of the existing WorkPage instead of re-reading it from the database. _______________________________________________________________________________________________________

Improved error handling for 'Response Data Transform'

SR-117928           ISSUE:  174886

When creating a data page with ‘List’ structure and ‘Connector’ as datasource, it is mandatory to use ‘Response Data transform’ (Else throws an error and unable to save data page). However, when ‘Response Data Transform’ is used, connector error handling details (pyStatusValue, pyHTTPResponseCode and pyStatusMessage) are not saved to the datapage. To correct this, the system has been updated to always call 'response data transform' even in failure cases, enabling the mapping of the error information coming from the data source page (intermediary page) onto the primary data page. _______________________________________________________________________________________________________

Datetime conversion smoothed for SQL queries

SR-117961           ISSUE:  174233

If the date time format on an SQL Server 2008 instance is set to ydm, a datetime conversion error was created due to the PRPC query using ymd format. In order to support all date formats for SQLServer, Timestamp is now formatted as "yyyyMMdd HH:mm:ss:SSS". _______________________________________________________________________________________________________

Tabbed display validation error resolved for DB2 z/OS

SR-117999           ISSUE:  177374

When running in 'tabbed' mode using DB2 on z/OS, it was not possible to select 'ACTIONS' nor 'WRAP UP' the call. This was due to the Rule html fragment UserWorkForm being taken from Pega-UIEngine instead of from the local application after validation failed following improper execution of an complex query. Further analysis found that the query was looking for records in list (0,2). As the DB setting of in this error situation was Decimal=comma, it was not taken as list but as single value 0,2 (a decimal value). This has been mitigated by adding a space before the '2' so that it will taken back as a list. _______________________________________________________________________________________________________

Spellcheck on text area fixed for Internet Explorer 8

SR-118016           ISSUE:  174520

Using Internet Explorer 8, a text area with SpellCheck enabled generates the error "Script Error: Message: 'null' is null or not an object" if there is more than one line present. This was caused by the handling of the check for list length, and has been modified to work with all browsers. _______________________________________________________________________________________________________

BIX filtering corrected

SR-118029          ISSUE:  173069

Bix filters were not working consistently due to a missing call in the logic handling the ruleset references, and are now working correctly. _______________________________________________________________________________________________________

Corrected column width auto expand issues in decision table

SR-118036           ISSUE:  171165

Decision tables which have many columns (8+) will expand the width very wide automatically by just clicking the resize cursor (no dragging is necessary). However, trying to resize it back to a more reasonable width caused it to keep getting wider and wider due to an error with the dynamic display logic. This has been fixed. _______________________________________________________________________________________________________

Added edit format for Designer Studio integer control in read-only when

SR-118053           ISSUE:  172515

In the Integer Control for Designer Studio, it is not possible to set properties on the Edit Format when the presentation is Read-only based on a when rule.
Both the Formats appear when the Edit Options is selected as Auto. Options have now been added to set the properties. _______________________________________________________________________________________________________

CorrNew activity can send email in sync or batch

SR-118061           ISSUE:  175102

When attempting to send email correspondence in synchronous mode i.e. not via the agent processing, the activity always queued it to the agent even when the Activity CorrNew SendNow param was set to true. To correct this, the system will pass the value of a BatchSend param based on the value of the SendNow param: email will be sent immediately If SendNow is set to 'yes', or will be queued for batch processing if SendNow is set to 'no'. _______________________________________________________________________________________________________

Excessive logging addressed in Pega Mobile 4.3

SR-118077           ISSUE:  170104

In PegaMobile, the oLog debugging statements were generating excessive log files. This has been addressed in Pega Mobile 4.3. _______________________________________________________________________________________________________

Focus correctly set for dynamic select using accessibility

SR-118081           ISSUE:  169902

When using a cascading dynamic select control configuration with the PegaWAI accessibility ruleset, setting the focus of the first DS list did not work when attempting to navigate the UI components via the keyboard. When reaching the first DS control, users could only select the next item in the list and then the focus switched to the second DS list immediately. The DynamicSelect control was missing a name attribute, and has been updated to address the focus issue. _______________________________________________________________________________________________________

Improved accessibility for UI properties

SR-118106           ISSUE:  174462

When a property is put on the UI from a different Page the generated UI was not setting the correct LabelFor - it stripped the Page context but didn't strip the dot from the front of the property. Accessibility JAWS and other assistive technologies were therefore not associating the label with the input and did not read it out for the given input. The label generation function has been changed to address the reported issue. _______________________________________________________________________________________________________

Drop-down focus modified for accessibility

SR-118111          ISSUE:  175580

When an onChange event is set on a dropdown (select) while using the accessibility framework, the focus automatically shifted onto the next element in the UI. This was not the desired behavior, and the system has been modified. _______________________________________________________________________________________________________

Circumstance property value carried into dropdown options

SR-118125           ISSUE:  171188

If a property of mode single value and type text was created with a defined local list of property values for the property, the value field was not automatically included in the dropdown options when attempting to use this property for circumstance/specialized flows. This was caused by an incorrect refresh section strategy used to determine when to reload the section for the circumstance by property, and has been corrected. _______________________________________________________________________________________________________

Corrected date display in graphs

SR-118144           ISSUE:  171689

The incorrect date was being displayed in graphs after using the Month function alias to get the first day of the month. The grid displayed when running the show data option in the graph contained the correct date. This was caused by a problematic time conversion in graphs for a specific timezone, and has been fixed. _______________________________________________________________________________________________________

Improved handling for Case notes when spellchecker is active

SR-118159           ISSUE:  174990

If a lot of content was added for a case Note, clicking the Notes tab caused the text to display in a big yellow box which could not be dismissed. This was traced to the spell checker not properly handling RTE's hidden textarea field, and the code has been modified to correct this. _______________________________________________________________________________________________________

Property History TaskName field expanded

SR-118170           ISSUE:  171859

Previously, the TaskName field was limited to 32 characters. This has been expanded to 128 characters. _______________________________________________________________________________________________________

Sorted Report Definition drill downs corrected

SR-118174           ISSUE:  173341

For some configurations, the Report Definition drill down did not work when it has been sorted. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was caused by an error in calling the page sort in cases where 'do not display group headers' was checked, and has been corrected. _______________________________________________________________________________________________________

Drag and drop work reassignment corrected

SR-118190           ISSUE:  172520

An error was found that prevented the ability to drag and drop a request from workbasket to worklist or from worklist to workbasket in the Case Manager portal. This has been corrected. _______________________________________________________________________________________________________

Declarative refresh now working for Internet Explorer

SR-118194           ISSUE:  170594

When using Internet Explorer, property changes on the clipboard did not trigger a declarative refresh. This was traced to a duplicate refresh section list that was not getting cleared properly with addition of cross thread change tracking, and has been corrected. _______________________________________________________________________________________________________

LookupList opened to unauthenticated requests

SR-118259           ISSUE:  173287

When a list lookup was called from an unauthenticated service, it failed due to the lack of required authentication. The activity RULE-CIRCUMSTANCE-DEFINITION LOOKUPLIST has been modified to allow its execution by an unauthenticated requestor. _______________________________________________________________________________________________________

Report definition reference columns expanded to include data type smallint

SR-118305           ISSUE:  171562

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. _______________________________________________________________________________________________________

Integers with embedded spaces now prompt screen edit during validation

SR-118307           ISSUE:  172330

If an Integer property was populated with a number with spaces ("12345 67890"), it generated the validation error "** PropertyValueInvalid null .pegaToInteger() Invalid number format (was 12345 67890)". A numeric value with embedded spaces will fail during conversion to Integer, but this will now be caught with a screen edit in the same way a non-numeric character would be during screen validation. _______________________________________________________________________________________________________

Resolved missing Datatype issue for report definition resolution

SR-118369           ISSUE:  169422 /170799

After migration, the error "No enum const class com.pega.pegarules.data.external.rd.constants.ColumnType.FLOAT" occurred during the resolution of the report definition. This was caused by a missing Datatype, and support for Datatype Float has been added for external db column types. _______________________________________________________________________________________________________

Ensured Application Document wizard captures all subflows

SR-118415           ISSUE:  172879

The Application Document wizard was documenting only some of the flows that were expected to be included. This was caused by an incorrect null check on the input parameters which treated the subflows as duplicate flows, and has been updated. _______________________________________________________________________________________________________

Improved error handling for iFrame XSS

SR-118512           ISSUE:  175817

When using cross-site scripting with iFrame, attempts to use auto-complete did not populate data and an 'Access Denied' error was raised when keywords were entered for searching. While the system cannot access or modify iFrame content from another domain, the JavaScript for the autocomplete function has been modified to correctly handle any exceptions thrown while accessing iFrame from a different domain. _______________________________________________________________________________________________________

Fixed server error alert generated by portal logout

SR-118528           ISSUE:  175205

A "Server Error " error was being generated when logging off from "List views/Summary Views" in the Portal Dashboard. This occurred when the request to unload the page reached PRPC after the end session completed and the request to unload was unable to find the associated session on the server as it has been already invalidated. The Wizard_MainWindow HTML rule has been modified to smooth the timing and clear the clipboard properly. _______________________________________________________________________________________________________

Externally mapped class hierarchy given precedence over default mapping

SR-118604           ISSUE:  175098

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. _______________________________________________________________________________________________________

JMS-MDB Listener deployment descriptor updated for EJB 2.1

SR-118622           ISSUE:  175815

The generation of the MDB Deployment Descriptor has been modified to comply with EJB 2.1 specifications. _______________________________________________________________________________________________________

Corrected duplicated validation errors

SR-118675           ISSUE:  172991

In some cases, validation error messages were being duplicated in the display. This was traced to code in the dynamic display being executed twice, and has been corrected. _______________________________________________________________________________________________________

Enhanced access to work object attachments

SR-118692           ISSUE:  176658

When a new work object is created and attachments are added in the advanced view, they are added to a list of all attachments that is sorted by the attachment type. A single-click opened an attachment normally, but a double-click opened the next attachment instead of the target attachment. Since this was not intuitive behavior, the system has been updated to accept both a single-click and a double-click to open the target file. _______________________________________________________________________________________________________

Corrected XML generation with element substitution

SR-118705           ISSUE:  174935

When an XSD schema with XML element substitution was imported using the Integration -> Connectors -> Create Other integration option and the option to generate substitution groups was chosen, the parse rule was generated properly, but when it was embedded within another element it was not outputting properly. Similarly, when parsing an embedded element that has type substitution, it only parsed the common parts and ignored elements of the specialized type. This was traced to incorrect mapping rule generation for element substitutions, and the rule generation has been enhanced to create the appropriate component rules. _______________________________________________________________________________________________________

Excessive length of filter window corrected

SR-118722           ISSUE:  175625

In work object Audit window, the History table -> Description column filter window is appearing very long. This was caused by an inadvertent change to the listview function in conjunction with the Time column filter, and has been fixed. _______________________________________________________________________________________________________

Corrected focus for filter window using WAI

SR-118725           ISSUE:  174420

With WAI enabled for work object - Audit window- History table - Time column, clicking Filter window did not properly move the focus to the first element i.e., Add/Remove columns link. The getFirstInputElement API has been modified to fix the reported issue. _______________________________________________________________________________________________________

Handling corrected for drag and drop image attachments from Outlook

SR-118738           ISSUE:  172565

If a document containing an image was added to a work object from Outlook via drag and drop, it would be corrupted when opened. This was caused by an encoding/decoding mismatch - the encoding differed depending on whether the file was first saved to the desktop or not, but the decoding did not take that into account. This has been corrected. _______________________________________________________________________________________________________

Change Password redirect loop fixed

SR-118880           ISSUE:  172588

When URLEncryption is enabled along with Security Policies, redirection to the Change Password screen caused the browser to loop into an endless redirect (HTTP 302 loop). This was caused by Incorrect (un-obfuscated) data being used internally when obfuscation was enabled, and has been fixed. _______________________________________________________________________________________________________

Create Work correctly encodes Japanese characters

SR-118884           ISSUE:  172536

When Japanese characters are passed as parameter to Create Work action, the newly created work item was registering cryptic characters instead of the expected Japanese characters. This was traced to a deprecated API, and has been corrected. _______________________________________________________________________________________________________

Fixed CPM alerts popup for Internet Explorer 8

SR-118929           ISSUE:  177444

The CPM messages and Alerts screen was not displaying correctly in Internet Explorer 8, and the selecting the 'Show All Workgroups?' checkbox did not show the workgroups on the 'Create a new alert message' popup window. This was caused by the z-index of chart legend being higher than the modal dialog, and has been fixed. _______________________________________________________________________________________________________

Smoothed error handling for searching in listview gadgets

SR-118956           ISSUE:  175342

When using a gadget with a listview that includes a header and has "Display data in a frameset" under the Format tab checked, a sporadic "Missing Property .pyStreamName" error appeared when performing a search. This was traced to a timing issue with multiple clicks that caused some pages to be cleared once the report has been run. To correct this, whenever the stream name is empty, an error message to resubmit the request will be displayed to the user instead of an exception. _______________________________________________________________________________________________________

Corrected error flag location in layout with hidden tabs

SR-118970           ISSUE:  176298

When working with a harness using tabgroups layout with multiple tabs where each tab contains sections with properties that are associated to validation rules, when validation failed the red cross error icon appeared on the wrong tab. This issue only occurred when there was a hidden tab in-between. This was caused by missing logic for handling the hidden tabs scenario, and has been fixed. _______________________________________________________________________________________________________

Clipboard privileges tightened to enhance security

SR-119030           ISSUE:  172922

Using standard browser development tools, it was possible to insert a client-side modification into a Pega-served HTML page to allow a customer to access partial clipboard inspection functionality. To correct this, starting activity privileges have been tightened. _______________________________________________________________________________________________________

Flow rule form header fixed for Chrome

SR-119036           ISSUE:  176992

When using Chrome, the background flow rule form header was dragged upwards and became invisible when any shape property dialog box was scrolled down to specifications tab. No scroll bar was presented to scroll the flow rule form back to the original position, resulting in inaccessibility of the header of the flow rule. This was caused by the presence of hidden iframes that were not properly handled by the display, and has been fixed. _______________________________________________________________________________________________________

Corrected drop-down onchange event firing for accessibility mode

SR-119055           ISSUE:  174515

If a select button was associated to a DynamicSelect control in a Cascading Dynamic Select configuration with WAI, at runtime, the child DynamicSelect list was auto loaded once the value on the parent DynamicSelect list was changed. In accessibility cases, the select button was introduced to be beside the drop down to set the value selected from the drop down. However, in cascading dynamic select, selecting the value from first drop down caused the values in the second drop down to load because an onchange event was fired. In order to handle this correctly, pega_ui_dynamicselect js has been updated to not fire upon change event when in accessibility mode, but instead fire upon click of the select button. _______________________________________________________________________________________________________

Calendar Control accessibility enhanced

SR-119074           ISSUE:  175337 / ISSUE:  176791

In accessibility mode, the Calendar Control defaulted to the current year +/- 10 years. This did not allow dates for lifetimes or for long-term activity dates. In order to improve functionality, the dynamic system setting pyNumberofYears has been inserted to allow modification of the datetime cell properties as desired. _______________________________________________________________________________________________________

TagCloud rendering corrected

SR-119095           ISSUE:  174195

When opening pxTagCloudViewGadget, it generated the error: 'Unable to open an instance using the given inputs: pxObjClass = "Rule-Obj-Report-Definition", pyClassName = "", pyStreamName = ""' . The tag cloud gadget reported "Can not render @baseclass.pxTagCloudInit", and when run or included in a section, it did not render any tags. This was found to be a design time error in Obj-Open of the report definition, and has been fixed. _______________________________________________________________________________________________________

Security Enhancement to the pzTransformAndRun activity

SR-119114           ISSUE:  173899

As a security enhancement, a new pyAllowTransformAndRun 'when' rule (available rule) can be invoked by the activity pyTransformAndRun. By default this 'when' rule returns true, but this rule can be customized to validate the values of the parameter pyPreActivity and return true if it contains an invalid activity name. _______________________________________________________________________________________________________

"?" character allowed in URLs with get requests

SR-119130           ISSUE:  173876

When specifying an Alternate Domain URL for a link, if the URL contained a GET request followed by parameters ("?get&p1"), the URL was modified by SafeURL to include an "=%26" between the "?" and "get" ("?=%26get&p1")
(%26 is url encoding for an ampersand & ). In order to ensure alternate URLs are properly processed when they contain "?", a check has been added. _______________________________________________________________________________________________________

MSSQL columns with spaces in the name will generate an error seeking correction before submission

SR-119148           ISSUE:  173101

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. _______________________________________________________________________________________________________

Amended login caching to be compatible with new versions of Firefox

SR-119158           ISSUE:  175351

When using the latest versions of Firefox browser (32+), there was a problem with logging in again after logging out. This was caused by a change in the cache engine for Firefox, and the system has been updated to compensate for the difference in caching. _______________________________________________________________________________________________________

DefaultValue API updated to retain values after deleting rows

SR-119223           ISSUE:  177088

When deleting rows from a repeating grid configured with read-only dynamic select control, the remaining rows were not properly holding their values. For example, if the row number to be deleted was "x", the "x+1" row occupies the Xth row place, but x+1th row's drop down value becomes lost and resets to "-Select-" value (Default Value). This was caused by the setOptionAndCaption API setting default caption instead of default value for the option tag. To remedy this, the DS_setDefaultValue API has been updated. _______________________________________________________________________________________________________

Max limit error localized and variable added for unsaved work items

SR-119239           ISSUE:  173898

In order to allow a local value for the number of unsaved work items, a new Field value has been created : MAXIMUMTABSALERT. In addition, the error message text "You have reached the maximum limit for pending changes. Please commit/cancel one or more changes to continue" is now available for localization. _______________________________________________________________________________________________________

Localization improved for Lithuania

SR-119246           ISSUE:  178095

If the localization was set to Lithuania, using a property of type Date with a control pxDateTime and configuring its display mode to Dropdown Lists only allowed 'month' to be selected rather than the whole date. In addition, the three letter month abbreviations were ambiguous, using "Rug" for both Rugpjutis (August) and Rugsejis (September) rather than Rgp and Rgs. These issues have been fixed. _______________________________________________________________________________________________________

Purge/Archive on a cover case now auto-includes the covered objects

SR-119342           ISSUE:  176846

On running the Purge/Archive wizard over a cover case, only the cover case was archived while the underlying covered objects were not purged. This was caused by code that required the classes of the covered items to also be selected for purging. Since this was not the expected behavior, the code has been updated so that if a cover class is archived or deleted, its covered classes will also be included. _______________________________________________________________________________________________________

Improved speed for deleting repeat grid rows with Dynamic Select

SR-119537           ISSUE:  174774

When deleting rows from a repeat grid with Dynamic Select and heavy HTML, deleting the first one was very fast but a delay appeared when there was one row left in the repeat grid. The browser message "Pegacloud not responding due to a long-running script" would also be displayed. This was found to be caused by a list-to-list control function being invoked for each processOnBeforeSubmit call which generated an increased number of input elements in the form. This has been corrected. _______________________________________________________________________________________________________

Detection added for custom work history tables

SR-119538           ISSUE:  177397

In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present. _______________________________________________________________________________________________________

Updated ObjClass name handling for XML generation

SR-119560           ISSUE:  175797

When an extract rule is run with output as XML and the pxObjClass was not selected manually, the XML generated had pxObjClass tag and values, but the definition was not present in XSD. This was caused by the code that generated the XML having pxObjClass set in the resulting page; this was incorrect as pxObjClass needs to be written to XML only when it's selected or if the -c option is used to differentiate different classes in the hierarchy. The code has been updated. _______________________________________________________________________________________________________

PDF field mapping corrected for modal dialogs with Internet Explorer

SR-119578           ISSUE:  175170

When using Internet Explorer, some fields within a modal dialog were not properly populated in a generated PDF. This was caused by the PlaceHolder text becoming an actual value after an AttachAfile local action with a multi-part content file, and has been resolved. _______________________________________________________________________________________________________

Corrected resizing issue with screen layout skin

SR-119610           ISSUE:  177443

An issue was found when mixing re-sizable and non-re-sizable widths in the Header 'Left Right Screen' layout for EndUser71 skin. On screen load, the panels appeared with the correct size, but once the right panel was closed and reopened, it reopened to the size given for the 'Left Panel Width'. This has been corrected. _______________________________________________________________________________________________________

Enhanced integer rounding options available in repeating grids

SR-119683           ISSUE:  177507

While the engine supports all integer rounding options, those options were not fully available in repeat grids where one row has the pxInteger control. An enhancement has been added to support all available rounding options in this control. _______________________________________________________________________________________________________

Smoothed Report Definition handling for missing or incorrect ObjClass

SR-119725           ISSUE:  176399

In some situations, a Null Pointer Exception was being generated after a call to a report definition on the Report Content Page. This occurred when given a target results page with a missing or incorrect pxObjClass. The code has been modified to generate the error "Invalid Report Content Page" instead of the NPE if the ObjClass is incorrect, or to complete the processing if the ObjClass is empty. _______________________________________________________________________________________________________

Corrected copying pages containing autopopulated properties

SR-119803           ISSUE:  171111 / 174193 / 175017

When the clipboard viewer copied a page from a given thread to its own thread to show it in the clipboard, an exception was generated if the page being copied contained an autopopulate property. To remedy this, autopopulate and reference property functionality have been changed to allow copying when declarative processing is disabled in a thread. _______________________________________________________________________________________________________

Adjusted code to prevent double-localization when using Chrome

SR-119858           ISSUE:  175151

When utilizing a locale that uses commas instead of points to demarcate decimals in numbers, editing any numbers in a skin caused extra zeros to be added to the numbers. When using Chrome, if an input type is a number, Chrome by default will localize. The control is also localizing the value after reload, so localization is happening twice. In order to resolve this, If the input type is text, only control localization will happen. _______________________________________________________________________________________________________

Access Role Editor link errors fixed

SR-119869           ISSUE:  176176
When using Internet Explorer 11 or Chrome, clicking the hyperlink to a privilege associated with a class in Access Role Editor created issues that prevented changes from being made or saved. In some cases, after clicking 'Remove Checked' in the popup dialog, the developer portal loaded in the popup. This was caused by the forms-based role selection not being converted for cross-browser support, and has been fixed. _______________________________________________________________________________________________________

Fixed page toggle when a grid contains an error

SR-119909           ISSUE:  176760

It was not possible to navigate to a different page in a grid when a validation error existed on any page. The error could be corrected if it occurred on the current page and paging ability would return, but if the error as in a different page it was not possible to navigate to correct it. This was traced to code which prevented moving to another page if there was an error on refresh. While there was a workaround, the code has been updated to allow moving to another page unless the error occurs on the current step page. _______________________________________________________________________________________________________

Smoothed handling of dynamic select with refresh section

SR-119926           ISSUE:  177335
In the course of server-side prep of the list for a Dynamic Select (via a long running activity wrapped up with a per interaction refreshing Declare page), the Refresh Section event is getting fired. This caused the properties bound to Dynamic Select controls (either in read-only or editable modes) to lose their values. This was resolved by modifying the dynamic select code to load the dynamic select values and set default value upon refresh action (even in case of read-only). _______________________________________________________________________________________________________

DateTime control logic improved for repeating grids

SR-119989           ISSUE:  176616

If a repeat grid was configured with the pxDateTime control for one of the columns, clicking the 'calendar' icon for the first time would not show the calendar. Thereafter, the calendar would appear on icon click. This was found to be an error in the JavaScript logic where the DatePicker function was returning false even if the event was from the DatePicker control. This has been corrected. _______________________________________________________________________________________________________

Lock msg "currently being modified by" now localized

SR-120181           ISSUE:  177028

An enhancement has been added to make the lock screen message "<wo> is currently being modified by <user>" available for localization. _______________________________________________________________________________________________________

Resolved deleting rows where the InsKey contains spaces

SR-120217           ISSUE:  177095

Deleting rows from a Data Table was not working in Chrome or Firefox when using the associated DataTableClassEditor list view for the Data Table. Clicking the delete icon calls JavaScript to retrieve the InsKey of the row to be deleted, but if the InsKey had a space it was being encoded as "&nbsp;" and then did not match the passed InsKey to determine the row to be deleted. In order to prevent this problem, the JavaScript has been updated to correctly handle the space character. _______________________________________________________________________________________________________

CPU efficiency improved for SmartInfo popup

SR-120321           ISSUE:  176135

In order to maintain a low demand on the CPU, the smartinfo popup has been modified to not maintain itself in a ready state. _______________________________________________________________________________________________________

GetNextWork Tab title 'Next" now localized

SR-120505           ISSUE:  177090

On performing GetNextWork in CaseManager Portal, the label 'Next' is displayed as the Tab title temporarily before opening the work object. This label has now been made available for localization. _______________________________________________________________________________________________________

RedirectAndRun' enhanced to better handle thread passivation

SR-120561           ISSUE:  176643

Activity 'RedirectAndRun' is used to run processing on an existing thread page. If the target thread is passivated, it could not be found in the requestor's list of threads and a new thread was created which did not have the original thread context. The handling has been updated to load the existing passivated thread from the database so context is not lost. _______________________________________________________________________________________________________

Resolved work flow issues with scheduled tasks and reports

SR-121151           ISSUE:  177794

Several issues with the scheduled tasks landing page and updating scheduled reports have been resolved. If a scheduled report was reopened and then immediately deleted, all scheduled reports were being deleted instead of only the one being updated. Clicking Submit or Delete after selecting an item on the worklist also deleted all scheduled reports. This was caused by the work object being corrupted by the subsequent action happening before the object was fully processed for opening, and the system will now ensure the object is fully opened before the next action is executed. Also, clicking the Reopen button and then dismissing it by clicking the X without clicking Submit or Cancel or Delete caused the item to be put on the worklist. The reopen button will reschedule the report and move the operator to the review harness rather than perform so that extra assignments are not scheduled. _______________________________________________________________________________________________________

Clear and actionable guardrails help you mitigate risk sooner

The Application Guardrails landing page has been restructured to give you an executive-level view into your application health. Use the available metrics and tools on each tab to understand the scope of warnings in your application, the operators responsible for introducing this risk, and ways to improve your compliance score before your development goes into production.

Include this landing page in your governance process to:

• Understand your application compliance score and how it has changed over time:

  • A score of 90 or greater indicates your application is in good standing.

  • A score of 80-89 indicates your application needs review for improvement.

  • A score below 80 requires immediate action.

• Investigate the factors contributing to your score, such as warning age or severity, and the rules and operators associated with each warning.
• Review a comprehensive list of warnings and the recommended path to resolve them.
• Communicate all of these details to project stakeholders through email or exported documents.

​

Available metrics on the Compliance Details tab of the Application Guardrails landing page

The Charts tab in this landing page has been superseded by the Compliance Details tab, which provides more options and an enhanced presentation.

For more information about the available features on all tabs in this landing page, see Application Guardrails landing page.

Rollback functionality is limited to latest revision

The rollback functionality in DSM Revision Manager allows customers to roll back the import of the latest revision to their DSM application. Only one rollback is allowed; after a rollback, the rollback option is disabled until the next revision is imported. If importing two (or more) revisions at once then attempting a rollback, the system only rolls back one revision.

Example: a user has a base DSM application. They import Revision 1, and then import Revision 2. Next, they try to roll back both revisions. The system reverts to the Revision 1 version of the application, and the customer cannot revert all the way back to the base application.