The user wanted to know why, on SLA Definitions, they could not select "changes to" or "changes from" operators like they could elsewhere on the Platform (e.g. with notifications).

After a conversation with the Product Owners for Service Level Agreements (SLAs), it was found that the operators "changes to" and "changes from" are purely a configuration driven capability (for condition builders). Looking at the below sys_dictionary entry for the Reset condition section of a SLA Definition, note the attributes:

• extended_operators=VALCHANGES;CHANGESFROM;CHANGESTO
  
  reference: /nav_to.do?uri=sys_dictionary.do?sys_id=066c1ceedbc33300cab952c8dc9619db%26sysparm_view=advanced

Enabling these operators in the other three SLA Definition sections is as simple as adding those attributes per section (Start, Stop, Pause).

The reason these operators were only added to Reset conditions was to keep complexity down. Using the "change from" and "changes to" operators is going to make "crafting" the conditions a little more complicated, unless the Cancel and Resume conditions are also used.

Using the operators on Stop conditions introduces the same complexity issue. If they are utilized, the user would need to ensure that the Start condition no longer matches after the Stop condition has been matched, otherwise they will get new SLAs that they likely are not expecting/do not want.