Improvement
The following improvement is introduced in Crescendo 6.3.1.2 Patch 30.
Improvement Name | Description | Benefits |
|---|---|---|
Retain in-active user data User Persona: Analyst | This improvement ensures that inactive users are consistently retained and displayed in all user-related fields (such as Requester, Analyst, etc.) across records, regardless of record status. The system no longer filters out inactive users from dropdowns or populated fields, allowing records to preserve correct user information for Open, In Progress, Closed, Resolved, and Cancelled statuses. For more information, refer to Retain in-active user data. |
|
Fixed Issues
The following are the issues fixed in Crescendo 6.3.1.2 Patch 30.
Issue ID | Issue Description | Resolution |
|---|---|---|
187065 | While forwarding the ticket for approval to a new approver, the email sent to the new approver contained the old approver’s information. | While forwarding the ticket for approval to a new approver, the email sent to the new approver contains only the new forwarded approver’s information. |
186967 | The AD job did not create or update records because it returned the error “Job is already in progress.” | The AD job now creates and updates records successfully |
184631 | The Next Set value did not update in the request workflow. In the workflow sequence Set Workgroup > Approver > Set Workgroup > Waiting for Change > Set Workgroup, the final set value was not updated after approval. | Updates the request workflow logic to correctly apply the Next Set value after approval and to ensure the final set value is updated in workflows containing multiple Set Workgroup steps. |
185979 | When a new software entry was created in Assets, the updated information was not saved. | When a new software entry is created in Assets, the updated information is saved successfully. |
179024 | Clone features did not work if the workgroup is not assigned. | Clone features work as expected irrespective of workgroup. |
187213 | The business rule configuration for Squad Cast integration was not functioning as expected. | The business rule configuration for Squad Cast integration is fixed and functions correctly. |