Minor Changes:
Enhancement: T-Systems:Connector: Deployed the scheduled job on vendor "TSC Error Resend " in active=false
As per ServiceNow cer recommendations, frequently running scheduled jobs will now be deployed in an inactive (active = false) state by default. Customers are required to activate and configure these jobs based on their specific scheduling needs.
Important: The "TSC Error Resend" scheduled job is critical and should be enabled appropriately, as it supports the retry mechanism for handling communication errors with T-Systems.
Enhancement: Update the business rule conditions related to skipping business rule error message
Sometime the condition configured on the Business Rule does not evaluate to a valid boolean (true/false) and instead resolves to null. Since ServiceNow requires Business Rule conditions to return strictly true or false, the platform skips execution of the Business Rule and generates the system message: "evaluated to null; skipping business rule"
Based on the ServiceNow recommendation logic is updated to handle null scenarios appropriately so that the Business Rule condition always evaluates to either true or false. The business rule condition is moved to script part. Updated Business rules "Message exchange triggering", "CHM Validation for Master T-Connector", and "CHM Message Exchange Trigger".
Bugfix:T-Connector Change - missing state change from Scheduled to Authorize
As per the initial design, the combination of the system property com.snc.change_management.change_model.type_compatibility == false and the connector property chm.slave.change.drivenBy.flow == true was responsible for attaching the "CHM Slave Change" model, which manages reverse state transitions (e.g., from Scheduled to Authorize).However there are certain customer instance which might contain 'com.snc.change_management.change_model.type_compatibility' as true.
To avoid any issues,T-connector script is updated so that the CHM Slave Change model is attached solely based on the condition chm.slave.change.drivenBy.flow == true.
Always ensure that both chm.slave.change.drivenBy.flow and chm.slave.change.drivenBy.workflow are set to true.
The CHM Slave Change model handles reverse state transitions when the customer uses workflows, as workflows must be canceled on the slave side to align with the master which is already taken care in Connector scripts.
Important --> If the customer uses flows, they must suppress them by applying appropriate conditions to prevent them from being attached to the change request. Updated script include "CHM_changeInfo_in"
BugFix:Second resolve by T-Connector of a TSI ticket doesn't trigger a new resolve-message
After an incident is resolved, if an asynchronous error is received from OTIP, a @no send work note is added to the incident. This prevents the next update from being triggered, intentionally avoiding message looping but also stopping further message stream processing.
The fix is implemtned to add An additional work note automatically after the @no send work note only in case of async error during resolution.
Ensures that the message stream is re-triggered, allowing subsequent updates to be processed correctly without causing loops.Updated script includes "errorHandler" and "errorResponse".
Note:No mapping or properties are udpated for this release.
