Number and text input controls on Android devices may not display the correct keyboard
Valid from Pega Version 7.1.8
When running a Pega 7 application on a device using the Android operating system, pxNumber and pxTextInput controls may not display when using the desired on-screen keyboard. This happens when the number or text input type is set to number.
At design time, the input type is selected in the Editable Format section of the Presentation tab in the Cell Properties panel for a pxNumber or pxTextInput control. Due to a known limitation in some versions of the Android OS running on some devices, the keyboard displayed at run time may not support entry of decimal values when a Number type keyboard is specified.
To resolve this issue, use the Phone type when numbers with decimal values may be required. Using the Phone type displays a numerical phone keyboard. The Android phone keyboard includes both commas and periods so that decimals may be entered.
The Phone type selected in the Presentation tab of a Number control
Note that this issue only occurs on Android devices. It is recommended that applications for iOS continue to use type=“Number”.
Split schema upgrade instructions missing properties
Valid from Pega Version 7.1.3
If you upgraded from 5.x, 6.x, or 7.x using the instructions in previous versions of the upgrade guide, you may have neglected to set the properties below in your migrateSystem.properties file when you migrated your upgraded schema to the source system:
pega.rules.objects.generate=true
pega.rules.objects.apply=true
If these properties were not set during an upgrade that splits the schema, your environment does not have the indexes, triggers, and primary keys on the rules tables.
To check for this issue, see if the pr4_base and pr4_rule rules tables in your existing rules schema are missing primary keys. If they are, use the SQL scripts in the ResourceKit\MigrationRecoveryScripts directory of the release to cleanup duplicate rules that were created due to this issue. Follow the steps below to run the scripts.
To run the scripts on Microsoft SQL, Oracle, or PostgreSLQ
- Take down any app servers using the affected schema.
- Backup your database.
- Replace all instances of @RULES_SCHEMA in <database>_cleanDups.sql with the name of the schema that contains the pr4_base table.
- Run the <database>_cleanDups.sql script on the database with vendor tools (sqlPlus, SQL Server Management Studio, etc).
- Replace all instances of @RULES_SCHEMA in <database>_fix_vw_table.sql with the name of the schema that contains the pr4_base table.
- Run the <database>_fix_vw_table.sql script on the database with vendor tools (sqlPlus, SQL Server Management Studio, etc).
- Generate and apply the ddl using the command line generateDDL command. Check the installation guide for your database or the upgrade guide for details about how to use the generateDDL command line script.
- Rebuild the indexes for the tables in your rules schema using vendor tools. This is necessary so that your system runs at an optimum speed.
- Optionally upgrade to the latest release, at this point your database is ready to be upgraded or used depending on your needs.
To run the scripts on DB2 for LUW or z/OS
- Take down any app servers using the affected schema.
- Backup your database.
- Run the <database>_cleanDups.sql script on the database with vendor tools (UDB CLP, Data Studio, etc) to create the CLEANSE_RULES_DUPS stored procedure.
- Run the query Call CLEANSE_RULES_DUPS(‘<rulesSchema>’); where <rulesSchema> is the name of schema that contains the pr4_base table.
- After the previous step is complete drop the CLEANSE_RULES_DUPS procedure.
- Replace all instances of @RULES_SCHEMA in <database>_fix_vw_table.sql with the name of the schema that contains the pr4_base table.
- Run the <database>_fix_vw_table.sql script on the database with vendor tools (UDB CLP, Data Studio, etc).
- Generate and apply the ddl using the command line generateDDL command. Check the installation guide for your database or the upgrade guide for details about how to use the generateDDL command line script.
- Rebuild the indexes for the tables in your rules schema using vendor tools. This is necessary so that your system runs at an optimum speed.
- Optionally upgrade to the latest release. At this point your database is ready to be upgraded or used depending on your needs.
Resolved Issues
Issue: 135287 SR-96116
After using the 'Edit in Word' feature on the body of an email, single quotes (‘), double quotes (“) or similar characters appeared as “junk” characters in instances of Outlook set to use Western European (Windows) encoding. It was possible to work around this issue by changing the encoding format to UTF-8, but PRPC has been updated to also handle the Western European setting.
_________________________________________________________________________________________________________
Issue: 135441 SR-96445
When using a Modal Screen Flow with IAC, the modal flow displayed properly, but processing did not correctly update the parent thread when finishing the flow and the base thread ended up no longer having a proper pyWorkPage clipboard page. This problem existed only with IAC where thread names contain the application name as well, and a change has been made to handle the additional data so flows will now finish correctly in IAC.
_________________________________________________________________________________________________________
Issue: 136276 SR-103324
During the install of the RAP files, PRPC 7.1 upgrades all declare pages to data pages. An input parameter was not correctly copied to new data pages, preventing certain activities from correctly loading the pages. Migrated declarative pages now have the needed input parameter automatically defined for the new data pages.
_________________________________________________________________________________________________________
Issue: 137264 SR-102313
Chinese characters in a pyEmailBody being attached to a workobject were not displaying properly due to a mismatch in the settings of the sending and receiving versions of Outlook. The Outlook advanced properties in the Email Listener have been changed to use Chinese Traditional(Big5) encoding to enhance compatibility.
_________________________________________________________________________________________________________
Issue: 137646 SR-103158
When mapping properties to an external database table, the properties created with the data class were created with the appropriate property type. However, any properties which were mapped after the data class is instantiated were all created of type text, irrespective of the actual property type. Properties mapped after the class is instantiated will now be created with the same type as the original property.
_________________________________________________________________________________________________________
Issue: 138178 SR-103774
Dates on messages shared in Pega Social were previously encoded to use only the 'mm-dd-yyyy' format. This format is now set as the default, and other date formats may be set in the new field value "PegaPulseDateFormat" (example: 'dd-mm-yyyy' format).
_________________________________________________________________________________________________________
Issue: 138713
Several processes were tuned and new variables were added to improve system performance:
1) pxSystemFlow was removed from the GetNextWork query; it was added in 7.1 to filter out system flows like OverallSLA up front, but as that property didn’t exist before 7.1, customers upgrading from an earlier version were having difficulty having their old assignments picked.
2) Using an urgency threshold now alters the filter criteria, creating a significant performance improvement for a large workbasket table by dramatically lowering the result set. For example, given an urgency threshold of 96, a workbasket containing 100,000 rows evenly distributed along the 0 to 100 urgency spectrum will now be checked only for assignments with urgency 96 to 100. In the above example, this would have a result set of 5,000 rows instead of 100,000.
3) An Oracle optimization was added to allow the use of indices instead of table scans. To utilize this, (a) turn on system setting pyGetNextWork_UseAdditionalIndexGetContent and (b) create a function index for nvl on the table.
4) An option has been added to skip skill checks if your application does not use them. This enhances performance by removing a heavy operation from the query if it is not needed. When skill checks are used, the process has been streamlined to improve speed.
_________________________________________________________________________________________________________
Issue: 138739 SR-103462
When importing XML Schema Definitions (XSD) containing element and type substitutions, some rules were created in draft mode for the element substitutions due to the type map being added more than once. This caused compile errors. The map variable is now cleared.
_________________________________________________________________________________________________________
Issue: 138773 SR-103350
When creating a report definition SQL query in a repeating grid layout with paging enabled, some special characters used as search strings were being converted to HTML charcodes on the second and subsequent pages of the results, leaving those pages blank because the search string wasn't correctly matched. The query has been fixed to correctly handle characters such as “&”, "(", or ")" as search parameters.
_________________________________________________________________________________________________________
Issue: 139521 SR-102942
When using POP3 to handle email, malformed recipient addresses such as Owner"<[email protected] would cause a runtime address exception leading to a loop where mail was not being processed successfully. Code has been added to enable PRPC’s third-party library (JavaMail) to catch the exception and attempt to retrieve a valid mail ID from the existing invalid ID (removing quotes or other special characters), and then use this ID in the message header for further processing. This looping behavior was not an issue for sites using IMAP.
_________________________________________________________________________________________________________
Issue: 140668 SR-104824
In the Case Manager portal, work baskets are now displayed with the more easily-readable short description instead of the rule name.
_________________________________________________________________________________________________________
Issue: 141031 SR-105062
When using the MQ listener configuration, the PRPC engine was not properly implementing the Backout Requeue feature of the Global Resource Settings. This has been corrected.
_________________________________________________________________________________________________________
Issue: 141280 SR-104550
When using non-auto-gen section includes in inline dynamic layouts, the subsequent sibling elements of the layout are included as children of the non-auto-gen section. When the user enters an advanced parameter for non-autogenerated sections, PRPC was generating a malformed HTML fragment. This has been fixed.
_________________________________________________________________________________________________________
Issue: 141913 SR-104637
Every time a customer application called a SOAP connector, customers were seeing 4 jar files, generated by our third-party tool Axis2, generated into the axis2-tmp-number.tmp file. The following files would be generated:
-- axis2numberpraddressing-1.5.4.jar
-- axis2numberpraxis2-1.5.4.jar
-- axis2numberprrahas-module-1.5.1.jar
-- axis2numberprrampart-module-1.5.1.jar
where number is a 19-digit integer (“1082024463755692860”)
Overall, this issue was addressed in earlier releases by modifying the activity that invokes Axis2; but one use case, where the customer uses WS-TRUST connectors, was not handled. The resolution code has now been moved to a more central location in Axis2 so that all use cases are covered.
_________________________________________________________________________________________________________
Issue: 142572 SR-105889
A BIX issue caused the error “Unable to Create Rule-Obj-XML Rule” when trying to create other XML rules in PRPC. The work around was to checkout pyUserData property in Pega-BIX ruleset and set the class name as $ANY, but the issue has been resolved in this release by regenerating the BIX distribution image.
_________________________________________________________________________________________________________
Issue: 142573 SR-104929
The process ForceCaseClose is used to resolve a Work Item and its child cases and delete all assignments. This process used the WorkObjectID and assumed there was only one class group. This behavior has been refined to use the object key of the Work Item, allowing for cases where there is more than one work pool associated with an access group and the work item is not from the default work pool.
_________________________________________________________________________________________________________
Issue: 143106 SR-105419
Although the reindexing process was working correctly, the search monitoring agent in UNIX and Linux environments showed the following error: “Line 553: 2014-02-07 10:44:02,827 [fault (self-tuning)'] [ STANDARD] [ ] [ PegaRULES:07.10] (ch.internal.LuceneSearchEngine) INFO - Index Directory does not exist. Click Re-index rule to create index files”. This resulted from the system environment being case-sensitive, and the false errors have been eliminated by the checking for “dataIndex” instead of “DataIndex”.
_________________________________________________________________________________________________________
Issue: 143201 SR-105333
When submitting a case-wide supporting process that was defined in the 'Other Actions' → 'Add Work' menu on the perform harness, a “Reconcile inconsistency in stage processing" error was generated. This was caused by the case-wide flow incorrectly being marked as a stage flow. If this occurs, an automatic stage transition will not happen if the case-wide flow is still open. Case-wide optional processes are now considered stage processes if the case type has stages.
_________________________________________________________________________________________________________
Issue: 143271 SR-106062
After using spellchecker on a textArea property, attempting to use the spellchecker again after section refresh caused the javascript error “Object Required” due to the hidden elements is no longer being accessible in the SPELLCHECKERSCRIPTINCLUDE HTML fragment. This has been remedied.
_________________________________________________________________________________________________________
Issue: 143284 SR-105020
When data pages were used to populate a page list, the references of the data page did not appear in the Referencing Rules display (Actions → View references). The class information is now retrieved from the data page definition and displayed as expected. Note: For pre-existing properties, the property rule must be re-saved to incorporate this correction.
_________________________________________________________________________________________________________
Issue: 143419 SR-106044
In a section, after changing a label to a link control and saving the section, the following error was displayed: “This record has2 errors; Cells in a Row: ** "(caption)" is not a valid property String value of a cell: (caption) does not exist for use by this record (Validate).” Changing the control triggered a refresh of the section, and the property panel changed to show the one corresponding to the new control. It retained the value which was given for the label field and tried to copy the same value to the property reference field of the new control (Link in this case), even when that property didn’t exist. This has been changed to clear the value when switching to a link control, eliminating the error.
_________________________________________________________________________________________________________
Issue: 143483 SR-105590
When using the DateTime-Calendar Control in the Accessibility framework, submitting an input form with an invalid or incomplete Date and missing mandatory fields could cause the date fields to be randomly changed. To remedy this, the init method has been modified to perform a check on the Date object if any invalid date string is provided.
_________________________________________________________________________________________________________
Issue: 143730 SR-103883
When exposing columns in a database, there was discrepancy between source and target date fields. A PRPC property of type 'Date' maps to a VARCHAR in both a SQL Server and an Oracle database. However, a PRPC property of type 'DateTime' maps to DATETIME in SQL Server, and DATE in Oracle. For BIX DDL generation, 'Date' properties are now mapped to VARCHAR to resolve this discrepancy.
_________________________________________________________________________________________________________
Issue: 143749 SR-106285
While adding an annotation shape to a flow outside of a swim lane and then bringing it into the swim lane worked as expected, adding annotation shapes directly into the swim lane caused flow save failures. This was due to it being handled as a shape instead of an annotation, and a check has been added to correctly handle shapes added directly to the swim lane.
_________________________________________________________________________________________________________
Issue: 143971 SR-106167
Saving a rule without errors had no indication that the save was successful. Additionally, the loading icon disappeared briefly before the section was refreshed to add error messages and markers to the ruleform. Progress is now indicated with a "Save" icon that will gray out once the item has successfully saved and remain grayed out until the item has been updated/changed in some way, at which time it will return to full color.
_________________________________________________________________________________________________________
Issue: 143993 SR-106531
The control DisplayYesNo, which displays a Radio button with values of Yes and No for a true/false property, has been updated to allow language localization.
_________________________________________________________________________________________________________
Issue: 144205 SR-103943
Since PRPC version 6.1, custom jar files can be uploaded into the PegaRULES database, instead of using the Dynamic System Setting “compile/defaultPaths.” However, some customers wish to use this setting, and when they tried, they got an error stating “Error: myclassname cannot be resolved to a type.” Code has been added so that custom jar files may be specified in the Dynamic System Settings as well as loaded to the system.
_________________________________________________________________________________________________________
Issue: 144256 SR-106113
It was possible for the BIX 'Extract for History' query to miss some records when processing under the time dependency 'use last update as start'. The filter operation has been changed from > (greater-than) to >= (greater-than AND equal-to) in the query formation in order to include all of the relevant records.
_________________________________________________________________________________________________________
Issue: 144264 SR-105492
When a security privilege is not present for an operator, the operator running a report received the error "Errors.pyReportDefinition.pyContent: ** No access permission for the report." The error text was previously hard-coded, but may now be localized as desired by using 'FieldLabel'.
_________________________________________________________________________________________________________
Issue: 144381 SR-106916
The ReplyToQueue value in the JMS Header was not being mapped in the JMS Service request message headers field due to a flaw that caused the value to be skipped when mapping it to the clipboard. This has been corrected.
_________________________________________________________________________________________________________
Issue: 144449 SR-103309
When using an abstract class to define the structure of a Report Definition search criteria, flows may contain a temporary work object to display the report definition. However, if the the underlying report page is passivated and some of the properties used in the report contain empty values, then those property names were not properly restored to the clipboard when the page was reactivated. An error such as “SearchCriteria.MyEmptyProperty page not present in clipboard” is displayed. Blank properties were generally not passivated or restored, so the system has been changed to handle blank properties if desired. As part of this fix, a new prconfig setting called passivation/passivateBlank has been introduced. If it is set to true, then blank properties will be passivated. The default is false.
_________________________________________________________________________________________________________
Issue: 144501 SR-106307
After creating a concrete class with “Find name first (Pattern)” unchecked, the newly created class was not found in the Application Explorer tree structure unless the class was manually changed. A Directed Inheritance enhancement has been added to provide the class automatically.
_________________________________________________________________________________________________________
Issue: 144504 SR-106698
Following migration of Summary View Reports from Pega 5.4 to 6.3 to 7.1, the Back button became disabled and the Tips hyperlink was missing. These were traced to changes made in the Pega final rules 'SpaceTitleBar' and 'Wizard_Parameters'. These changes are deliberate and will not be reverted.
_________________________________________________________________________________________________________
Issue: 144506 SR-104986
When viewing a large list of properties in the App viewer, a page property can be expanded to show all of the properties using the “Show all results...” option at the bottom of the list. If the data class was abstract, the “Show all results ...” option would generate the error “Class @baseclass is not a concrete class“ and not display properly. This has been corrected.
_________________________________________________________________________________________________________
Issue: 144533 SR-106847
The type 'DateTime' was not shown in the Data Type dropdown for defining parameters on the Activity Parameter tab. This was a problem in the DataTransform rule where the entry labeled "Date" was under the covers "DateTime and the type "Date" was missing. This has been fixed.
_________________________________________________________________________________________________________
Issue: 144537 SR-107061
When upgrading from Pega 7.1.3 to Pega 7.1.4, the process would exit with the error:
“Caused by: com.pega.pegarules.pub.PRRuntimeException: Unable to identify default schema for the connection to FCMR”.
This was caused by mapping a class to a custom Data-Admin-DB-Name for which the configuration is missing in the new instance. As in In other cases where the system is unable to get the necessary information for migrating instances (e.g. finding a BadClassDefinition), now a warning will be issued and the process will continue.
_________________________________________________________________________________________________________
Issue: 144568 SR-106635
When setting a SLA to run at a specific hour of the day using a 24-hour clock, for example 23:00 (11pm), the Agent rule would not save due to the local list on the pyStartHour rule validating against a local list only containing the values for 12-hour clock. PyStartHour has now been amended to support the 24 hour clock that the SLA Agent runs on.
_________________________________________________________________________________________________________
Issue: 144641 SR-107108
When using IE8, users were unable to add Rule-Obj-Validate conditions – a 403 error displayed in Internet Explorer. The same validate rule worked properly in IE 9, or the Chrome or Firefox browser. Rule-Obj-Validate has been fixed to work in IE8.
_________________________________________________________________________________________________________
Issue: 144655 SR-105910
Urgency and Due Dates background colors on the Worklist/workbasket views were not updating correctly when the due date was manually updated. The issue has been fixed by updating the function in the 'when' rule to consider the date-time when checking for deadline timestamp.
_________________________________________________________________________________________________________
Issue: 144800 SR-105102
After migrating application from 6.3 sp1 to 7.1.3, Field Values created under @baseclass level were getting picked up, but Field Values defined under Work class level were not. This was traced to an error where @baseclass had been hard coded. The code has been changed and defining Field Values under work class now works as expected.
_________________________________________________________________________________________________________
Issue: 144856 SR-106055
When drilling down into a Detailed View of a Summary report, the javascript error “com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference .ID is not valid” would appear. This was caused by an error in the option “use lightweight list” on the Summary Report, an feature that was set 'on' by default. Customers were able to work around the error by unclicking the option, but the code has been changed to properly allow drill-downs in combination with “use lightweight list”.
_________________________________________________________________________________________________________
Issue: 144941 SR-105811
The 'On exception, jump to later step label' value on an Activity transition was not being validated, making it possible to enter a label that does not exist and successfully save the Activity. This has been corrected.
_________________________________________________________________________________________________________
Issue: 144959 SR-106254
If a a report definition was created with empty/blank values, the legend name in the chart was empty. The code for generating charts has been adjusted to better handle null values in a report.
_________________________________________________________________________________________________________
Issue: 145034 SR-106087
The developer portal makes a REST Connector call to the PDN in order to display an RSS feed of developer tips. These calls to an external system in production may not be allowed in a local environment, causing the application to fail a customer's internal audits. The calls could be suppressed by creating a custom portal without the sidebar, but this release includes the dynamic admin system setting “AllowAccessToExternalSystem” whose default value is true. Setting this value to “false” will disable calls to PDN RSS feed.
_________________________________________________________________________________________________________
Issue: 145084 SR-106318
When moving the mouse over the magnifying glass icons in activities (located to the right of the method input box), the cursor changes to the "move" cursor instead of the "pointer" cursor. The control had a style specified that was working differently in IE and Chrome browsers. An additional style was added to the rules so that the “pointer” cursor will display.
_________________________________________________________________________________________________________
Issue: 145104 SR-102406
Property trees were not returning all the properties from the upper classes of the class hierarchy when “Include Inherited Property” option was selected. It was possible to see all properties from upper classes when doing a direct query on those classes; however, those classes weren't showing when queried from a class lower in the hierarchy. This was solved by increasing the property tree size so that more properties can be handled.
_________________________________________________________________________________________________________
Issue: 145110 SR-107187
Avaya has a requirement that the SOAP service being called by Avaya needs to use a different soapAction than the one defined in the WSDL soap:operation element that PRPC generates to determine the package, class, and activity. The format conflict caused the error “SOAPAction URI value has invalid format”. PRPC now provides the ability to successfully invoke a SOAP service without using the SOAPAction HTTP header value specified by the generated service WSDL. If the SOAPAction header is not present, or does not conform to the pattern specified in the service WSDL, the service rule package and class keys will be derived from the URL path info of the SOAP target URL. The service method key will be derived from the element name of the first child element of the SOAP Body element.
One thing to note, when using document literal SOAP services, the name of the first child element of the SOAP Body element will not necessarily be the same as the SOAP service method name. There are two ways to fix this:
1. Do a Save As of the SOAP service rule so that the service rule method name and the name of the root element of the XML stream rule used in the SOAP Body are the same.
2. Append the service method key to the URL path of the SOAP endpoint. The format of the endpoint URL would be something like this: http://myservicehost:8080/SOAP/MyServicePackage/MyServiceCLass/MyServiceMethod"
_________________________________________________________________________________________________________
Issue: 145135 SR-106425
It was not possible to manually configure Editable options (read only 'When" or expression) while a property is marked as 'required'. This was not an optimal work flow, and has been changed to allow the simultaneous configuration of Required and Readonly (when /expression).
_________________________________________________________________________________________________________
Issue: 145141 SR-106351
In the Case Manager portal, right-clicking to open a modal dialog creates a separate thread. This thread should be cleaned up once the modal dialog was closed, but it persisted even after a refresh. A check has been added in the API to invoke removeThead activity and remove the stale thread.
_________________________________________________________________________________________________________
Issue: 145184 SR-106800
Attempting to lock a ruleset after checking in/out a rule was not working correctly unless the ruleset form was refreshed. The "Lock and Save" function was relying upon stale data for validation, and has been corrected.
_________________________________________________________________________________________________________
Issue: 145227 SR-106577
When using the pyWeeklyThroughput report definition, the columns for "Previous" and "New" were displaying identical values. This was caused by the report definition 'pyWeeklyThroughput' being incorrectly converted from Summary view 'pyWeeklyThroughpuIC', and has been fixed.
_________________________________________________________________________________________________________
Issue: 145239 SR-105797
When the 'select all' check box was used in a header, all items were properly selected. However, when one of the individual boxes was then deselected, the 'select all' box above remained checked. This area was missing a function to uncheck the 'all' box if any of the rows below are deselected, and the proper click handler has been inserted.
_________________________________________________________________________________________________________
Issue: 145272 SR-106631
After configuring and deploying a Data-Admin-License record, the pr_usage_daily table was not being updated and the pr_hourly_usage table was not being purged. This has been addressed with schema changes specific to MS SQL databases.
_________________________________________________________________________________________________________
Issue: 145305 SR-106672
SmartInfo popups on the user worklist were being truncated when using old fixed portals (e.g. WorkManager) while generating the javascript errors “invalid argument” and “nextslibin”. The Smartinfo pop over was not correctly calculating the available space and display in available directions (left/right/top/bottom/middle), causing it to be contained within the iFrame displaying the work list. This has been adjusted to display properly.
_________________________________________________________________________________________________________
Issue: 145455 SR-107648
Previous versions of PRPC allowed the use of empty elements for date types. PRPC now follows the XML spec disallowing the empty values, and this strict handling caused XML parsing to fail when the XML stream contained older records with invalid dateTime values. The error included “javalang.IllegalArgumentException: '2014-03-20 01:05:44:119562Z' is not a valid lexical representation” “. To ease the transition for customers, PRPC is now using the JAXB DatatypeConverter API for all XSD date/dateTime/time conversions, and will return null values for blank input. If the source XML contains any invalid XSD date, dateTime, or time values, they will be mapped to the clipboard as-is, with no format conversion. A warning message will be added to the log for each invalid value.
_________________________________________________________________________________________________________
Issue: 145487 SR-105977
Associating Actions with the standard Checkbox control was producing inconsistent behavior ranging from alert boxes to failure to execute. PRPC had been restricting the propagation of events in the ui_events.js click handler by checking against event.detail to avoid double click, but this encountered a bug in IE9+ browsers where the event.details flag is not set appropriately. We had adjusted the click handler for IE9+ browsers to not check against event.details to prevent this problem.
_________________________________________________________________________________________________________
Issue: 145534 SR-106890
When previewing an activity, errors were shown in Tracer and the log file. This occurred for multiple activities; one example is “Embed-ListParams – getContentAndSuites”.
2014-03-10 09:13:49,673 [ http-6311-4] [ Developer] [test:01.01.01] ( internal.access.RuleResolver) ERROR - Trying to open rule "PYRECURRENCETYPE" of class "Rule-Obj-Property", but the defined-on class "$CLASS" is invalid
2014-03-10 09:13:49,673 [ http-6311-4] [ Developer] [test:01.01.01] (ules.generated.pega_wb_default) ERROR - AP_CreateAnchorForProperty
com.pega.pegarules.pub.database.BadClassDefinitionException: Attempting to access a rule with a bad defined-on class: $CLASS.
Code was added to check for null values, and these errors no longer occur.
_________________________________________________________________________________________________________
Issue: 145541 SR-106778
When claiming a task on Home tab of Designer Studio, the "Owned by" field was displaying pyLabel (the Short Description of the Operator ID record) instead of pyUserName. This has been fixed.
_________________________________________________________________________________________________________
Issue: 145542 SR-106310
When using a "Call XXXX" method with a required parameter missing from the method parameters, the description field of the step wraps below the step at save time. If the step is commented out with // on the label, the description moves back up. IE8-specific code was added to remove spaces at the beginning of the description field, so the value shows correctly when using that browser.
_________________________________________________________________________________________________________
Issue: 145814 SR-107391
A javascript error was being generated when attempting to open an assignment from the Federated Worklist while using IE8. This was traced to an API used to focus the active tab. In this release, the API line which focuses the active tab within a try-catch block now wraps to avoid the JS error in IE8.
_________________________________________________________________________________________________________
Issue: 145857 SR-106064
When selecting a page on the clipboard standard viewer and using Edit –> Add, a popup window opens and displays a smart prompt of available values. Previously, only values present in baseclass were shown. The logic has been added to additionally include properties picking from the current 'applies to' class.
_________________________________________________________________________________________________________
Issue: 145943 SR-107433
When two product rules and an access group were open simultaneously and a hotkey was then invoked for functions such as 'open XML', 'Clipboard', 'Run', and 'Save', IE8 generated the javascript error “Message: Object doesn't support this property or method”. A new IE8-specific version of the hotkey implementation has been added to enable this function.
_________________________________________________________________________________________________________
Issue: 145984 SR-106308
When viewing @baseclass, a duplicate class was listed in Application Explorer. The Explorer rule was updated to check for and remove class duplicates added from the workpool list.
_________________________________________________________________________________________________________
Issue: 146053 SR-107649
When displaying a remote assignment via an FCMgadget, the ResizeFCMGadget JavaScript function was called continually. This has now been fixed, and it is possible to scroll down the screen and view the assignment.
_________________________________________________________________________________________________________
Issue: 146063 SR-106744
If 'property definition' doesn't contain a property, a null pointer error was generated when making a Twitter API call. The error was caused by an unhandled null check in Rule-Connect-REST.pyInvokeRESTConnector activity. A null check for property definition lookup has been added, enabling the JSON array to map to virtual property.
_________________________________________________________________________________________________________
Issue: 146064 SR-106639
When pick a value icon runs a background query to get the list of valid values for a column which has a very large number of rows, the execution was taking an excessive amount of time. Duplicate activity population logic has been removed to improve performance.
_________________________________________________________________________________________________________
Issue: 146134 SR-104724
The merging of Branch Rulesets from Refactor Ruleset (”Pega button -> System -> Tools -> Refactor Rulesets -> Copy/Merge RuleSet”) is not a supported option. The "Refactor Ruleset" wizard is used only for merging of individual rulesets and not for merging branch rulesets. This is by design. To merge branch rulesets, the “Merge Branch Ruleset Wizard” must be used. In order to clarify this, the "Refactor Ruleset" merge utility has been updated to eliminate branch rulesets from the list of available rulesets. An enhancement has also been made to the “Merge Branch Ruleset Wizard” to include features from the "Refactor Ruleset" merge utility (e.g. merging multiple branches at once, rollback, etc.).
_________________________________________________________________________________________________________
Issue: 146155 SR-106309
When typing in the name of a method in a new step in an activity with a very large number of steps, there was high latency between what was being typed and what was rendering on the browser. This was found to be an issue with checks performed by SmartPrompt, and the SmartPrompt attributes have been modified to only update when the method filter is changed, rather than on every key up.
_________________________________________________________________________________________________________
Issue: 146252 SR-103516
On Running the search for work report from manager portal and passing status and create date time values (using criteria greater than or equal), a 403 forbidden error was generated: "Due to the presence of characters known to be used in Cross Site Scripting attacks, access is forbidden. This web site does not allow Urls which might include embedded HTML tags.". On further analysis of the issue it was found that the url formed for the list view contains character %3E (WorkCondition=%3E%3D) which is being blocked by siteminder CSSChecking. To fix this, special characters like "<" and ">" will be changed to the English expressions "LessThan" and "GreaterThan".
_________________________________________________________________________________________________________
Issue: 146257 SR-107017
If a section referring to another page was included and configured using a visible 'when' condition with “Run on Client” mode enabled, the 'when' condition was evaluated using the context of the included section, leading to sections not being displayed even when the condition is true. A new property has been added to correctly evaluate the visibility condition.
_________________________________________________________________________________________________________
Issue: 146269 SR-104739
When Email Listener processed a message with Chinese characters for attachment to the workobject, the Chinese characters were getting changed. This occurred when the original character set was GB2312, and Email Listener has been modified to handle this character set to correct this problem.
_________________________________________________________________________________________________________
Issue: 146321 SR-107249
A pre-existing parse rule that mapped values to a page list became corrupted after migrating it to the 7.1.3 environment. This was shown when an application was created defining RulesetA(RulesetB as a prereq) and RulesetB; then a property was defined in RulesetB; then a parse rule was defined in RulesetA to be parsed into RulesetB. Then RusesetB was removed from the application stack and the parse rule was resaved. At runtime, this created an empty page or had no properties set, and generated the unusual error message “pyMappedValueProperty: ** P``````````” . This corrupted rule has been corrected.
_________________________________________________________________________________________________________
Issue: 146344 SR-106338
In a particular use case the dynamic select values weren't being populated even though they has worked correctly in PRPC 6 + .The cause was traced to a javascript error in the tab support, and the system has been changed to check for an undefined lastTab variable and return if it is undefined.
_________________________________________________________________________________________________________
Issue: 146401 SR-107164
When launching a portal and turning on the UI Inspector, highlighting a section (example: pyPortalLogo, CPMPortalLogo) in the portal header caused UI Inspector to render the section as a property and fail to open the section rule in the developer portal. Searches for rules with this name returned an empty list. In this instance, the UI Inspector was unable to differentiate whether it was a property or a section rule and wrongly displayed the information. This was an issue only for sections included in Dynamic Layout and there was a work around of using free form layout. The issue has been resolved.
_________________________________________________________________________________________________________
Issue: 146571 SR-106305
When importing Specifications from Excel, if the Short Description (pyLabel) text is larger than 64 bytes (due to it containing unicode characters) but less than 64 characters, the import was failing with the following error appearing the logs: “Caused by SQL Problems. Problem #1, SQLState 72000, Error code 12899: java.sql.SQLException: ORA-12899: value too large for column”.
The error was getting written to the log file, however no error was presented to the user, giving the impression that the import had been successful.
A code change has been made to display a suitable message to the user in the event of this problem occurring. Additionally, this error can be avoided by increasing the size of the underlying database column.
_________________________________________________________________________________________________________
Issue: 146646 SR-106919
When a ListView was run with some parameters defined to be prompted before execution (i.e. having “Prompt user before executing this report” as true in Prompt Settings), only the PDN icon was displayed at the top tight corner even though the list view is defined to show both PDN and HELP icons. This was an issue with the Wizard_MainWindow HTML fragment and has been corrected.
_________________________________________________________________________________________________________
Issue: 146921 SR-107525
There have been changes implemented via UserStory(US-15141-1 ) in 7.1 to support split schema and how connections are handled. There were also changes made in the Connection Management, and many old unused setting were removed ( https://mesh.pega.com/docs/DOC-38091 )
In 7.1, app servers do the connection management rather than Pega handing it, meaning you will not see anything in the Managed Connections table if you are using the Data source. If you are using the previous method of Pega connection pooling, then connections are not passivated and will be shown in the table. Help text has been added in the SMA screen to give better information regarding Managed Connection in DB Details.
_________________________________________________________________________________________________________
Issue: 146992 SR-107945
Branch Merge Wizard was sporadically failing to correctly display errors during failed merges. This was traced to any errors encountered during the Step page not being carried into the Primary page. Specifically, if any of the steps fail, a message is set on the step page, this error is properly handled, and a Rollback is issued. When the activity ends, there may very well be a page message, but it is not visible to the user. Additionally, the activity status is still Success (since the rollback is graceful, and there is no forced failed status set) but the RSV is actually NOT created. This has been fixed, and Step errors in the Merge Wizard are now copied to the Primary page and displayed.
_________________________________________________________________________________________________________
Issue: 147141 SR-104072
The value of the property .pxLinkedClassTo originally contained the name of a class being linked to. The values of this property were displayed as an attachment type in an item. In Version 6, the values of this property were changed to reflect the category type instead of the class, which was not the original intent of the property. The values of this property have been changed back to reflect the name of the class being linked to.
_________________________________________________________________________________________________________
Issue: 147147 SR-107454
In Report Definition under 'rows to include', Field Values were not working for Filtering Caption on Report Definition. The field value localization was corrected in the RRFilters_Logic control.
_________________________________________________________________________________________________________
Issue: 147253 SR-104716
An activity without error handling calling Obj-Open led to a cross-site scripting vulnerability when displaying a harness. This has been fixed.
_________________________________________________________________________________________________________
Issue: 147417 SR-108473
An update to the Spell Check Properties rule "en_US" was made to improve running time.
_________________________________________________________________________________________________________
Issue: 147727 SR-106884
“When” rules referencing properties with very long names on sub-pages were suffering from degraded performance. The regular expression has been modified to improve performance for these highly complicated properties.
_________________________________________________________________________________________________________
Issue: 147746 SR-104540
In BIX, the XSD for simple properties of type date, datetime, decimal, double, integer, timeofday, and Boolean all have the attribute nillable="true", meaning that these properties can be null. However, ValueList and ValueGroup properties of non-string data types did not have this attribute. They have been updated to have the XSD attribute nillable="true".
_________________________________________________________________________________________________________
Issue: 147874 SR-108180
Scheduled report definitions generating emailed PDF reports were displaying enlarged double headings containing buttons. The PDF generation has been corrected to properly display the headings.
_________________________________________________________________________________________________________
Issue: 147909 SR-107729
When a section using a local action is included in the flow action of a list that uses expand-pane editing, the local action failed if it was on an embedded page of the list item. A change has been made to the processActionModal API to ensure that the parameters passed to the process action activity allow for multiple levels of nesting of flow actions/expand-panes.
_________________________________________________________________________________________________________
Issue: 148351 SR-107440
An issue was identified with the latency in retaining the focus on the Save-As button when using PRPC 7.1.4 with IE8. If “Save As” was clicked before the focus was completely retained, the system did not perform any action. However clicking on “Save As” after the focus is completely retained performed the save without any issue. This problem was traced to the DOM query for div.document-statetracker being extremely slow in IE8 Quirks Mode. To correct this problem, the DOM query has been updated; also, the “Save As” button will turn blue when focus is completely retained.
_________________________________________________________________________________________________________
Issue: 148442 SR-104899
Some revalidate and save processes were failing after upgrading unless the rules were open and the save was performed on the rule form. During the revalidate and save process, BULKVALIDATESAVE is called. When a warning was issued, the process treated the warning as a failure and did not complete the save. This behavior has been changed, and if the execution of the step has any warnings, it is marked as an error and the record is saved.
_________________________________________________________________________________________________________
Issue: 148625 SR-107472
Logging has been added for HTTP 500 errors, allowing originate from the server or from within the application, extensive logging in the PegaRULES logs or Server logs will help isolate the issue needing resolution.
_________________________________________________________________________________________________________
Issue: 148646 SR-105529
When attempting to run Declare expressions that were applied to different classes, a java exception error was created. The logic filter for Declare expressions has been changed to place reference class and expression class in a single class hierarchy in order to pick up both expressions.
_________________________________________________________________________________________________________
Issue: 148649 SR-108345
When a workpool session was left idle for a long period of time, the workpool would be blank when the user reactivated the session due to the AccessGroup and workpool information being reset with information from the database. In order to smooth reactivation, authorization activation has been modified to perform a check and use the workpool information on the passivated pages rather than the ones from the database if no authorization rules have changed since passivation.
_________________________________________________________________________________________________________
Issue: 148965 SR-108581
When creating a work item via a service requestor (e.g. a SOAP service), the work item details are not written to the *federated repository* even though the "Publish Work Remotely?" is set on the work type on the application rule. This issue occurs because FCMR “Can publish?” When rule was trying to rely on the existence of an Application clipboard page to check if the Case type can publish the work to the FCMR repository. If the request comes from any SOAP service, the Application clipboard page does not exist, so the When rule returned false. As a result, the work items are not pushed into the repository. In this situation, the system will now create an Application clipboard page if one does not exist, so that work items may be put into the repository.
_________________________________________________________________________________________________________
Issue: 149001 SR-104619
Some information in the SOAP header end elements must be qualified by a XML namespace. However the generated WSDL contained the elementFormDefault="unqualified" in the schema definition without specifying form="qualified" for the elements that needs to be qualified, so while global elements were properly qualified with the namespace, local XML elements were not. This has been changed so any client that uses the WSDL will properly qualify the element with the required namespace defined at individual node level. Specifically, elementFormDefault is always set to "unqualified" in the schema. If the namespace defined at a node level is the *same* as the targetNamespace of the schema to which it belongs, the generated element in the WSDL must have "form" attribute set to "qualified". The *schema* element still has elementFormDefault set to "unqualified".
_________________________________________________________________________________________________________
Issue: 149152 SR-108496
As part of theSmartInfo accessibility enhancements, a custom event [popOver's onContentDisplayed event] was used to trigger a callback. The element values given to the SmartInfo container are acceptable to most modern browsers, but some versions of IE are quite strict and do not accept the CSS color codes used, resulting in a Javascript error that caused IE8 to display a non-clickable close icon. A more refined cross-browser solution was implemented.
_________________________________________________________________________________________________________
Issue: 149430 SR-108602
Calling Flow as an escalated action from Service Level rule caused an error. The parameter was incorrectly set as "flowtype" in the activity, and has been corrected to "flowType".
_________________________________________________________________________________________________________
Issue: 149522 SR-109157
“Create PDF” SmartShape used a fixed orientation of landscape mode when printing a letter. A page orientation parameter has been added to the SmartShape to allow the choice of portrait or landscape printing.
_________________________________________________________________________________________________________
Issue: 149553 SR-109206
The “enter” key is used to submit a form in the Perform harness, but it was possible to use the option “Hide the default Action Section buttons?“ in Flow Action. This meant there was no Submit button on the form. When the enter key was pressed, the process tried to submit the form, but due to the removal of the Submit button actions, the system could not find the Finish Assignment activity and went into an infinite loop and disabled all the other buttons in the form. The submission process has been changed to submit the form only when the submit button is available on document or bulk submit button is enabled, and the handleSubmit method has been changed to not to set busy indicator when the enter key is used, but rather to set it before submitting the form.
_________________________________________________________________________________________________________
Issue: 149554 SR-107386
JMS activities for both test connectivity and runtime used Queue/Topic specific interfaces based on the selection in JMS Producer Model data instance. This created a problem when a unified (generic) ConnectionFactory was created in WebSphere as opposed to a QueueConnectionFactory or a TopicConnectionFactor, generating the error “Fail :Couldn't create JMS connection: java.lang.ClassCastException: JMSConnectionFactoryHandle incompatible with javax.jms.QueueConnectionFactory”. The ClassCastExceptions have been resolved by leveraging JMS common interfaces instead of Queue/Topic specific interfaces.
_________________________________________________________________________________________________________
Issue: 149584 SR-106801
When localized Field values were given for the Properties description, these localizations were not being applied to the Application document generation. While getting the property description for generating the Application documentation, the actual value was being fetched instead of the localized value. This has been corrected.
_________________________________________________________________________________________________________
Issue: 149802 SR-107534
There was an error in the documentation regarding timezones and conversions. The DateTime.FormatDateTime function accepts timezone as the 3rd parameter. The 4th parameter is for locale. The confusion is from the Expression Builder Example,which passed the 4th parameter as "EST" which is wrong. Additionally, PRPC makes use of the timezones allowed in java in doing the date conversion, but a few timezones like EDT, MDT and some others are not allowed/available in the java api in doing the date conversions because they are not unique. Instead of these three letter timezones, timezones should be designated as America/New_York, America/Mexico, and other values outlined in the list of java supported timezones here :http://tutorials.jenkov.com/java-date-time/java-util-timezone.html
The function documentation has been updated to reflect the third parameter change, and examples of functions have been updated to “America/New_York”.
_________________________________________________________________________________________________________
Issue: 149855 SR-108991
The flow action Work → EditAttachments failed in 7.1.4 using the out of the box PegaSample-Task item (ie General Task). Returning from editing in Word generated the error “You don't have the privilege to save attachments in any category”, and the submit saved a corrupted file. This has been fixed to the correct behavior of returning a dropdown of categories to select before submitting the flow action and correctly saving the updated Word document as an attachment.
_________________________________________________________________________________________________________
Issue: 149894 SR-109004
When implementing field level validation, any errors generated by those properties will have an error icon displayed next to it. When scrolling to view, the error image remained at the fixed position of the monitor rather than remaining next to the problem area. This was caused by the error icon having a CSS attribute of “position: static”, tying that error icon to the browser window. This has been fixed by giving the error icon the attribute “position: absolute” and setting its parent HTML element to have “position: relative”. As a result, when the screen is scrolled, the error icon now stays tied to the field where the error occurred.
_________________________________________________________________________________________________________
Issue: 149934 SR-108384
In a repeat grid, when you configure actions and do not specify the “Using Page”, it automatically defaults to a row page. Once submitted, a flow launched in a modal is designed to merge with the Parent flow from which it was launched. An engine error was occurring when a local flow action that doesn't update any of the data in the declare page was then attempting and unable to update the page due to its read-only status. This was remedied by inserting a check that prevents the merge if the page is set to read-only.
_________________________________________________________________________________________________________
Issue: 150228 SR-108930
Using the Pega section rule "pxSessionTimer" in a harness to implement a timeout mechanism in the portal was not working as designed, causing a rendering distortion in the portal and failing to trigger the timeout when the given interval has elapsed. The problem was caused by an HTML error in the OOTB function "pxSessionTimer". There was a workaround of incorporating the JavaScript content of pxSessionTimer in a Rule-HTML-Fragment included in UserWorkForm, but the provided code for this section rule has been repaired and will now work correctly.
_________________________________________________________________________________________________________
Issue: 150243 SR-108588
An enhancement has been added to allow locally setting the parameters for Java Mail by way of an "Advanced" button in the inbound area of the Email Account form that will launch a simple modal and override all other settings. One example of using this would be to create an email listener to read email messages from a shared email box in MS Exchange 2010 via IMAPS protocol. To do this, set the USER ID on email account form in the following format: “domain\username\sharedMailbox” and set two extra properties for IMAP connection in step 5 of Data-EmailAccount POP3orIMAPConnectivity Activity:
prop.setProperty("mail.imaps.auth.plain.disable", "true");
prop.setProperty("mail.imaps.auth.ntlm.disable", "true");
_________________________________________________________________________________________________________
Issue: 150306 SR-108981
When starting WAS8 server with Java2Security enabled, the first or second attempt to start the system would throw a StackOverflow and get stuck in a loop checking permissions. Eventually the system would startup. The root cause of the issue lies in the way Apache harmony checks for permissions: during permission check, the host name of the code source URL is being resolved to an IP Address. Since the format of the URL that PRPC generates contains a hash code rather than the real host-name, the hash code might sometimes generate a negative number. IBM is working on a solution, but while that code is being fixed, changes have been made to the PRPC code to bypass the problem by avoiding generating a negative number for host name and overriding the places where URLStreamHandler uses the host name for IP Address resolution.
_________________________________________________________________________________________________________
Issue: 150323 SR-107067
When using watch variables in the Activity tracer, the old and new values were not getting populated. This was incorrect behavior and has been fixed.
_________________________________________________________________________________________________________
Issue: 150329 SR-109219
When running a series of overlapping lengthy BIX extractions, there were points when the complete log from one or more of the extractions was not being written due to simultaneous attempts to write to the log. This was an issue with non clearance of the Log4J buffers when doing a System.exit, and those buffers are now being explicitly cleared to ensure the logging process is completed before the next extraction starts.
_________________________________________________________________________________________________________
Issue: 150411 SR-108970
The OOB function getAsBusinessDay(Library:BusinessCalendar) was returning the wrong result. This stemmed from an error in the java code, and has been corrected by changing “String currentDate = pega_rules_datetime.CurrentDate("yyyymmdd", timezone);” to “String currentDate = pega_rules_datetime.CurrentDate("yyyyMMdd", timezone);”
_________________________________________________________________________________________________________
Issue: 150422 SR-106906
SQL with Websphere was generating the error “GenericCaseMgmtServicePackage|Services|GenericNotify|AE6483EABFCC469AF8CA530956C70A614 - Error in commit()
com.pega.pegarules.pub.database.IntegrityConstraintViolationException: Database-Saver-Insertfail“ when encountering duplicate dates. pzInsKey is made up of the work object id plus the current time, but if the time portion is generated for two separate entries within the same millisecond, then this leads to a conflict. In order to avoid this, PRPC now uses “getCurrentTimeStampUnique”() for setting the attachkey property.
_________________________________________________________________________________________________________
Issue: 150671 SR-109351
Attempting to delete an Accordion Layout from a Section via the trashcan icon results in a JavaScript exception message: "Exception when trying to execute deleteElement" error. The Design View has been updated to use cross-browser functions.
_________________________________________________________________________________________________________
Issue: 150856
In the System “alerts by week” section of the Application → Guardrails → Compliance Score landing page, the enhancement "Interaction Count" has been added to Alert Count and Average Request Time (seconds).
_________________________________________________________________________________________________________
Issue: 150926 SR-109632
Calling Flow from Service Level rule was causing LockGoneException error messages in PegaRULES log. This was caused by the wrong activity being called in case of SLA Run Flow, and has been changed.
_________________________________________________________________________________________________________
Issue: 151456 SR-108748
Upon opening a custom portal, an activity that makes a obj-open-by-handle call was throwing a null pointer exception during the ThreadContainer.get() call from isCustomLockTimeOutSet(). This occurred once in a day for an operator, but not during the very first call of the day. The issue occurred when ThreadContainer.get() returns null, and has been changed so isCustomLockTimeOutSet uses the thread passed as a parameter and will try to perform .get() if it receives a null.
_________________________________________________________________________________________________________
Issue: 88653 SR-80391
TITLE attributes were missing for the NewWorkGadget control and when using the Date control in the input mode. A new parameter has been added for a TITLE attribute in NewWorkGadget and Dynamic Select.
_________________________________________________________________________________________________________
Resolved Issues for 7.1.6
SR-78890 ISSUE: 86812
Delete row was not working in a repeat grid with validation errors when the perform harness "DISPLAY FORM-LEVEL ERRORS" is set to "in configurable section". When using a custom error section, any errors in the Primary page caused a 'customErrorMsg' SPAN tag to be sent along with the response. When the handleErrorAfterPartialSuccess API found this span tag, it aborted any further Js actions, leaving the row in place and generating a NPE. The API has been changed so if the delete is successful the system will continue without error.
_________________________________________________________________________________________________________
SR-95608 ISSUE: 125912
While the user worklist correctly displayed names in Japanese (Katakana), the user name was not being correctly passed to an activity as a parameter when using openWorkByURL. There was a workaround that used the clipboard to retrieve the value when needed for a specific use-case, but the encoding steps for passing a multi-byte username have been fixed to accurately pass the Japanese characters.
_________________________________________________________________________________________________________
SR-99387 ISSUE: 134235
Column filtering was not displaying correctly in the attachment window list view when non-alphanumeric characters were used at the beginning or end of the column name. Filtering has been adjusted to handle column values with non-alphanumeric characters and incorporate them when giving results.
_________________________________________________________________________________________________________
SR-100313 ISSUE: 134172
When HistoryListView (Listview rule) used a custom activity for report source, the sorting behavior did not allow flexible sorting. This has been updated to handle multiple sorting methods.
_________________________________________________________________________________________________________
SR-100499 ISSUE: 136626
When upgrading, the parse assembler for 7.1.2 was not creating names of elements in a connect-rules valuelist correctly. This was traced to a bug in that assembler that caused incorrect mapping of the data from the response xml. It was possible to call an old version of the assembler as a workaround, but the assembler has been fixed to properly generate the elements.
_________________________________________________________________________________________________________
SR-100866 ISSUE: 136213
Generating SOAP connect rules using the Connector Wizard with WSDL and checking the box to disable theWS-Addressing requirement generated the error message “com.pega.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present”. While there was a workaround involving restarting the server after selecting the WS-A checkbox, the code has now been modified to correctly read the dynamic state of the checkbox and skip the addressing handler when enable addressing is false.
_________________________________________________________________________________________________________
SR-101329 ISSUE: 136194
The default values for MaxTotalConnections and MaxHostConnections given in the InvokeAxis2 activity were set too high, and too many idle TCP connections were left open before being reset. This socket overload caused system performance issues and the inability to open new cases. These connection values can be set dynamically, but the default values have been lowered from 1000000 and 100000 to 1000 and 100 respectively.
_________________________________________________________________________________________________________
SR-103684 ISSUE: 140892
When opening an attachment with an undefined file type, the current PRPC session was being replaced in the active Internet Explorer browser window and could not be resumed. The viewer has been updated to open attachments without a file extension in a new Internet Explorer tab.
_________________________________________________________________________________________________________
SR-104008 ISSUE: 139599
When using accordion with tab group, the accordion stopped being usable and none of the accordions in the layout were clickable. The tab view attributes have been fixed to handle accordion layouts.
_________________________________________________________________________________________________________
SR-104416 ISSUE: 144881
In batch operations, like batch outbound marketing, some users were getting an error: “ERROR – Batch table creation failed.” In batch operations, a large number of classes and properties are dynamically created and then an inventory is taken of their property types. This error occurred because the property information (property type) was not being returned to the caller when a large number of classes and properties were being created dynamically. We improved synchronization of property lookups so this problem no longer occurs.
_________________________________________________________________________________________________________
SR-104783 ISSUE: 142872
Email with no FROM header information in the .eml file, typically bounce messages from the mail server, caused NPEs when processed by the EmailListener. Checks have been added to correctly handle messages with null fields.
_________________________________________________________________________________________________________
SR-104805 ISSUE: 149107
A large number of -803 errors were being created for updates to the pr sys cache dep table. These errors did not show up in any logs, but did show up in the monitoring detector and appeared to be truncating the cache tables and causing assembly to fail. No impl key was being saved to the DB and some generated class entries were missing in the sys cache impl table, so the assembled class couldn't be found and was constantly triggering new assembly. Later assembly also failed at GlobalCache lookup. To prevent this problem, both entry and ACE from Web/Webtesting node will not be saved to the DB to prevent reusing by other nodes, and the entry in cache will be removed if the generated class can’t be found from nowhere (cache and DB and file system) since it is unusable.
_________________________________________________________________________________________________________
SR-104943 ISSUE: 143905
The InvokeHTTPConnector was not able to handle a connection for social media integration through a proxy because the underlying Apache HTTP layer did not have a direct way to specify a proxy host with authentication content (username and password). Support has been added for REST & HTTP connectors to consider proxy configuration.
_________________________________________________________________________________________________________
SR-104965 ISSUE: 143153
When a test suite was scheduled to run recursively, the queue entry was being saved as an instance of "System-Queue-TestSuite" in table "pr_sys_queue_autotest". However, the agent "RunRecursiveTestSuites" was querying for queue entries from table "pr_sys_queues" for instances of "System-Queue-DefaultEntry" class, with the result that the Test Suites were never running. The class of the agent activity has been changed to be picked by the recursive agent.
_________________________________________________________________________________________________________
SR-104991 ISSUE: 144459
Based on the locale that is set on the operator profile, the application is localized to the correct language. This was not being correctly set when using a screenflow in a modal popup, and the language of the browser was used instead. This has been corrected.
_________________________________________________________________________________________________________
SR-105049 ISSUE: 142755
When the locale setting used 24 hour time, the popup picker for calendar in listview was showing 12 hour time with AM/PM disabled. The setDate API has been corrected to check if it is 12 hour or 24 hour format and display the date time in correct format in popup picker calendar.
_________________________________________________________________________________________________________
SR-105895 ISSUE: 145710
If a decision tree used with a custom ARO contained a call from an 'Access When' rule to the function havePrivilege, an exception was thrown. The instance page was not being passed correctly, and the handling has been fixed.
_________________________________________________________________________________________________________
SR-106031 ISSUE: 145632
The getAsBusinessTime function was failing to convert the "passed in" time to that of timezone specified in the calendar. The logic has been reconfigured to convert the time correctly based on the calendar specified by the user.
_________________________________________________________________________________________________________
SR-106108 ISSUE: 150895
A change in the Parse XML was causing an error on rules imported from older versions of PRPC; properties were mapped correctly for the first run after server restart, but had subsequent errors. Activity executed manually by login to the developer portal did not contain the errors. A temporary workaround using the DSS "SwitchToOldAssembler" called the old Parse XML assembly, but the new implementation of the Parse XML Java Wrapper has been fixed to map the properties correctly.
_________________________________________________________________________________________________________
SR-106187 ISSUE: 146044
Complex rule-declare-expressions were displaying inconsistent behavior when variables were overridden in the reference properties. This function has been updated to ensure the expression is checking the correct reference for the variable change.
_________________________________________________________________________________________________________
SR-106331 ISSUE: 149926
Using the DateTime property, 'AM' and 'PM' were being assumed for values greater or less than 12:00. Additionally, time defaulted to AM if the AM/PM field was changed to nothing and the Hours and Minutes fields were both also empty. New code has been added to include a "Set AM as default" checkbox on datetime properties. Based on this selection, times will show "--" or "AM" appropriately.
_________________________________________________________________________________________________________
SR-106390 ISSUE: 144231
Using HTTPS, REST connections were not successful when using a certificate where the hostname in the certificate did not match the hostname of the server receiving the connection request. This behavior may be desired during UAT using manually generated certificates, so a dynamic system setting “https/allowAllHostnames” has been added to Pega-IntegrationEngine. It must be set to 'true' to allow this connection, but note that this causes HTTPS to be less secure and should be used with caution.
_________________________________________________________________________________________________________
SR-106449 ISSUE: 147029
It was possible to right-click a Tree Node and open a duplicate instance of the same work object in the same thread in a new window or tab. This opened the potential for data corruption as the same thread is being used, and the JavaScript has been updated to not allow opening the new window or tab.
_________________________________________________________________________________________________________
SR-106464 ISSUE: 145647
Filter options in repeat grids were not consistent for Date and Currency fields. This was traced to the data type defaulting to "Text" irrespective of the property type defined in rule form, and has been corrected.
_________________________________________________________________________________________________________
SR-106553 ISSUE: 143753
After skimming a ruleset during an upgrade, some "Where am I?" images were missing and 404 errors were displayed in logs while referencing the Rule-File-Binary image used by the work item. This was caused by Work-GetLocationForAssignment not being able to locate the originating flow used to create the work object, and has been corrected to support cases where the current location no longer exists in the rule-obj-flow.
_________________________________________________________________________________________________________
SR-106587 ISSUE: 157142
In some cases, attempting to refer to a property being pattern inherited from another class caused a NPE. This issue was caused by two declare expressions from higher and lower rulesets both being defined as 'whenever inputs change' but which then used different decision rule methods. When an operator who did not have access to the higher ruleset changed the property, the error occurred. A check has been added to ensure the correct inheritance rules are followed.
_________________________________________________________________________________________________________
SR-106632 ISSUE: 152168
The SOAP Connector wizard in 7.1.3 generated XML Stream rules with "mode=literal" in the XML source, and doing a checkout and clicking Save without any changes generated a guardrail warning. The reported behavior was part of a critical optimization that allowed the wizard to generate significantly fewer XML parse and stream rules by using a wildcard as the name of the root node for component rules, and passing the root node name in from the parent rule that calls it. The runtime behavior is identical to the previous behavior, and the wizard completes 10x to 20x faster than before. However, because this warning was causing customer concern, the mode=literal has been changed to mode=normal and the warnings have been suppressed. Performance should not be affected.
_________________________________________________________________________________________________________
SR-106672 ISSUE: 153403
The Smartinfo popover configured over a user worklist was being truncated when using older fixed portals (e.g. WorkManager). The code has been updated to correctly calculate the available space and display in available directions (left/right/top/bottom/middle).
_________________________________________________________________________________________________________
SR-107100 ISSUE: 151508
The SystemHealth GetStatus API was invoking MBeans that generated large log files of NPEs. Since getStatus method is not a static implementation, MB2EngineAccess.invoke tries to create an instance of SystemHealthAPI on which it can invoke the method. Because SystemHealthAPI is a static singleton and has no visible default constructor to invoke, it fails to create an object of SystemHealthAPI and ends up invoking the method on a NULL object. This exception is then propagated back and creates the error. To resolve this, the behavior was changed to make the instance variables static.
_________________________________________________________________________________________________________
SR-107182 ISSUE: 151804
When drilling down from a chart to list view, the header value was not being displayed in the listview due to a missing summary view page. Additionally, if the drilldown parameter had no value, the list view header displayed the string "(Empty)". This has been corrected.
_________________________________________________________________________________________________________
SR-107324 ISSUE: 153620
Under some circumstances, inbound SWIFT (interbank communication) messages were causing the MQ listener to briefly suspend and cause a delay before recovering automatically. The thread locking has been modified to correct this delay.
_________________________________________________________________________________________________________
SR-107518 ISSUE: 152014
The Global Checkbox was not behaving as expected when used with progressive scrolling within a report: only those rows loaded at the time the Global Checkbox was checked were included in the check while progressively loaded rows were not, and unchecking one of the rows did not uncheck the Global Checkbox. Changes have been made to support proper header unchecking in progressive load-enabled grids.
_________________________________________________________________________________________________________
SR-107554 ISSUE: 149629
If a custom format was given for date values in Report Definition, blank date values were given the value "31 Dec 1969" when the data was exported to Excel. A change has been made to store date/time values in a 64 bit floating point number to match the format used by Excel to eliminate this error.
_________________________________________________________________________________________________________
SR-107656 ISSUE: 152286
When importing database table mapping instances from one PRPC system to another, the import utility may detect an invalid schema definition for some tables. When the SQL which was generated is checked, it contained the following error: “Invalid XML found in the import archive.” There seems to be difficulty with synonym processing by Oracle databases. Now the system will eliminate the duplicate columns when the archive is being built, and emits a diagnostic message: “Ignoring duplicate column data for table *tablename* (possibly due to the presence of multiple synonyms).”
_________________________________________________________________________________________________________
SR-107671 ISSUE: 148112
Different browsers were having difficulty correctly displaying very large decision tables. In Internet Explorer 8, the text being edited in a long decision table was hovering above the cell, causing confusion as to which row is being edited. In Internet Explorer 9, the rows of a long decision table were not properly aligned. In Chrome, the 'Export to Excel' button was not visible. These browser issues have been remedied.
_________________________________________________________________________________________________________
SR-108123 ISSUE: 155587
A Rule Cache Management operation via SMA to a remote PRPC node in PegaCloud was timing out with the error “Node: APAC-1 Exception”. To remedy this, the logic has been updated for looking up the presence of a property reference in the property reference pool. Previously, the lookup was a linear search. This is now a lookup for value based on key and the key is built from the value, reducing the search to map lookup.
_________________________________________________________________________________________________________
SR-108139 ISSUE: 152813
Values under filter option were not properly sorted when a filter was applied to a mixed integer/decimal type column. The parameter list has been updated for better sorting.
_________________________________________________________________________________________________________
SR-108199 ISSUE: 152471
When creating the Export to Excel for a repeating grid, a Java activity step is used to set the ContentDisposition header to reference a specified filename for the Excel file. In a standard portal environment, this works as expected; the Content-Disposition header can be seen (through tracing tools) when the request/response is made, and the opened Excel file has the name provided. However, in the Pega Portlet/WebSphere Portal environment, the Content-Disposition header was not visible (in the tracing tool) and the Excel file name was always the default (PRPortlet.xls) and never the one specified through the activity. The Portlet functionality has now been enhanced to use the Content-Disposition header specified in the activity.
_________________________________________________________________________________________________________
SR-108340 ISSUE: 152335
When sending attachments from PRPC to Outlook, Chinese characters in the attachment filenames were not properly handled. This has been corrected by encoding the characters before sending.
_________________________________________________________________________________________________________
SR-108345 ISSUE: 151401
An operator AccessGroup and related work pool information was not being correctly restored when reactivating passivated pages. Authorization activation is now modified to use the workpool information on the passivated pages rather than the ones from database if no authorization rules have changed since passivation.
_________________________________________________________________________________________________________
SR-108367 ISSUE: 150675
The 7.1 parse rule assembly handles dynamic element substitution in a way that differs from the way the 6.3 assembly functioned. Instead of using the rule keys listed on the node that contains the Apply Rule mapping for the substitutable content, it uses the element name and namespace URI of the element that appears in the incoming XML stream. This caused different results depending on the environment being used while importing an XSD with element substitution rules. There was a workaround to use a Dynamic System Setting to revert the parse rule assembly to the one used in 6.3, but the parse rule assembly code has now been changed to use the rule keys that appear in the mapping details for all elements.
_________________________________________________________________________________________________________
SR-108399 ISSUE: 149592
Using the traditional portal, an error 400 was generated when clicking 'links' under the Tools menu if the prconfig variable SubmitObfuscatedURLwas set as optional. A change has been made to safeurl to check whether the 'pega' object is defined or not before it is called, which eliminates the error.
_________________________________________________________________________________________________________
SR-108440 ISSUE: 154902
After running the Refactor tool to change the RuleSet name, it was not possible to choose the RuleSet version context and create rules that required this context selection (such as new->sysadmin->agents). To remedy this, the hasDependency API has been modified.
_________________________________________________________________________________________________________
SR-108490 ISSUE: 148647
When Security Policy is enabled and login penalty is set, the operator record in pr_operators table is locked during the login penalty waiting period. If the operator password is reset during this waiting period, the previously completed authentication would cause the operator record to be updated with the last logon timestamp, and the changes done by the agent were overridden. A new API has been added to get the attempted username in all the implementations of IauthenticationScheme in order to determine whether to introduce a delay or not for a particular user.
_________________________________________________________________________________________________________
SR-108511 ISSUE: 153527
In Case manager portal --> My Events -- > Go To, Deadline Calendar and Goal Calendar were selected by default. An enhancement has been added to allow customization in the calendar by using a checkbox to control the behavior of Option(Show Events Initially) in the CMEvents section.
_________________________________________________________________________________________________________
SR-108515 ISSUE: 150752
An enhancement has been added to the activity CalendarViewPreProcessing to localize the Calendar Name. This allows the creation of field values for default Calendar Names, and can be used to fulfill business needs like displaying a Calendar Widget with two types of events (ex, "Assignment Goals" and "Assignment Deadlines").
_________________________________________________________________________________________________________
SR-108559 ISSUE: 159218
If a report has filter conditions for a property with symbolic dates (like 'today', 'yesterday' etc.) it runs an RUF 'GetStartOrEndDate' to calculate the time window that is applicable. During this evaluation, this RUF uses time zone and locale from the 'Requestor' page. In the case of reports being run by a batch requestor, the Requestor page was not honoring the JVM argument Duser.timezone and was instead returning results based on GMT. The system has been updated so PRDateFormat will take into account the JVM parameter for time zone if passed.
_________________________________________________________________________________________________________
SR-108585 ISSUE: 154052
When using Chrome and editing a property in the Decision Table Rule Form, double-clicking the table column header opened an unnoticed pop-up window behind the current window. This made the Rule Form appear unresponsive without reason and prevented the updated values from being reflected in the table. This was linked to Chrome's modal dialog, and was resolved by setting a Boolean flag that performs a check to see if the new window is already open to prevent duplication.
_________________________________________________________________________________________________________
SR-108628 ISSUE: 152169
The OOTB property BranchID had a max length of 16 even though documentation indicated the field length was 64. This caused a problem for functions like the TrackSecurityChanges transform rule where the field name exceeded 16 characters. To remedy this, an exception has been added for these FVs (TrackSecurityChange_Add and TrackSecurityChange_Remove) during validation to allow for the needed length.
_________________________________________________________________________________________________________
SR-108639 ISSUE: 151825
The activity CheckWorkObjectID was set to require authentication. Since other processes that call CheckWorkObjectID (such as DeleteAssigmentsForWork) are allowed run as unauthenticated, this behavior has been modified to allow the authentication setting of the calling process to filter down to all subordinate activities.
_________________________________________________________________________________________________________
SR-108672 ISSUE: 150501
If a new knowledge content rule was created and additional content was added in a separate layer, re-opening the checked-in rule and deleting a layer caused the layers following the deletion to also be deleted. Attempting to save the rule at this point caused further rule corruption and the system would become unresponsive. This was traced to an issue with synchronizing the page and clipboard data, and has been corrected.
_________________________________________________________________________________________________________
SR-108703 ISSUE: 153531
Previously, Log-Service-File entries were not being purged by SystemCleaner activity after aging for a predefined time. This behavior was causing an undue buildup of these entries and impacting recovery processing in the file listener, and has been modified to be included in SystemCleaner.
_________________________________________________________________________________________________________
SR-108748 ISSUE: 153568
Upon opening a custom portal using IAC configuration, the first use of Obj-Open-By-Handle was generating a null pointer exception. Pressing F5 allowed work to continue, but the error was traced to Java code in the ThreadContainer which has now been changed.
_________________________________________________________________________________________________________
SR-108779 ISSUE: 151704
When emails were not processed successfully because of AddressException (or any exception extending javax.mail.MessagingException), this failure was not being written to the log unless logging level was set to "INFO" or "DEBUG". A dynamic system setting named FailOnAddressException has been added to Pega-IntSvcs to better handle this. The default value is 'true' to ensure message processing failures are caught, but can be changed to ignore processing failures related to message headers if desired.
_________________________________________________________________________________________________________
SR-108781 ISSUE: 153486
After using the 'Edit in Excel' feature to update propositions, attempting to export the propositions to a new environment did not carry over the latest values from the source environment. This was linked to a specialized save activity which has been replaced with a baseclass Save activity to correctly update information about the creation/update of instance. This same baseclass Save activity is also now being used when creating/updating propositions from LP.
_________________________________________________________________________________________________________
SR-108835 ISSUE: 156409
An enhancement has been added to create a "pagegroup ordering by subscript" feature/tab for splitforeach available to screenflow, enabling complex flows such as a split on a page list where each page of the list references a page of a pagegroup.
_________________________________________________________________________________________________________
SR-108845 ISSUE: 152920
When a mail message sent from Outlook contained Chinese, Thai, Japanese, or other characters in the To, Cc, or Bcc lines, the characters were not correctly handled when the email reached PRPC. The system has been updated to properly handle the encoding of To, Cc and Bcc headers in Email Listener.
_________________________________________________________________________________________________________
SR-108879 ISSUE: 151966
Earlier versions of PRPC were finding inconsistencies when Update Manager was run after an upgrade. The application has been refined to ensure accurate reporting of hotfixes vs maintenance level releases.
_________________________________________________________________________________________________________
SR-109038 ISSUE: 149426
When upgrading, a rule which is not associated with any ruleset version (non rule resolvable rule) would create a null pointer exception error. The PRScanner.java has been updated to handle this condition.
_________________________________________________________________________________________________________
SR-109108 ISSUE: 152061
PRPC placed a backslash before an accent mark for the localized label of a field value used as the False Label for a CheckBox-control. The backslash was not added when using the same field value as a label in a grid, eg "d\'évaluations" versus "d'évaluations".The function has been replaced with CrossScriptFilter which simply converts special characters to HTML for consistency.
_________________________________________________________________________________________________________
SR-109152 ISSUE: 152641
In Report Definition, applying a format to a column with blank values caused the filter condition for the value in the report to show “Empty” instead of the formatted value. This was resolved by adding a check for a localized string value.
_________________________________________________________________________________________________________
SR-109161 ISSUE: 158554
Bulk Processing Agent was losing lock and crashing when the bulk processing agent was run in two nodes. In some cases when multiple sets of Bulk Resolves were initiated, it halted processing at a certain point, then sent multiple emails for the same set before ceasing all processing. This was caused by an incorrect implementation of the bulk action code, and has been fixed.
_________________________________________________________________________________________________________
SR-109186 ISSUE: 150967
When a Prompt Select is populated with a value which does not exist in the Local List configured for that property, the error message "**ValueNotInPromptList\tVALUE\tPropName" was displayed. This message contained inappropriate \t characters and needed more information. The error message has been changed to "The value [value2] for property MyPrompt is not defined in the prompt list".
_________________________________________________________________________________________________________
SR-109191 ISSUE: 155144
A "Server Error: -1" error was being generated when logging off from "Summary Views" in the Portal Dashboard. This occurred when the request to unload the page reached PRPC after the endsession 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.
_________________________________________________________________________________________________________
SR-109194 ISSUE: 151202
An enhancement has been added to handle different URLs for schema definition (xsd path) for dev, test and production environment, allowing dynamic configuration of the xsd path in parse XML instead of requiring the absolute path.
_________________________________________________________________________________________________________
SR-109229 ISSUE: 160066
When queuing a task, the primary requestor's access group would not trickle down more than one level. For example, if a user queues a task to Agent (A), Agent (A) will be working with the original user’s AccessGroup. If Agent (A) then queues the task to Agent (B), Agent (B) will not be running with the original user’s AccessGroup. To fix this, the Authorization cache has been modified to correctly update with the switched access group value for the task.
_________________________________________________________________________________________________________
SR-109307 ISSUE: 155223
A NPE was being generated when the 'Create Custom Report' icon was clicked twice. This was caused by the activity Wizard_Clear_ClipBoard having cleared the clipboard after the first click, leaving nothing to be processed on the second click. The click behavior has been changed to not delete the page if the report wizard is already open.
_________________________________________________________________________________________________________
SR-109362 ISSUE: 153008
A checkbox configured in a repeat grid header to perform a "select all" of all the rows in the repeat grid did not test whether the row level checkbox was enabled or not. A conditional test has been added to detect whether the row level checkboxes are enabled and skip them if they are not.
_________________________________________________________________________________________________________
SR-109370 ISSUE: 151768
If a report definition was created that referenced a clipboard list of over a million items, an OOM error would occur. The clipboard now has a limit of 5,000 items.
_________________________________________________________________________________________________________
SR-109482 ISSUE: 152180
When a decision table has multiple action columns, all fields in the action columns on the 'otherwise' row were copying the value in the field of the first action column on the otherwise row. This has been corrected.
_________________________________________________________________________________________________________
SR-109508 ISSUE: 159396
If an operator has multiple access groups associated with it, changing groups did not change the default access group and rulesets. This has been fixed to ensure the correct access group and rules are applied when the operator switches groups from the user portal.
_________________________________________________________________________________________________________
SR-109687 ISSUE: 154410
When using Internet Explorer with Japanese IME installed, the Developer Studio's IME mode control of “normal” was not being supported by the browser and was defaulted to the “active” setting instead. This caused the browser to switch to Japanese every time the tab key was used to change fields. To correct this, the default IME mode for all languages has been changed to “auto”, meaning no change is made to the current input method editor state when tabbing.
_________________________________________________________________________________________________________
SR-109713 ISSUE: 152817
In certain circumstances using Internet Explorer 8, clicking the autocomplete on one of the input fields on Report Definition rule form created a large blank area at the bottom of the screen which could not be removed. This was traced to the iframe calculation used by Internet Explorer 8, and was fixed by modifying the logic used to identify the top location of the popup.
_________________________________________________________________________________________________________
SR-109717 / SR-111833
ISSUE: 152936 / ISSUE: 156251
When a custom field was added to a Decision Table, any “when” step was lost during the rule save even though the custom field remained. This has been corrected to ensure all steps and conditions are properly saved.
_________________________________________________________________________________________________________
SR-109744 ISSUE: 153496
When copying from Word and pasting to RTE, the font was not being correctly matched. This has been fixed.
_________________________________________________________________________________________________________
SR-109764 ISSUE: 154808
Radio buttons configured with onChange action will trigger the action when clicking a button that is already selected. This was traced to Internet Explorer 9 having an undefinedelement.value that caused the event to fire irrespective of the value change, and the code has been modified so the button handling will to cancel the action if the radio button value is the same as previously given.
_________________________________________________________________________________________________________
SR-109765 ISSUE: 155393
When creating a flow, if the work parties of a work object included the work party mentioned in the last row of the “Send Email” shape, then it was sending email to everyone. If the work party type mentioned in the last row was not added to another work object, then the email would not be sent to anyone. This was caused by an “if” condition being returned as false if any of the included party types did not match with the value of the final shape's variable, and has now been corrected to ensure the mail activity performs as expected.
_________________________________________________________________________________________________________
SR-109792 ISSUE: 152360
When a tab group was set to a vertical style (left), no visual textual content was generated on UI in the sections of the Tab when relative font size is used. This was traced to vertical tabs that had a hard coded inline style of 0 pixels for the tabs font size and the content of the tab area; this coding style is deprecated, is not supported in HTML5, and is not supported in Strict DOCTYPE. The code has been updated.
_________________________________________________________________________________________________________
SR-109792 ISSUE: 156170
Previously, vertical tabs had a hard coded inline style of 0 pixels for the tabs font size and the content of the tab area. When a tab group was set to vertical style (left) and a relative font size was used, no visual textual content was generated. This has been corrected.
_________________________________________________________________________________________________________
SR-109837 ISSUE: 151418
JavaScript has been added to the File Listener rule form to use a custom password text box that hides the encrypted password value, preventing the password from appearing when the user does a “View Source” on the rule form of the listener instance. Previously, the encrypted operator password was visible in the HTML of the File Listener form because a text box was used for user input.
_________________________________________________________________________________________________________
SR-109914
ISSUE: 152820 / ISSUE: 156191
After defining a screen flow, the "Close this item" icon was incorrectly inserted to the right of the first title bar defined on each section step of the screenflow. This was caused by improper handling of the check for right widgets in the title, and resolved by adding extra checks for the same.
_________________________________________________________________________________________________________
SR-109915 ISSUE: 154862
When a section was created in Tabbed Screenflow with a search that returned a list of items where one needed to be selected, double-clicking a repeat grid row caused the text around/outside the grid on the screen to be highlighted. This only occurred in Internet Explorer 8, and the grid handling has been updated to process the correct selection for the double-click in that browser.
_________________________________________________________________________________________________________
SR-109937 ISSUE: 152701
If a formatted text property was used in the header/title of a Dynamic Layout, applying an inline style to the property caused a warning icon that increased the row height. To resolve this undesirable behavior, the warning icon display has been changed so it does not affect the cell height.
_________________________________________________________________________________________________________
SR-109938 / SR-111282
ISSUE: 153442 / ISSUE: 155607
When a RadioButton is marked required and it is the first element on a form, a validation error fired when choosing any value other than the first radio. This was caused by the code used to determine button focus: the blur event fires as focus is changed and error div is added, but when a different value was selected on the same radio group, the change event fired to clear any error marker that might exist. To fix this issue, a setTimeout has been added on the required field of radio button, allowing a delay so the onBlur event will not immediately fire a validation unless or until a change event occurs.
_________________________________________________________________________________________________________
SR-109958 ISSUE: 152162
When performing a 'Save As' on Navigation Rule Data-Portal to a custom ruleset (same Label and Identifier just into a custom ruleset version), the Class name of the Flow Action ChangeOperatorSkills on the Action tab was changed from Data-Admin-Operator-ID to Data-Portal, the class of the Navigation Rule. Although the Class Name field appeared editable, it was not possible to amend the Class name and it always reverted to the class of the Navigation rule instance (Data-Portal) rather than the expected class (Data-Admin-Operator-ID). Local Action behavior values in the newly created Navigation rule have been modified to re-set the Class Name and ensure no validation / rule errors.
_________________________________________________________________________________________________________
SR-109964 ISSUE: 156922
After a popup window with an autocomplete control appeared, closing the pop-up window left the autocomplete field on the screen until another part of the screen was clicked. This has been fixed.
_________________________________________________________________________________________________________
SR-109977 ISSUE: 155382
Attaching a file to a new SR in the Pulse feed and submitting the case caused an 'Invalid static content' error. The issue was traced to the getAttribute() method in MSIE finding a duplicate element, and has been corrected.
_________________________________________________________________________________________________________
SR-110000 ISSUE: 152175
An enhancement has been added to TrackSecurityChange to allow referencing a Field value to translate the data into the audit log with additional data from a page list. This allows customization for handling values in pages lists, and logs the translated values instead of the field names and parameters. If the string doesn't start with “TrackSecurityChange,” just the string received is returned without translation.
_________________________________________________________________________________________________________
SR-110123 ISSUE: 155252
On a repeating grid enabled to show details, by default there was no indicator that the rows are clickable. This feature was not present in Grid, and a CSS declaration has been added to display a hand icon that points towards click of the row.
_________________________________________________________________________________________________________
SR-110147 ISSUE: 152120
When using Internet Explorer 8 or Internet Explorer 9, the "Browse" system scanner button used to upload a catalog file was invisible - you could click it if you knew where it was, but no button was displayed. This was caused by a setting incompatibility in Internet Explorer 8 and Internet Explorer 9 where the opacity scale is 0-100 (not 0-1 like in other browsers), and has been remedied.
_________________________________________________________________________________________________________
SR-110185 ISSUE: 152792
If an external table is missing a key column, a configuration exception was being created in the JVM that then tried to look up a rule message, causing stuck threads and poor locking and eventually poor system performance. The system has been updated to better handle this missing information, and improved synching and locking has been added.
_________________________________________________________________________________________________________
SR-110279 ISSUE: 157466
In some instances, Case Manager/Designer was not showing 'child' cases or a way to configure dependencies, e.g. child case B starting as soon as child case A was resolved, and no Instantiation / Dependencies were available from the details tab of the case type rules. In addition, the documentation did not line up precisely with the available options in an actual case. The parent/child case handling and the documentation have been updated.
_________________________________________________________________________________________________________
SR-110301 ISSUE: 156571
A discrepancy was noted in the Work Manager Portal: hitting the “cancel” button in the workobject header returned the user to different places in the work flow depending on the PRPC version being used. The behavior of the “cancel” button in this situation has been set to return the user to the Workbasket.
_________________________________________________________________________________________________________
SR-110352 ISSUE: 154048
When running the 'Execute Activity' after right-clicking a clipboard page from a Thread that is not "STANDARD", the resulting activity crossed Threads when accessing clipboard pages required by the activity. To resolve this, the activity selected from the clipboard viewer will now run in the context of the selected thread rather than always running in context of STANDARD thread.
_________________________________________________________________________________________________________
SR-110355 ISSUE: 158654
In some new PRPC implementations, opening the App Explorer and then selecting a LEAF caused excessive delays before expanding the selected option. This has been improved by tuning the DB with an index that has sharply increased access speeds.
_________________________________________________________________________________________________________
SR-110384 ISSUE: 153575
As part of Hfix-8520, when setting the node name, character cleansing is done to replace special JavaScript characters (“=”, “<”, ” >”, “\”, “/”, “%”, “;”, “&,” and “+”) with underlines in order to preserve the textual context, but render any JavaScript non-executable. As a further enhancement, this cleansing was extended to other text fields in SMA.
_________________________________________________________________________________________________________
SR-110426 ISSUE: 154318
The PromptFieldValue control was not localizing the property values in read only mode. This has been corrected.
_________________________________________________________________________________________________________
SR-110462 ISSUE: 155756
In some cases, it was possible for an operator to make modifications beyond their access group in a portal. The system has been modified to include an access check to prevent unauthorized changes. In addition, autocomplete was incorrectly available for the password field in the user profile, and has now been disabled.
_________________________________________________________________________________________________________
SR-110481 ISSUE: 153138
When trying to launch a local action within an embedded page list of a different class (in expandable rows FA), PRPC was looking for the local action in the top level page list class and did not resolve the correct class. This has been fixed.
_________________________________________________________________________________________________________
SR-110520 ISSUE: 156339
While showing the Report Definition Result, some of the column values were wrapped due to width measurement of the screen and the values were truncated when exported to PDF. This was traced to the column width being set in pixels, and the code has been modified to correctly handle this setting.
_________________________________________________________________________________________________________
SR-110524 ISSUE: 155092
An issue with MultiSelect Listbox Control that caused the standard value to be displayed instead of the localized value has been corrected by adding Label (which is prompt value instead of standard value) to the options.
_________________________________________________________________________________________________________
SR-110530 ISSUE: 154945
An error was discovered in the Invoke activity section of the Rule-Connect-JCA class that caused a list to be incorrectly mapped to the input record index, and has been fixed.
_________________________________________________________________________________________________________
SR-110601 / SR-114143
ISSUE: 159902 / ISSUE: 161363
Under certain conditions, a "Pega is undefined" Java Script error message displayed when there was a visible "when" condition on a Repeat Grid. This issue may occur with any component which uses pega object: if there is a "FilePath" control in UI, form submission happens on a separate <iframe>. Due to this, the running script may not have access to pega object (as it is included in a new <iframe>). To remedy this, an "if" check is now run before accessing pega object.
_________________________________________________________________________________________________________
SR-110659 / SR-111143
ISSUE: 155646 / ISSUE: 156330
Where there are two text areas within the same section and one is hiding and the other one is showing, Spellcheck did not work properly in the text area that was showing. This has been corrected.
_________________________________________________________________________________________________________
SR-110706 ISSUE: 154574
If the locale of the user was set to a 24 hour format and the recurring agents time was set to a value greater than 13:00:00, changing the locale to support a 12 hour format caused the hours drop-down to have a blank value. This error has been corrected.
_________________________________________________________________________________________________________
SR-110753 ISSUE: 156001
The Pega Field Level Auditing gadget was not supporting auditing on Value group and Value list property modes, generating the error “The Flow Action pre-processing activity failed: The property was of mode String Group while com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getStringValue(int) was expecting String List mode.” Code has been added to properly handle group and value mode property changes.
_________________________________________________________________________________________________________
SR-110757 ISSUE: 156732
When sorting operator IDs, the resulting page xml was returned displaying the SQL query used to get the sorted list. An enhancement has been added to security/showSQLInListPage to make displaying the query a dynamic setting populated only when security/showSQLInListPage is 'true' (the default value is 'false').
_________________________________________________________________________________________________________
SR-110773 ISSUE: 153721
An issue was found with rule check-in where the WorkPage was created with the obj-class Work-ProjectManagement-CheckIn, but the WorkPage was not being deleted from the clipboard when the check-in was complete. This could lead to latent errors in other places, and the WorkPage is now cleaned up at the end of rule-checkin process to avoid this issue.
_________________________________________________________________________________________________________
SR-110773
ISSUE: 160105 / ISSUE: 163339 / ISSUE: 163400 / ISSUE: 163433
When New, SaveAs, and Delete were performed on a WorkPage, the clipboard was not clearing correctly after check-in, causing the data to be incorrectly reused. In some cases, an exception was thrown when clicking 'edit'. WorkPage now has an additional check for error messages at end of rule check-in to avoid this issue, and will delete the clipboard only if it is no longer in use.
_________________________________________________________________________________________________________
SR-110796 ISSUE: 157428
In some cases, running a flow in the upgraded instance chrt-24.pegacloud.com gave an error in the search screen. This navigation error has been fixed.
_________________________________________________________________________________________________________
SR-110799 ISSUE: 156350
After adding a new row in a Repeat Grid and then pressing the discard button, any further attempt to expand an existing row caused a "target is undefined" javascript error. The handling for canceling a flow action has been smoothed to clear this problem.
_________________________________________________________________________________________________________
SR-110842 ISSUE: 156208
When using an OOTB Date Control in Firefox and selecting a date for next year (1 calendar year difference), hitting “Submit” caused the system to hang without generating any error messages. This was traced to the input type of 'image' causing an infinite loop in the core Firefox code, and the markup has been modified to use an anchor tag instead.
_________________________________________________________________________________________________________
SR-110855 ISSUE: 156925
While creating a Product rule, if the List view mentioned under the ‘List View Filter’ has a circumstance, the base version was picked up during export of the Product and the circumstanced rule was ignored. Previously, the circumstance template required a designated primary page to function. The system has been changed to create a temporary primary page if one does not exist so this process will complete without error.
_________________________________________________________________________________________________________
SR-110862 ISSUE: 157593
When using a repeat grid with collapsible headers, using an "Expand When" condition defined on the headers was not honored. The issue was with identifying the index of reload element when repeat grid is expanded and refresh is triggered, and the code has been modified to resolve this problem.
_________________________________________________________________________________________________________
SR-110882 ISSUE: 154370
When adding a Link to a Rich Text Editor Control in a Section, a set Target was being lost and opening the configured Link showed the Target reset to no value. This issue was due to a missing target name field, and has been fixed.
_________________________________________________________________________________________________________
SR-110930 ISSUE: 155339
When using Internet Explorer 8 and performing an Application Import of an archive containing schema changes, the expand icon used to view the table of proposed updates caused an "Error on page" notification to appear and the contents failed to display. This was caused by the java code making a check for an element not supported by Internet Explorer 8, and has been changed.
_________________________________________________________________________________________________________
SR-110935 ISSUE: 153267
When the harness is set to show icons with tooltips for field level error, left padding was added to the CSS to ensure user entry into the field did not appear behind the error icon. However this makes the assumption that all harnesses use 'icon' display for error messaging rather than full text error messaging, and this style has been made conditional to ensure proper behavior under varying conditions.
_________________________________________________________________________________________________________
SR-110965 ISSUE: 153681
In the Case Manager portal, on the MyCases tab and the MyReports tab, the error message “Cannot render section” might be displayed. A local customization on one of the tabs of Dynamic Container to use a FlowAction rule from the Work class rather than from the Data-Portal class caused an issue with displaying all of the tabs for the portal. This was related to the customization changing the Primary page class name and that class flowing down to the other tabs. The system has been enhanced to scope the processing of the flowaction to just a harness, to avoid encompassing the Portal context.
_________________________________________________________________________________________________________
SR-111004 ISSUE: 153265
A difference in the hotfix tags used for V6 and V7 releases caused the System Scanner to inaccurately determine which hotfixes were installed or available for V6 maintenance level systems. It was still possible to install the appropriate hotfixes and the ‘Hotfix Status’ landing page accurately showed which hotfixes were installed, but the cataloger issue that caused incorrect ML results from system scans has been corrected.
_________________________________________________________________________________________________________
SR-111005 ISSUE: 154453
Previously, the Designer Studio RSS feed was hard-coded to use HTTP when accessing pdn.pega.com. This caused a problem for sites requiring the use of HTTPS. An enhancement has been added to allow overriding the URL for the PDN RSS feed.
_________________________________________________________________________________________________________
SR-111026 ISSUE: 156881
In some situations, the mandatory fields in a screen created PDFs with the text “Required” appended in the labels. This was caused by the Required tags from the markup being passed to the HtmlToPdf activity, and has been corrected.
_________________________________________________________________________________________________________
SR-111043 ISSUE: 157566
With paging disabled, filtering for datetime and decimal properties was not working for list views. This was related to a missing data-type attribute for filter button during list view generation, and has been fixed.
_________________________________________________________________________________________________________
SR-111047 ISSUE: 156838
Container Managed Transaction mode did not allow explicitly setting auto commit, and attempting to call setAutoCommit() caused the error “Problem saving Java sources to database java.sql.SQLException: You cannot set autocommit during a managed transaction!”. An enhancement has been added to the engine code to validate whether the transaction is container or bean managed, allowing the use of auto commit for CMT.
_________________________________________________________________________________________________________
SR-111111 ISSUE: 154330
Lock and roll functionality was showing an error on the screen and would not allow the lock of rulesets when the Pega-BIX or Pega-Social ruleset was part of the application rule. This was caused by a conflict in permissions for the rules being validated, and an exemption has been added for these rule sets.
_________________________________________________________________________________________________________
SR-111158 ISSUE: 157558
It was possible to use the 'View/Edit in Word' link when a specification rule was in a locked ruleset (checkout enabled or disabled). This appeared to be an effective way to make changes, but any changes made to the rule in Word were lost when the rule was checked out or the ruleset was unlocked. The preferred way to edit the rule is to type into one of the fields directly on the form, then click checkout. To avoid confusion, the 'View in Word' link will now be hidden in locked specifications when RTE is available and will only be displayed in case RTE is hidden so that the rule may be viewed.
_________________________________________________________________________________________________________
SR-111231 ISSUE: 158946
When creating a tree grid with a repeating grid embedded pane as the edit option, every first click in the tree grid was showing the correct data in the repeating grid but subsequent clicks would not show the existing data. This was a tree grid pagination error, and has been corrected.
_________________________________________________________________________________________________________
SR-111238 ISSUE: 154158
In a report definition, unchecking the 'Display Report Header' caused the filter criteria to not show on the report or the exported PDF while it would show if the data was exported to Excel. The HTML has been modified to conditionally display the criteria filters properly.
_________________________________________________________________________________________________________
SR-111262 ISSUE: 155949
Previously, XMTreeViewBuilder only supported circular references of complex types in xsd and not circular references of groups. Attempts to use WSDL circular group references caused the import to fail. An enhancement has been added to the handling in XMLTreeViewBuilder to support circular group references.
_________________________________________________________________________________________________________
SR-111272 ISSUE: 155321
When configuring the parameters for the format of currency values in a report definition column using the Currency control, the dialog could not be submitted. Instead, a browser popup appeared stating "Please correct flagged fields before submitting the form!", but there were no flagged fields. The "Separators" option also appeared twice on the dialog. This issue was due to 'Run On Client' being selected for a hidden Other Currency field's visibility condition. Even though the field was not displayed, the client-side evaluation was still picking up the field's required setting and preventing the submit. The Separators radio buttons was configured twice in the same section with the save visibility conditions. These have been fixed.
_________________________________________________________________________________________________________
SR-111288 ISSUE: 155389
When localizing the OOTB Case manager portal, the the period ranges and Workgroup names were not being properly localized. The Workgroup label had been inadvertently left hard-coded, and has been corrected to localize properly.
_________________________________________________________________________________________________________
SR-111327 ISSUE: 157332
In Firefox, opening a popup page to run obj-validate for null values and clicking Save caused error messages to appear in the popup. This was a problem with the handling of the source element event, and the code has been changed to use a multi-browser API to get the element and display it correctly.
_________________________________________________________________________________________________________
SR-111363 ISSUE: 158720
Making a SOAP call from PRPC to an HTTPS webservice URL that is secured using FIPS 140-2 standard and requires TLS encryption protocol resulted in a 'Connection Reset' error. The issue has been resolved by making a WebSphere configuration change to enable FIPS, and adding the selection of TLS protocol from Connect-SOAP -> Advanced tab.
_________________________________________________________________________________________________________
SR-111368 ISSUE: 156879
Previously, SpecsForWorkType had a paging limit of 50 for retrieving specifications for each work type. This has been increased to 10000 to allow handling complicated case types.
_________________________________________________________________________________________________________
SR-111383 ISSUE: 156316
When attempting to default to Internet Explorer Document Mode in Internet Explorer, the application instead defaulted to "Quirks” and the orientation was distorted in places. There was a workaround of pressing F12 and manually selecting Internet Explorer 8 to display the screens correctly, but the problem was traced to the logic used for inclusion of the different data sources, and has been changed to work more smoothly in Internet Explorer 8.
_________________________________________________________________________________________________________
SR-111425
ISSUE: 154851 / ISSUE: 155373
When trying to create SOAP connectors by launching the SOAP Integration wizard, choosing WSDL was not working: after selecting the file using the browse button the file name appears in the text field, but pressing 'Next' blanked the field and produced the error "This record has 1 error. Source Location: This field may not be blank." While there was a workaround of using WSDL via URL, attaching the file has been fixed.
_________________________________________________________________________________________________________
SR-111453 ISSUE: 155333
The Report Source Max value was previously set to 500 in the final rule DisplayShortcutsForSearch listview. This caused an issue with truncating the report list if it exceeded the max value. The max value has been increased to 5000.
_________________________________________________________________________________________________________
SR-111471 ISSUE: 154897
If a field level validation fails and a page-set message is set-up, the page-set message appeared even on the audit window. The HistoryAndAttachments Harness showed error messages if they are any errors present on Work Page, but the activity has been updated to not display the errors while loading the harness itself.
_________________________________________________________________________________________________________
SR-111490 ISSUE: 158401
Previously, the Report Definition aggregate function (summarize function AVG, SUM, etc) only allowed a two-digit DecimalPrecision qualifier (x.xx). Some customers wished more precision (i.e., more decimal points). There is now functionality which allows more decimal places.
For the property pySummaryValue, the UI control specified is formatSummaryDecimal. Copy the pySummaryValue property into your RuleSet, and clear out (delete) that UI control from the property. Then on the Advanced tab of pySummaryValue, in the Property Qualifiers section, click the “+” to add a qualifier. Add the qualifier pyDecimalPrecision, and in the Value field, type the number of digits you want after the decimal point. Save your changes.
_________________________________________________________________________________________________________
SR-111513 ISSUE: 158388
Attempting to call showHarnessWrapper during application implementation was causing a "no such method fixBaseThreadTxnId" error. This was traced to fixBaseThreadTxnId not being correctly initialized when showHarnessWrapper is called, and a check has been added to ensure proper behavior.
_________________________________________________________________________________________________________
SR-111531 ISSUE: 157040
After customizing the case manager portal to include the TagCloudSection, the UI was not displaying properly with a dynamic layout. The issue was caused by a conflict in handing page names, and has been resolved.
_________________________________________________________________________________________________________
SR-111532 ISSUE: 157140
In an activity, setting value on a "single value/text" property using Property-Set method after the property had been deleted from the database caused an embedded page to be created instead of value being set a scalar value. The property handling has been modified to correct this incorrect behavior.
_________________________________________________________________________________________________________
SR-111549 ISSUE: 157903
In a normal PRPC login, clicking 'TagCloud' produced the expected results. However, in IAC, while the tag cloud loaded and could be viewed normally, clicking one of the tags produced a JavaScript error and nothing was loaded. This was caused by getDesktopWindow returning a null value that was being used to compute operations. An "if" condition has been added to check whether getDesktopWindow is defined in order to resolve this error.
_________________________________________________________________________________________________________
SR-111562 ISSUE: 159151
When using Export to Excel for LIstView, attempting to update the data in the new Excel sheet generated the error "The cell or chat that you are trying to change is protected and therefore read-only". This is caused by a Microsoft change in paste behavior defaults for the latest versions of MS-Office that automatically set the copied cells to be write-protected. There was a workaround of unprotecting the worksheet, but macrocode has been added that explicitly unprotects the editable range after the paste to override the unwanted new Excel behavior.
_________________________________________________________________________________________________________
SR-111583 ISSUE: 155599
When there was an element in the stream rule not populated with any values but also not marked as optional, it was not appearing in the output XML. The code has been updated to pass the empty element correctly depending on the optional flag.
_________________________________________________________________________________________________________
SR-111593 ISSUE: 157702
In GetGridColUniqueValues activity, the class of an embedded page group was not determined properly, resulting in filters for the Grid Layout not working on embedded pages. Code has been added for proper computation of the class.
_________________________________________________________________________________________________________
SR-111692 ISSUE: 158930
Declarative network updating was altered such that it was updating on events that did not previously trigger updates, such as using Page-Change-Class to change the class of the WorkPage. This timing may not be desirable in cases where customer-required conditions have not yet been met, so a checkbox has been added as a new parameter in the Page-Change-Class acitivty step which can be used to skip declaratives.
_________________________________________________________________________________________________________
SR-111696
ISSUE: 157472 / ISSUE: 160247
An error was displayed when attempting to check out a section containing a Grid Repeat, where a change in the Report Definition referenced by the Grid Repeat caused an error with the Grid Repeat. This was caused by incorrect system behavior that allowed a rule containing errors to be saved to the database without validating the changes and presenting any errors. The system has been updated to allow checkout of rules with errors, but validation has also been enhanced to prevent future problems.
_________________________________________________________________________________________________________
SR-111704 ISSUE: 158775
An enhancement has been added to allow for the use of an icon to launch an action within a collapsible header without the action being auto-launched when the report is triggered. The auto-generated Icon control has been modified so that added icons are excluded from the expand/collapse functionality, but the expand/collapse icon remains functional. There is also an accompanying check for the data-click attribute on the new icon to ensure that it has an action associated with it.
_________________________________________________________________________________________________________
SR-111715 ISSUE: 160753
The Application Express wizard allows spaces in the Organization Name, Division Name, or Unit Name field, but if the field was expanded and names with spaces were entered at that point, the save would fail and present an error saying spaces were not allowed. The correct behavior is to allow spaces, but it the enhancement implementation was incomplete and has been corrected.
_________________________________________________________________________________________________________
SR-111730 ISSUE: 157461
Attempting to use FTP generated the error message "provided blank value for 'Host Name' field" even when the host name field was given. This has been corrected.
_________________________________________________________________________________________________________
SR-111777 ISSUE: 158677
If Tabbed Repeat contained a Tabbed layout and more than one tab inside the tabbed repeat, only the data of the first tab was displayed and the other tabs appeared frozen. This was an issue with the check for scrollContainerElement, and the code has been adjusted to resolve this issue.
_________________________________________________________________________________________________________
SR-111842 / SR-110372
ISSUE: 155349 / ISSUE: 159008
In some circumstances, images in HTML were not appearing when a PDF was generated. This was due to missing requestor type information, and has been corrected.
_________________________________________________________________________________________________________
SR-111927 ISSUE: 156588
While using a service package that doesn't require authentication, there was a problem with calling activities with "require authentication" enabled from the service activity of SERVICE-REST: resuming the flow from Service-REST generated the error “only authenticated users can access this activity”. The authentication requirements have now been adjusted to match the package being used so the flow can be resumed without error.
_________________________________________________________________________________________________________
SR-111935 ISSUE: 156040
When a data transform rule was invoked from a connector in a flow and referred to a param page without setting the param value in the properties on the flow, a Null Pointer Exception error was thrown. To fix this, the rule-utility-function flowfua process connector has been modified to use the current parameter page for the parampage variable rather than creating a new param page, ensuring current parameters are available for use by the data transform.
_________________________________________________________________________________________________________
SR-111944 ISSUE: 159826
Chart headers were getting removed after drilling down on a pie chart and then maximizing it. This was an error in the XML values used for tracking changes in displaying graphs, and the code has been updated to properly retain the header information.
_________________________________________________________________________________________________________
SR-111964 ISSUE: 161887
Attempting to save a report-definition name with hyphen or space generated an exception message. This message has been changed to read "This may only contain letters, digits, underscores and must begin with a letter." In addition, trying to save a report-definition to a name that was already present showed an obscure error message in the grey background, not in the pop up. This message has been changed to read "A report with this name already exists", and the Rule-Obj-Report-Definition function has been changed so it checks to see if the report name is valid shortcut rule name, and any error message is shown inline in the dialog.
_________________________________________________________________________________________________________
SR-111968 ISSUE: 156932
Certain ARIA attributes were missing on the error span, causing error message validation to not be picked up by Jaws or ZoomText and requiring a reading key to search for the messages. To ensure that error validation messages on activation are displayed, changes were made to AddMessages RUF to handle server side errors and ARIA attributes were added to pega_validators for client side errors.
_________________________________________________________________________________________________________
SR-111994 ISSUE: 157290
When cloning an Access Role Name, the new Access of Role to Object instances were created with Ruleset Versions. This incorrect behavior caused problems when attempting to update the instances, and has now been corrected.
_________________________________________________________________________________________________________
SR-112058 ISSUE: 157527
When using Case Manager-> Bulk Actions, the actions and list of work objects subject to the actions need to be selected before execution. Because GoBack is an auto-submit flowaction, attempting to use GoBack as part of a Bulk Action flow resulted in JavaScript errors because it would run despite not having any relevant work objects selected. A check box has been added to the action tab to disqualify GoBack during bulk actions.
_________________________________________________________________________________________________________
SR-112073 ISSUE: 155931
When using radio buttons inside a section with On Click/ On Change "Refresh Section" behavior on the radio buttons, placing that section inside a repeating grid failed to trigger a Refresh Section when the button's label was clicked. It did trigger if the radio button was clicked. This was caused by the label associated with the radio button not having a data-click attribute generated. This has been added, along with a check for any undefined label element.
_________________________________________________________________________________________________________
SR-112079 ISSUE: 157226
When a RAP file was exported from a multi-tenant environment and then imported into another multi-tenant environment, a problem occurred if Data-Rule-AppMetaData instances already existed in the target system. The TenantID property should not have been included in the instance when saving, and the code has been corrected to remove this conflict.
_________________________________________________________________________________________________________
SR-112090 ISSUE: 162492
The Purge and Archive wizard appeared to not be working as expected even though it was performing correctly. This issue occurred because the Engine API ExportImpl.performExportKeys() was returning false (which indicates some error) even though the export was actually successful. This has been corrected so the work done is reported accurately.
_________________________________________________________________________________________________________
SR-112122 ISSUE: 158684
After saving a field value in a higher version with availability = 'Withdrawn', the field value was still appearing in the prompt select options dropdown list. Removal of duplicates is generally done based on the property InsHandle, but the property is not always present on the page. The rule-utility-function has been modified to resolve based on InsKey in the absence of InsHandle, eliminating this error.
_________________________________________________________________________________________________________
SR-112147 ISSUE: 162872
After a modal dialog was launched from a local action and resized to make it smaller, a dropdown in the modal dialog makes more layouts visible in the modal dialog, but selecting a value from the drop down removed the re-size icon and OK/Cancel buttons. Upon resizing modal body, the system was not resetting height and width of modal container. The code has been modified to correctly reset the height.
_________________________________________________________________________________________________________
SR-112156 ISSUE: 158051
When creating a new application via the App Express using an existing organization to generate reusable division records for a new division, the wizard was throwing an invalid ruleset version error. This occurred when a new application was created for an organization whose Org ruleset had a higher ruleset version than the OrgInt ruleset, and the issue has been resolved by updating SetOrgIntRuleSetDefaults to appropriately set the parameter for 'get highest version' to be the AppRuleSetOrgInt instead of the AppRuleSetOrg ruleset version.
_________________________________________________________________________________________________________
SR-112167 ISSUE: 163769
When a requirement was added to validate the fields in the flow action section, submitting the flow action (i.e moving to an another node in the tree) displayed the validation errors on the top of the harness and the flow action section content was displayed as blank section. This problem only occurred when the grid control used option "edit pane" or "expand pane", and did not appear with "modal dialog". This issue was traced to having two embedded pane grids updating the same “newModalPage.pyInterestPage” property if the validate rule in the flow action for grid1 evaluated to false. To fix this, the handing in SubmitModalFlowAction has been modified.
_________________________________________________________________________________________________________
SR-112223 ISSUE: 157501
When using a data page to call a Connect SQL rule in PRPC 7.1.5 and there is no Response Data Transform, the resulting class was the class of the Connect SQL rule instead of Code-Pega-List. CallConnector activity decides the context in which data transform should run. Previously, it was setting to Connect SQL class - this has been changed to create a page of Code-Pega-List if there is no response DT Transform for list type SQL connector.
_________________________________________________________________________________________________________
SR-112254 ISSUE: 158980
Image references in the Rich Text Editor were not considered valid by an IAC Gateway because they lacked the "Application" part of the URL. For RTE images, the URL format is different when compared to the staticcontent requests. This difference was not previously handled in the Gateway code, and has been added.
_________________________________________________________________________________________________________
SR-112265 ISSUE: 158868
The visibility "when" condition used for an image cell in PRPC 6.3 was not properly transitioned for use in version 7. The data existed in the upgraded system and there was a workaround of changing the control from Image to Icon, but the clipboard location for Image was not referenced. The UI has been updated to display the correct conditions for the the Image cell.
_________________________________________________________________________________________________________
SR-112284 ISSUE: 157987
After a change is made to the start time information for a recurring agent and the agent schedule is deleted and regenerated, sometimes the schedule has an incorrect value for the agent start time. This was caused by misintepreting the combination of StartHour and StartAmPm when using a 24 hour clock, and has been fixed.
_________________________________________________________________________________________________________
SR-112326 ISSUE: 157867
The local action defined on the 'click' event of an icon was not displaying the modal dialog in the portal. Workarounds included updating the flow or flow action to run a data transform before loading the grid that contains the icon or calling a flow action from the same class on click and then setting the page context in that flow action to point at another class, but the system has now been updated to set the correct class and display the dialog as expected.
_________________________________________________________________________________________________________
SR-112332 ISSUE: 160928
It was possible for custom Access Role changes to create a LockGoneException for OnSend that would sporadically resend duplicate emails. The function obj-save-cancel has been added to avoid Queue Manager rolling back the transaction on a failed save.
_________________________________________________________________________________________________________
SR-112346
ISSUE: 157526 / ISSUE: 160405
In the Case Manager Portal reporting tab, it was possible to open a report from from standard category and change the filter criteria, then save under the same report name in the personal category. Subsequently, anyone opening the report from the standard category obtained the new personal report instead of the standard report. To avoid this, the system will now require selecting a unique name when saving a report to a personal category and will present an error if a report with the given class+name already exists.
_________________________________________________________________________________________________________
SR-112412 ISSUE: 162164
Values were incorrectly mapped in the clipboard during an Excel file upload, with values defined as page level properties instead being mapped to Results or any page list property defined in the template. This was caused by a missing condition to check how the result table ends, leaving all page level properties to be mapped to the result list. To fix this, the code has been modified to remove empty rows from the result table and keep no empty rows between the result table and the static content, and a hidden row will be added at the end of page list property values to tell the system where exactly the page list property values end.
_________________________________________________________________________________________________________
SR-112413 ISSUE: 161950
If the mandatory Standard element of PageList mode is not available in the clipboard at run time, then the XML stream is not able to generate empty tags for mandatory elements (which are generated from XSD file with minOccurs=1 and/or maxOccurs=unbound via Connector and Metadata wizard), and the pagelist to which the repeating elements is mapped is not populated with any data. This issue is resolved by code that has been added to create an empty page in the Page list with the help of XMLTreeViewUtils.java, in case of repeating elements marked as mandatory by not checking isOptional check box on the element of a XMLStream rule.
_________________________________________________________________________________________________________
SR-112447 ISSUE: 156839
After recording (i.e. testing and logging what activities and other rules have been executed during the warn step) and applying to an access group, the access group was locked down even if 'allow' or 'warn' were selected. In addition, not all activities were picked up when recording. In order to correct this, the activity RuleExecutionMessagesLogged has been modified to create the new RARO with permissions copied from ancestor RARO.
_________________________________________________________________________________________________________
SR-112450 ISSUE: 162961
An enhancement has been added to extend the behavior of AddWorkHistory with an extension point.
_________________________________________________________________________________________________________
SR-112457 ISSUE: 160408
Dynamically composing URLs based on various work types (WorkCaseKey) did not always work due to SafeURL_createFromURL not being able to handle partially encrypted URLs. An enhancement has been added to the SafeURL_createFromURL js function in safeURL.js to process partially encrypted strURLS.
_________________________________________________________________________________________________________
SR-112584 ISSUE: 159318
Attempting to create a decision tree with a string literal value (enclosed within double quotes) resulted in errors due to the value being treated as a class.property expression despite the double quotes. This was an error in the parsing of the return value that did not check for double quotes, and has been corrected so the system will pass it as a string literal as intended.
_________________________________________________________________________________________________________
SR-112622 ISSUE: 160678
Attachments sent by HTTP request from SoapUI were not being processed correctly, though the attachments were accessible if the request was sent from PRPC using Connect-HTTP. The java parser for multipart messages has been updated to fix the issue.
_________________________________________________________________________________________________________
SR-112693 ISSUE: 159839
During hotfix installation, each HFIX jar was previously unpacked into the same directory. When multiple hotfixes have the same file names included, such as Pega-ImportExport.jar, the files were overwritten and the Update Manager was not able to perform as expected. To avoid this issue, each hotfix jar within a DL is now unpacked into its own temporary directory based on HFIX-ID.
_________________________________________________________________________________________________________
SR-112698 ISSUE: 160447
When creating or maintaining Strategy rules using Internet Explorer 8, attempting to create connectors between shapes by dragging a line from the source shape to the target shape instead moved the shape. The mouseMove method of ConnectionHandler has been modified to perform correctly.
_________________________________________________________________________________________________________
SR-112721 ISSUE: 161292
When running the Product Migration wizard on an HTTPS port, the wizard would fail and log an exception. The activity uses the inputStream available*() method to determine if the file has been completely read, but this method returns 0 in a SSL socket because it cannot block to determine the actual amount of data that is available to be read. To enable HTTPS use, the activity has been changed to use the bytes-read return length to determine if end of file has been reached.
_________________________________________________________________________________________________________
SR-112758 ISSUE: 157751
In Read-Only format, a Declare expression symbol was always positioned on the left even if the symbol position was set to right. This was due to the symbol position not being correctly handled, and has been fixed.
_________________________________________________________________________________________________________
SR-112790
ISSUE: 160160 / ISSUE: 160856
Certain business Calendar functions like nextBusinessDay and addDays were not working properly when a custom Calendar had EST passed as parameter. This was caused by a conflict in formatting between the default and custom calendars, and has been corrected.
_________________________________________________________________________________________________________
SR-112792 ISSUE: 157938
When "required" is checked and a read-only when/expression was selected from edit options, there was no respective field to enter the when rule/expression. The code has been modified to allow this edit.
_________________________________________________________________________________________________________
SR-112856 ISSUE: 160344
For RuleSets with a large number of rules and RuleSet Versions, the All-Rules count for a version was showing as zero even though were rules present in a RuleSet Version. This occurred because the Maximum Number of Rows to Retrieve defaulted to 500, meaning the system would only count rules for the first 500 versions regardless of how many actually existed. In other cases, RuleSets with fewer versions but very large numbers of rules in the RuleSet were timing out. The Maximum Number of Rows to Retrieve has been greatly enlarged (to 500,000) so that customers will always get an All-Rules count, and Elapsed Time has been adjusted to ensure the function will complete.
_________________________________________________________________________________________________________
SR-112866 ISSUE: 159434
When switching from the Review to Perform harness by selecting a flow action from the Actions menu, the wrong flow action could be displayed if the list of available actions was different between the two harnesses (i.e. by using visible 'when' conditions on the flow action configuration). The was caused by the navigation rule running against an index rather than a ID for the flow action: before invoking the FA, the list is re-indexed so the option the index points to can change. To fix this, SetActionProperties was modified to ensure that if NewTaskStatus param has a value, the TaskIndex param is correct for it.
_________________________________________________________________________________________________________
SR-112878 ISSUE: 159137
In some cases, the scroll bar for the left panel disappeared after hiding the left panel. This has been fixed by re-positioning the scroll bar using CSS.
_________________________________________________________________________________________________________
SR-112912 ISSUE: 157896
When class groups BASE-B and BASE-C are listed in that order on details tab of rule-app, both with new-work checkbox, they appear on new-work dropdown in that proper order on CaseWorkerPortal. However, if BASE class group was added as the first item in the details tab without the new-work checkbox, then the order of the two items changed in the new-work dropdown. This was fixed by changing the GetStartingFlows activity to fetch all the processes of all workpools at once and then append them to the starting flows according to the order of cases listed in app rule.
_________________________________________________________________________________________________________
SR-112916 ISSUE: 158367
During daily shutdown of Tomcat 7, SEVERE logs were written to catalina.out indicating a possible memory leak due to threads not being properly resolved. This was a dual issue with PRPC and Apache. The PRPC memory issue has been resolved by using VicariousThreadLocal (which uses soft references) instead of java.lang.ThreadLocal. The Apache team addressed the issue in their log4j release version (log4j-1.2.17.jar), which has been incorporated into PRPC.
_________________________________________________________________________________________________________
SR-112928 ISSUE: 159782
When displaying a chart via report definition where the category axis shows time value in HH:mm format, two different time zones were appearing on the axis and the "Show Data" button on the chart display. There was an error in the generation of the fusion chart XML that did not properly take into account the Operator's defined time zone (timezone on the operator rule), and this has been corrected.
_________________________________________________________________________________________________________
SR-112934 ISSUE: 158415
When the Enable expression calculation was checked on Harness and flow action, a Safe URL-related Error popup window appeared during run time and all Declare events failed. This occurred because the metadata was contained in an array that was not supported in the API, and the format has been changed to a modifiable list to resolve the issue.
_________________________________________________________________________________________________________
SR-112936 ISSUE: 161706
A problem was found with creating new Rule Set versions where pyUsage was not being copied over from the RuleSet-Name record. If a Warning message was defined on pyUsage and filed at Rule- level, then a Warning message was created for the missing pyUsage field even though the History tab on the RuleSet form showed Usage and Description being filled. To correct this, the value of Usage will be the same as the RSV's description. Additionally, Warnings for a RSV were being saved to database only when the RSV was created using Quick Create/Create and Close options. This in turn was leading to inconsistencies in Guardrail reports. This has been modified so warnings associated with an RSV will be saved to the database.
_________________________________________________________________________________________________________
SR-112973 ISSUE: 158186
A single activity specified as a Pre-Load activity on a tabbed layout section was being executed twice when clicked. This was caused by the pre-activity of defer load in tab group being called in two different RUFs (GENERATESECTIONBODYHTML and GenerateSimpleLayoutHTML), and has been fixed.
_________________________________________________________________________________________________________
SR-112985 ISSUE: 158082
While using the Service Wizard, some page properties came across as children when they are actually siblings. Additionally, after choosing ruleset and service package, the harness showed the customized message "This is a new 7.1 end-user harness. Best practice is to customize..." etc. and the Service Wizard generated a Null Pointer Exception and failed to create the rules. The inheritance mapping has been corrected, and the recursive error causing the NPE has been resolved.
_________________________________________________________________________________________________________
SR-112988 ISSUE: 161431
When using the Modal Dialog to edit a grid created with header layout format 'B' and Header Type 'Bar', dismissing the Modal Dialog and returning to the grid in the parent section showed the layout header twice. This was a conflict in the handling: when using Header Type 'Bar' with "Refresh on update" checked, both the header and body were supplied in the response. This has been corrected.
_________________________________________________________________________________________________________
SR-113024 / SR-113388
ISSUE: 98681 / ISSUE: 161135 / ISSUE: 161298
During passivation, the serialized pages and threads are each stored as a separate file in the file system using their names as the file names. If the name exceeded 248 characters, attempts to reactivate the page failed with a runtime exception and it was placed back in the queue. Eventually, OOM errors would occur due to too many bad queue items. The passivation daemon has been modified to catch the IOException and handle it properly so that requestor passivation can still occur with long thread id. This will allow the system to skip the queue item and not allow the queue to fill up.
_________________________________________________________________________________________________________
SR-113026 ISSUE: 159758
After dragging and dropping an attachment, selecting category value caused a null value to flash momentarily before the category value was displayed. This was caused by the caption being set as a null value until the list is populated, and a check against caption has been added to properly validate and display the value in the dropdown.
_________________________________________________________________________________________________________
SR-113049 ISSUE: 158724
On the Service Package rule, checking the Customer Target Namespace checkbox on the deployment tab did not present the field to enter the namespace. As a result, it was not possible to save as long as the 'mandatory' checkbox for this field was active. The JavaScript function to present the field for editing has been corrected.
_________________________________________________________________________________________________________
SR-113050 ISSUE: 161023
Rule harvesting to create a Map value was displaying an issue around the conversion of decimal values when using Edit In Excel. This was caused by a defect in the connection string of the macro code in the template, and it has been corrected to parse the decimal header correctly. It was additionally noted that PRPC fires a validation on the auto-generated Map value rules when the Check Out button is clicked, effectively blocking further edits after creation. This is correct: due to check out, validation is an expected behavior in 7.1 because the Rule-Obj-MapValue rule cannot be empty (at least one row of data is required).
_________________________________________________________________________________________________________
SR-113054 ISSUE: 160656
When a failure occurred during transferring assignments using Bulk Actions, the pop-up box displaying the reason for the failure was blank. This issue was traced to a missing function in the activity BulkProcessItemsInHarness, has has been fixed.
_________________________________________________________________________________________________________
SR-113071 / SR-113751
ISSUE: 158817 / ISSUE: 160078
Using the OOTB control "Radio buttons" to display CMS related indicators in a repeat grid was not working properly with the clipboard onclick of 'delete icon', and the incorrect value was being blanked. This issue occurred due to duplicated radio button naming, and the handling has been corrected.
_________________________________________________________________________________________________________
SR-113163 ISSUE: 160007
When creating a case for Adhoc Product, two instances of Adhoc Service Order were being created. This was an issue with the implementation layer lookuplist activity which is called to get the starting flows for a case, and the Casetype generation code has been modified to eliminate duplicates from the master list.
_________________________________________________________________________________________________________
SR-113189 ISSUE: 159446
A Declare page at node level could become corrupted and generate NPEs if it contained a null value for the getcurrencycode activity. A null check has been added to XMLStream.java to avoid the NPE and continue with the next property, nd null values will not be added to the PropertyCollection.
_________________________________________________________________________________________________________
SR-113281 ISSUE: 161600
If a "Notify Party" escalation action was specified on an SLA, when the SLA milestone lapsed the execution of the action did not result in the email being sent. If the SLA escalation action was changed from "Notify Party" to "Run Activity", and that was configured to run the standard "NotifyParty" activity (from Work-), the NotifyParty activity would run and send the email. This was caused by the "Notify Party" SLA escalation action being inconsistently implemented, and has been fixed.
_________________________________________________________________________________________________________
SR-113288 ISSUE: 161326
If a section was designed with both TextArea and TextArea controls, work object content in that section was shrunk when it was opened. Refreshing the tab stretched the content and resolved the shrinkage. This was caused by the getDocumentHeight not being initialized if the "pega" object didn't exist. The code has been modified to get the correct document height if "pega" is not initialized.
_________________________________________________________________________________________________________
SR-113307 ISSUE: 161034
Sorting defined in the Report Definition was being overridden if categorization in grid repeat was used. The GenerateGrid HTML has been modified to sort a categorized RD grid correctly.
_________________________________________________________________________________________________________
SR-113325 ISSUE: 162088
After running a listview, when choosing the Export to Excel the resultant export file contain a hidden blank row. This interfered with being able to apply a filter in Excel unless this row was manually removed each time, and it has been corrected.
_________________________________________________________________________________________________________
SR-113386 ISSUE: 160357
When using the OOTB Audit window from either Case Manager or Case Working portal, " " was being appended to the names of tabs. This was caused by the accidental hard coding of " " in each tab header, and has been fixed.
_________________________________________________________________________________________________________
SR-113400 ISSUE: 160487
DBTrace revealed that creating a case was performing an unnecessary browse to validate case type. To improve system performance, CaseType rule is now accessed using a method that supports caching instead of getting it from the database.
_________________________________________________________________________________________________________
SR-113455 ISSUE: 136913 / ISSUE: 161514
Attempts to use autocomplete in a report definition with "Display Best Bets" checked generates a "parentNode is null" JavaScript error when using the control at runtime. The workaround was to uncheck the box, but this issue has been fixed.
_________________________________________________________________________________________________________
SR-113487 ISSUE: 159942
Some areas of Pega-ScheduledTask-Reporting were not properly localized. This has been corrected.
_________________________________________________________________________________________________________
SR-113602 ISSUE: 159896
In some circumstances, executing outbound SOAP connections was causing poor performance for inbound connections. After investigation, it was determined that duplicated batch output properties in the output table slowed system performance. The batch output hierarchy has been changed so as to no longer create the properties in each class, but rather find these properties via inheritance. To this end, the top level SR class must now have Data-Decision-StrategyExecution-ResultOutput as its directed parent. Each batch output class (both program run and event) will now have the appropriate SR class as its directed parent.
_________________________________________________________________________________________________________
SR-113657 ISSUE: 160044
Field Level Auditing was showing duplicate entries for Value Groups and Value Lists if the flow was saved multiple times without any intermediate actions before clicking audit. This was caused by the function handling: while adding history memos for ValueList/ValueGroup, the function removed previous values after checking whether the values were changed or not. When the save was performed a second time, the previous value were removed, and a third save caused values to be treated as added. To prevent this, the AddHistoryMemosForStringList function has been modified to check whether values changed or not and has an added condition to update the previous property list with current values.
_________________________________________________________________________________________________________
SR-113687 ISSUE: 161102
If the "%" symbol was present in the Input Text field, passing it to a new harness using the button onclick eventDisplay in New Document was generating a JavaScript error. The resultant Java exception has been fixed by adding a catch block for IllegalArgumentExceptionchanging to UIActionDisplayHarness and passing the value as-is for the rest of the processing.
_________________________________________________________________________________________________________
SR-113690 ISSUE: 163654
In some cases, the OOTB "RadioButtons" control was working intermittently if there was no display condition and it was set to be visible always. This behavior happened when an empty string was sent as an argument to the ClipboardPage "getStringIfPresent" API, so a check has been added to avoid calling the API if the property reference is empty.
_________________________________________________________________________________________________________
SR-113702 ISSUE: 162126
When joining two tables in a summary view and selecting a field in the customize criteria, the error "Property XXX is not a Database column" was generated and a duplicate entry appeared in Summary View. This has been fixed by modifying Rule-Obj-HTML • Wizard_Parameters to clear the temporary page list between processing joins and processing index values.
_________________________________________________________________________________________________________
SR-113789 ISSUE: 161675
When a Dynamic Layout was configured with a header/title and the title was configured to reference a property, the generated aria-label attribute in the HTML used the literal property name instead of the value. To correct this, aria-label was replaced with aria-labelledby, which references an element whose text content accurately represents the property value.
_________________________________________________________________________________________________________
SR-113792 ISSUE: 160362
If new agent was set to yearly recurring, attempting to save the agent generated the error "pyYearlyMonth: ** ValueNotInPromptList January pyYearlyMonth" and the save could not be completed. This was caused by incorrect values for the prompt list in the HTML code, and has been corrected.
_________________________________________________________________________________________________________
SR-113794 ISSUE: 161101
Although the short descriptions of specifications were displayed in the sizing spreadsheet, the short description was being set to the specification's full name when stage step was configured with that specification. In this case, the pyLabel was being overwritten with pyPurpose, and that behavior has been eliminated.
_________________________________________________________________________________________________________
SR-113845 ISSUE: 160686
In some usecases, generating an application document was picking up a ruleset that should not have been included in the current ruleset stack. The logic for fetching usecases and requirements based on Application capping has been updated to ensure proper ruleset filtering and inclusion.
_________________________________________________________________________________________________________
SR-113893 ISSUE: 162584
In some cases, saving a class instance could completely hang the browser. After restarting the browser, the class appeared to have been saved, but the associated History class and Database table instance were not created. If a second attempt to save was made, the Pega log file showed a stack dump followed by the error "com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor". In the SQL generator, the call to DatabaseMetaData.getIndexInfo() asked for accurate (non-approximate) index statistics. This caused Oracle to analyze table compute statistics and led to serious performance degradation. The db call has been modified to request approximate index statistics, improving system performance.
_________________________________________________________________________________________________________
SR-113927 ISSUE: 163291
Multiple calls by acquireLock to DateFormat were intermittently leading to Lock Manager errors. For example, if different items were opened on simultaneous multiple sessions in the Perform harness by performing remote debugging on the engine code and setting a breakpoint at the start of the acquireLock method (LockManagerImpl class), all threads would reach the breakpoint and be resumed at the same time. While this didn't show any errors in the logs, the following error (or similar) was appearing on some of the clients: "Error during acquireLock bean method call: codice: <none> Stato SQL: EJB Exception: : java.lang.RuntimeException: Problem during method invocation (acquireLock)" The root cause was the sharing of a DateFormat object. To resolve this, the sharing of the DateFormat instance in the requestor has been eliminated.
_________________________________________________________________________________________________________
SR-113928 ISSUE: 163377
It was noticed that the UI generated for an external assignment (DWA) was fast in Internet Explorer 8, but lagged when clicking radio buttons, check boxes, etc in Chrome or in higher versions of Internet Explorer. The getElementsByName API in (pega_yui_extensions) was programmed to use an XPath query for non-Internet Explorer browsers, but it was having a performance impact with Chrome. In that case, it will now use the getElementsByName DOM API if the root of the search is the document object but will fallback to XPath query in cases where a DOM element is specified as root of the search. The Internet Explorer problem was caused by using the YUI api instead of relying on "element.all" ; YUI api uses getElementsByTagName internally. This is a costly operation compared to element.all, especially when no TAG is specified in the call to getElementsByName, and the handling has been changed to improve performance.
_________________________________________________________________________________________________________
SR-113939 ISSUE: 160640
A 'Certificate chaining error' was being generated when doing a Quick Search of Work in a WebSphere clustered environment using SSL. The root cause is related to WebSphere, but it has been addressed by giving trust Keystore and SSL communication control to PRPC inside the Connect-SOAP rule used.
_________________________________________________________________________________________________________
SR-113968 ISSUE: 162955
When running application express on CPMFS (Customer Process Manager for Financial Services) 7.1.2, , after the cases are selected, the next screen presented the error "Data-Admin-DB-Classgroup does not exist". The issue was caused by classes being refactored by Application Express in a way that led to child sub-cases/classes becoming associated with the incorrect parent. The collision resolution algorithm has been updated to correctly resolve those situations.
_________________________________________________________________________________________________________
SR-114047 ISSUE: 161185
When attempting to perform a delete action on a specification, the rule was being withdrawn instead of deleted. This caused attempts to create a specification with same name to fail because the system reported the name already existed. The issue was an incorrect label name in the navigation menus for the Requirement and Specification landing pages: the correct label is "Withdraw", not "Delete", and it has been corrected.
_________________________________________________________________________________________________________
SR-114058 ISSUE: 162978
Emails encoded as x-user-defined were not processed and were marked as seen without creating a new case. This problem was traced to JavaMail not supporting all encoding types, and "x-user-defined" is one that is not supported. The code has now been updated to read the parts in case of unknown encodings using a chosen charset, and convert to a string so the email will be handled as expected.
_________________________________________________________________________________________________________
SR-114091 ISSUE: 161125
The "save" option was not refreshing the section showing the reports within a category, though "save as" was working as expected. This was traced to the save operation not having the same set of callbacks as the save-as operation, and has been fixed.
_________________________________________________________________________________________________________
SR-114153 ISSUE: 161844
The OOTB Edit validate rule 'ValidateOperPassword' was not set to allow localizing error messages for password policy. The field values for the message labels InvalidPasswordLength, InvalidPwdCharacter, DuplicateIDPwdCharacters, and MatchOldPasswords are now available for localization.
_________________________________________________________________________________________________________
SR-114154
ISSUE: 162063 / ISSUE: 162838
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.
_________________________________________________________________________________________________________
SR-114192 ISSUE: 162917
Previously, WS security only supported username token. An enhancement has been added to the service side layer to support signature as well.
_________________________________________________________________________________________________________
SR-114239 ISSUE: 162806
When the SOAP wizard is run for a WSDL that has repeating simple elements, the repeating simple nodes had a pyValue element hanging off of them. This was caused by the generation of elements in Parse XML and Edit XML Stream, and XMLRuleBuilder has been repaired so that it calculates leaf status correctly and does not attempt to process the artificial pyValue properties as nodes.
_________________________________________________________________________________________________________
SR-114254 ISSUE: 163325
Installing "Smart Dispute for issuers" via the app store failed, though manual installation worked. This issue was traced to an archive which changed a column from NULLABLE to NOTNULL, and the NOTNULL triggered the import code to use a database reference to determine the vendor type of a DADN which resulted in an NPE. This has been fixed so the install will not use a possibly null database instance during command line import.
_________________________________________________________________________________________________________
SR-114266 ISSUE: 162284
In a table with grid repeat, the filter icon triangle image was being overlaid on the text of the column header label cell instead of in its own column, causing a few letters to be hidden underneath the triangle. The enclosing element that contains the column header label and the filter icon was not resizing to accommodate the label and the filter icon without the icon overlapping the label, and has been fixed.
_________________________________________________________________________________________________________
SR-114323 ISSUE: 162809
As part of deleting a property rule by clicking the 'delete' button, a pop-up dialog box appears for entering the reason for deletion. Using Internet Explorer 8, this dialog box was Intermittently disappearing before it was possible to enter the comments and delete the property. This is caused by how Internet Explorer 8 handles modal flows, and the code has been updated to compensate for this browser issue.
_________________________________________________________________________________________________________
SR-114370 ISSUE: 162691
On selecting "Fixed (pixel) size grid and "Freeze grid header" option in the Presentation options of the repeat grid, the grid headers were not aligned properly. When 'Freeze grid Header' Option is selected, the header and the other rows are styled as different blocks. Hence when a scroll bar comes up, the header row is not considered and the alignment does not match. This has been fixed.
_________________________________________________________________________________________________________
SR-114410 / SR-111233
ISSUE: 162675 / ISSUE: 157531
The "Add Item" and "Delete" buttons present in the repeat grid were not available for localization. This has been corrected, and a field value rule has been inserted for "Add Item".
_________________________________________________________________________________________________________
SR-114452 ISSUE: 162050
When using a repeat grid with a fixed height and frozen header, the fixed size by itself works properly, but checking the Freeze header checkbox caused the height to be increased at runtime from 360 up to 780px. To correct this, changes were made to the scrollbar handling of the grid.
_________________________________________________________________________________________________________
SR-114508 ISSUE: 163553
The default setting in Internet Explorer 8 and Internet Explorer 9 is to have 'display intranet sites in compatibility mode' checked, and there is no option in IE to provide exceptions to this. As a result, IE=EGDE meta injection forces the browser into capability mode to render in standards, but the components (like modal), are still steaming considering "capability mode", i.e, they are serving old markup. To fix this, if the browser is in compatibility mode and meta is IE=EDGE, the inStandards param will be set to 'true'.
_________________________________________________________________________________________________________
SR-114564 ISSUE: 163676
If an email account page was set up for outbound transaction (Sender), leaving the UserID and Password fields empty for connecting to the SMTP server caused the setup to fail with an authentication error even if the SMTP server did not require credentials. In order to support SMTP Servers which are not password protected, the requirement for validation when connecting to an outbound SMTP server has been set to inactive by default.
_________________________________________________________________________________________________________
SR-114614 ISSUE: 162532
Using a percentage setting for width on the property panel was not working correctly. This was traced to the value being applied twice, halving the result. The code has been fixed to properly apply a percentage value for width.
_________________________________________________________________________________________________________
SR-114796 ISSUE: 163324
Previously, systems that being monitored by AES 3.4 had an SQL Query failure caused by the SQLs not meeting the schema qualifications required by Pega 7. Additional code changes were made to the APIs used by the AES Remote end to ensure proper monitoring.
_________________________________________________________________________________________________________
SR-114806 ISSUE: 163770
If File Listener encountered an empty file (0 byte), it would correctly skip case creation but it would not delete the input file. In order to ensure files are handled according to local processing requirements, there is now a checkbox provided on the FileListener ruleform's process tab for "Process Empty Files". Checking this box will cause File Listener to include empty files in its processing and delete them.
_________________________________________________________________________________________________________
SR-114824 / SR-114823
ISSUE: 163944 / ISSUE: 163945
When using the accessibility framework, a popup appeared with the message "Screen updated. Please refresh JAWS using JawsKey(Insert) + Escape keys." every time a rule was opened or a search was triggered. This box was not dismissing correctly when OK was clicked. The dismissal has been fixed, but in addition the popup box will now be suppressed if the accessibility framework is being used.
_________________________________________________________________________________________________________
SR-114825 ISSUE: 162713
A "Click here to sort" hover message was coming up for an unexposed column in list view. This has been corrected to not display the message for unexposed columns.
_________________________________________________________________________________________________________
SR-114829 / SR-114830 / SR-115220 / SR-115221
ISSUE: 162910 / ISSUE: 163150 / ISSUE: 163668 / ISSUE: 163670
The Summary view drill down report was not working if the label was clicked (first column of the listview), though it was working if the count (number column) was clicked. Drilling down on a summary view for the grand total column and all other links now works correctly.
_________________________________________________________________________________________________________
SR-114837 / SR-114831
ISSUE: 162696 / ISSUE: 162703
Case Details became editable on click of review button even if a user did not have access to a class and tried to open a WO for that class (via search). A link to open the assignment was displayed, and clicking the link displayed the default error message along with the Review and Close buttons. Selecting the Review button allowed the case details (in the review screen) to become editable. This was caused by the parameters not being set properly while calling the display harness, and has been fixed.
_________________________________________________________________________________________________________
SR-114839 ISSUE: 162557
When exporting a report to Excel, an unwanted extra row was being added at the top if the first row in the report was masked with ** value. The markup generation that is created to export data to Excel has been modified to correct this behavior.
_________________________________________________________________________________________________________
SR-114873 ISSUE: 164137
Some customers were unable to perform a Save / Save As on sections containing imbedded images after upgrading, and the error "setShowProperty(boolean) from the type StreamBuilderToolKit is deprecated" would appear. This was caused by a change in how the HTML handled filenames containing special characters like quotes. For ease of use, handling has been added to correctly imbed the images used under older versions of PRPC without requiring filename changes.
_________________________________________________________________________________________________________
SR-114877 ISSUE: 164485
When trying to create a new framework application built on the application 'Customer Process Service for Financial Services 7.1.2', the following error occurred: " A Rule-Obj-Class could not be saved due to 1 error(s) on it: .pyClassGroup: ** ClassGroup name must match the beginning of the ClassName". While there was a workaround of deselecting the survey and interaction classes and then manually adding them later if needed, this issue has been resolved.
_________________________________________________________________________________________________________
SR-114998 ISSUE: 163993
"Scan Document(s)" was being displayed as Scan Doument#40;s), a problem caused by the security handling in crossScriptingFIlter not processing the bracket correctly. To fix this, a check has been added.
_________________________________________________________________________________________________________
SR-115028 ISSUE: 164057
A bug in Internet Explorer (present in Internet Explorer 6 through Internet Explorer 10) produced an AJAX error some significant percentage of the time for a network with high latency between the browser and the server. Microsoft has a fix which eliminates the additional timeout user has to wait before the error is presented, but the error still occurs with exactly the same frequency. The greater the latency, the more frequent the error: the Webserver starts to (correctly) close the connection because the keepalive interval on the connection has expired. Because of the extreme latency between the Webserver and the Internet Explorer client, it may be quite a long time before the client becomes aware the connection is closing. During this time, the client issues a POST request which fails because the connection is closed on the other end. To handle this, ajaxTimeout now allows locally setting any value > 0 and < 10 minutes so callback.timeout would be set appropriately.
_________________________________________________________________________________________________________
SR-115086 ISSUE: 163124
Grid Repeat layout was failing to refresh correctly on close of an overlay window if it was set to inline row editing and a row was clicked, though it worked correctly if the inline edit mode was set to 'rows always editable' or with a modal window rather than overlay. This has been updated so closing the overlay window will refresh correctly.
_________________________________________________________________________________________________________
SR-115090 ISSUE: 164416
Previously, it was not possible to view files attached to a Requirement rule unless the rule was checked out (the Add/Edit attachments button was disabled, and there was no list of attachments). Requirement attachments have been enhanced in PRPC 7.1.6 and this issue no longer exists; requirement attachments are visible from the Landing Page or the Rule Form even when the requirement is checked out or its ruleset is otherwise locked.
_________________________________________________________________________________________________________
SR-115107 ISSUE: 163530
The mobility requirements of some customers require that they use a product called IBM Worklight. IBM Worklight comes with its own version of Cordova, which is different from the version of Cordova that Pega ships with. PRPC includes proprietary JavaScript static bundles for the specific version of Cordova that is shipped, but these static bundles don’t work with other versions of Cordova. We have now modified the HTML Fragment rule pyWorkFormStandardExtension. Customers can copy this HTML Fragment into their own RuleSet and then edit it to point to their own static bundle to work with their version of Cordova.
_________________________________________________________________________________________________________
SR-115181 ISSUE: 163320
An enhancement has been added to support Oracle Personal Edition.
_________________________________________________________________________________________________________
SR-115363 ISSUE: 164266
When using FCM Open Work Object (parent) with Key, the case opened and displayed in the same thread as a local work item tab and then lost the lock on the local work object. This was caused by an error in the method used to get the thread name, and the handling has been updated.
_________________________________________________________________________________________________________
ISSUE: 135526
The Mustunderstand attribute in the SOAP security header was unconditionally set and could not be disabled. A rampartconfig custom assertion has been inserted to allow for customization.
_________________________________________________________________________________________________________
ISSUE: 164629
The 'PDFFontsDirectory' parameter used for HTML-to-PDF conversion was causing NPEs unless it was set to a null value. The handling for this parameter has been updated to properly assign the fonts directory path in cases where a custom value was given.
_________________________________________________________________________________________________________
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 ' ' 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 " " 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. _______________________________________________________________________________________________________