Collaboration

Data Stories

Users can now add content to Story Zones and search for both stories and story zones simultaneously.
What Changed
In the Data Stories, there was no flexibility to add content for a Story Zone. Now, content can be added to a Story Zone, and users can search for both Stories and Story Zones simultaneously.
Affected Users: Authors
Data Stories table now correctly displays content in both Arabic and English, ensuring proper rendering of multilingual data.
What Changed
In the Data Stories table, Arabic and English content did not display in the correct order, and copying descriptions from Word documents retained unwanted HTML elements. Now, Arabic and English content displays in the proper order in the Data Story table, and descriptions copied from Word documents no longer contain unwanted HTML elements.
Affected Users: Authors
The Data Stories Editor has been enhanced to support extended formatting options, allowing users to create richer, more visually appealing stories.
What Changed
In Data Stories, the Froala editor lacked display options such as text size, font family, headers, and other formatting features. Now, the Froala editor in Data Stories includes additional formatting options such as text size, font family, headers, and more.
Affected Users: Authors

Service Desk

In Service Requests, when fulfillment remarks are updated, all the remarks are now captured in the Remarks History.
What Changed
In Service Desk, updating a fulfillment remark in a service request would overwrite the existing remark, causing the older remark to be lost. Now, when a fulfillment remark is updated, the older remark is captured in the Remarks History.
Affected Users: All users
Draft versions can now be created and edited for published templates.
What Changed
In Service Desk, once service requests were raised using a template, the template could no longer be edited. Now, templates with raised service requests can be moved to Draft status for editing. In Draft status, new fields can be added, existing fields can be deleted, and configurations can be updated.
Affected Users: Administrators
Customizable Service Desk list view with updated naming conventions.
What Changed
The Service Desk list view is customizable. Service Request Groups are labeled as SR-1000, and approval tickets are labeled as SR-1000-01.
Affected Users: All users
In Service Desk, after a term is deleted, cloning the request and approving it caused the job logs to display “null” instead of proper log entries.
What Changed
In Service Desk, service requests with the request type Change term structure could be cloned, but the cloned requests failed during fulfillment if the object was unavailable or its order had changed. Now, Service Desk templates with the request type Change term structure can no longer be cloned, preventing fulfillment failures caused by unavailable objects.
Affected Users: All users
Service Desk now allows adding fulfillment comments to track the service request progress.
What Changed
In Service Desk, users could not add fulfillment comments to track the progress of a service request. Now, in Service Desk, users can add fulfillment comments to track the progress of any service request. These comments are also displayed in the Latest Comment/Remark column of the All Requests tab.
Affected Users: All users
The Priority field in Service Desk Templates can now be hidden at the template level.
What Changed
In Service Desk Templates, users could not hide the Priority field when creating Service Desk templates. Now, the Priority field can be hidden at the template level. Although it remains a mandatory system field and cannot be deleted, it will not appear on the form if configured to be hidden within a specific template.
Affected Users: Administrators
Service request descriptions now support rich text formatting with a 10,000-character limit.
What Changed
In Service Desk, the default description limit for service request text areas was 1,000 characters. Now, the default description limit for service request text areas is 10,000 characters, allowing more detailed request information.
Affected Users: All users
Service Desk templates now feature separate tabs for easier viewing and creation, replacing JSON structures with a user-friendly properties manager for configurations.
What Changed
Service Desk templates used JSON structures for configuration, making them harder to view and edit. All configurations were managed in a single interface without separation by template aspect. Now, Service Desk templates are easier to view and create, with separate tabs for different aspects of the template. JSON structures have been removed, and a user-friendly properties manager has been introduced for configurations.
Affected Users: Administrators

Question Wall

In Question Wall, the default assignee for the General Question Wall can now be changed.
What Changed
In Question Wall, the default assignee for the General Question Wall was previously fixed as OE_Admin and could not be changed. Now, the default assignee for the General Question Wall is editable. This update provides flexibility to update the default assignee as needed.
Affected Users: All users

PreviousMetadata Governance NextAdvanced Tools

Last updated 2 months ago

Was this helpful?