Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Organize the migration process

Log in to subscribe to topics and get notified when content changes.

Organize the migration process

There are several ways to convert the old SLAs to the new Task SLAs.

About this task

Perform the following steps to organize the conversion process:


  1. Convert the old SLAs to new SLA Definitions, but leave the Active flag unchecked on each one.
  2. Back up the old SLAs by exporting the table to XML.
  3. Deactivate the old SLAs, setting the Run the old SLA engine (System Policy -> SLA Management) system property (com.snc.sla.run_old_sla_engine) to false. This deactivates the legacy SLA engine preventing both engines from running and conflicting. This property is set to true by default, but will be set to false by the new SLA plugins, effectively deactivating the old SLAs.
  4. Activate the new SLA Definitions by checking the Active flags on each one.
  5. Navigate to Incident > Open and use the List Editor to "touch" each record. As each record is updated, the new Task SLA will attach to each incident. If there are too many open incidents to effectively touch using the List Editor, run a business rule that will update every open incident.