SR-B54175 · Issue 313627
Complex question Survey collection modified to support pagegroup reference handling
Resolved in Pega Version 7.3.1
Using a valuelist property embedded in a pagegroup to map the response of a Complex question resulted in a clipboard.InvalidReferenceException and the screen did not render the complex question. This was traced to the getMode function on ImmutablePropertyInfo returning the mode for the first property instead of the last property due to the first character being truncated if the property name started with "." To resolve this, SurveyAccessMethodBodyQuestionCollection has been modified to getMode from ClipboardProperty instead of ImmutablePropertyInfo.
SR-B65658 · Issue 294252
New case creation save errors resolved
Resolved in Pega Version 7.3.1
When a new case was created in an application built on top of Pega Pharmacovigilance, data propagation was throwing an error on the screen. Creation worked as expected when the pyDefault case type rule was opened and saved. This issue was traced to the case type rule not being created properly as part of the application creation, and has been resolved by updating pzDoesClassRequireBasicSave to not include Rule-Obj-CaseType in rows so the new application process performs a standard Save instead of an Obj-Save. In addition, it was not possible to save associated rules for selected data type when data type was in a locked ruleset and the pxUpdateRecord API was not setting pyrulename correctly when doing a save-as of the rule; these issues have also been corrected.
SR-B67239 · Issue 317809
pyCaseWorker offered during portal choice
Resolved in Pega Version 7.3.1
When choosing a portal on the access group, the pyCaseWorker one was not shown even though it was described in the documentation. To resolve this, an activity to update the property "pyDesktopType" to "User" has been added for the pyCaseWorker, pyCaseManager7, and pyPega7Express portals.
SR-B54548 · Issue 312031
Calendar Tab in Case Manager Portal shows Deadlines
Resolved in Pega Version 7.3.1
When opening the Calendar in the Case Manager Portal, it is expected that Goals and Deadlines are visible. However, Deadline was not visible in the Calendar even after the Goal time was reached. This was traced to the pxCalendarViewGadget taking the inputs for both GoalCalendar and DeadlineCalendar even though the latter is deprecated. In order to ensure pzCalendarAssignmentWorklist7 fetches the correct records, the pxCalendarViewGadget deadline source activity parameter has been modified.
SR-B46803 · Issue 306470
Button added to enhance chapter selection for Summary Tree
Resolved in Pega Version 7.3.1
When selecting specifications to include in a specification document, the "Chapters To Include" section did not always show the same specifications that were selected. To fix this issue, a new button labelled 'Update chapters to include' has been added; clicking on this will include the selected chapters in the Chapters Summary tree.
SR-B65006 · Issue 315528
Corrected validation for radio button labels in Survey
Resolved in Pega Version 7.3.1
When trying to save complex questions in Pega Survey with Answer mode as Radio button Matrix and giving radio button label as numbers, an exception was generated with the error "Label - Must start the value with a letter". This was due to incorrect validation, and has been corrected.
SR-B50458 · Issue 306818
Bulk Action select fixed for Microsoft Internet Explorer 11
Resolved in Pega Version 7.3.1
When using the Microsoft Internet Explorer 11 browser, clicking on the 'Select All' check box of the bulk action screen would select all of the assignments and then reset the flags to blank. This was an issue with select All property value being lost on refresh in Microsoft Internet Explorer 11, and has been resolved with an added Post value for the select All property in the pyBulkProcessingAssignDisplay section.
SR-B65922 · Issue 314665
Corrected Property type validation in Complex Question
Resolved in Pega Version 7.3.1
While creating a Complex Question with Property type Value list and referring an embedded property of type text in the Value list field, the validation message was not shown and system allowed the Complex Question to be saved successfully. Referring a top level property of type text (.ResponseText) showed the validation message (.ResponseText is not a valid Value List), but referring an embedded property type of text (.SurveyResponses(CEP).ResponseText) did not show the validation message. This was caused by missing handling, and has been corrected by modifying the ValidateSurveyEmbedPropertyMapping activity to check the last property mode for valuelist type.
SR-B74689 · Issue 323378
Marketing data flow run made more robust
Resolved in Pega Version 7.3.1
After upgrade, it was observed that Pega Marketing Campaigns were failing if there were no customers in the Audience configured on the Campaign, generating the error message "The run failed, because it exceeds the maximum number of failed records, which is currently set to 0". The cause of this was executing a distributed data flow with a database as primary source on an empty table, leading the run to fail as a table without any partition was considered in the handling. The database dataset has now been updated to differentiate the case when there's no partition available from the case when there's a single partition for every record, ensuring the DB data set now returns 'all' records when there is no partition key defined, and the data flow handles the no values for partitions in a more robust way.
SR-B65908 · Issue 314482
Serialization fixed for multi-node pre-activity dataflow
Resolved in Pega Version 7.3.1
Attempting to trigger a dataflow run with pre-activity configured to run on every node was failing with a serialization exception. This was caused by the task being distributed across the cluster having a member variable that was not serializable; this has been fixed.