New in Release 23.1

New

  • Multilingual support added to Email-based surveys
  • New ‘Rebadged’ field added to user profiles, enabling catalog managers to use it in ‘Provide Information’ sections for consumers
  • Trigger contextual approvals directly to CI groups for faster decision-making
  • Resolution categories shown in dropdowns to depend on whether a CI or Service is selected, based on admin settings. If both are filled, related values from both are merged and shown with the CI class for clarity.
  • “Rules Admin” role added to manage Rules lifecycle with better access control
  • Asset allocation now supports assigning to multiple users
  • GenAI-powered Natural Language Search added to Fulfillment module
  • Auto-cancel active approvals if an approver becomes inactive
  • Change and Problem Lifecycle Reports can now be exported in Word/PDF formats
  • Rules now support escalation notifications when priority is set to P1 or P2
  • Notify option and Internal/External comment segregation added at Task level

Improvement

  • Improved data syncing by allowing updates and additions to CI custom details during integrations through upsert APIs
  • Rules to ensure evaluation of offering.company when ITM/CHG is submitted for shared offerings
  • Technical improvement – API calls from Incident/Problem/Change to Tasks are now managed through Kafka for Auto Task handling
  • Use CI’s business criticality as a parameter in rules for dynamic approvals and task planning
  • Introduced Technical Owner, Business Owner, and CAB groups in the CI form
  • Added “Project” field in CMDB UI for better asset traceability
  • “Other Users” field introduced in CMDB model for broader user tracking
  • Create PI question-based rules for change process/module across all rule types
  • Projects can now be linked directly to asset allocations
  • Approvers can now view questions and responses during approval review
  • Mandatory Checklist attributes now marked with an asterisk at the work item level
  • Seconds removed from AI-estimated resolution time in incidents to provide more realistic and practical values
  • Resolved desync issue between Chain Entity and Rules after deletion
  • Renamed “Operational Category 1/2/3” to “Category, Subcategory, and Type” for better clarity
  • Approval comments and Notify body now support new line characters across modules
  • Increased question limit per service offering from 50 to 150+ for detailed PI configurations

This topic was automatically closed after reaching the maximum limit of 1 reply.