the integration only support the creation of a normal Change but nowadays a lot of team simply use Standard Changes.
The existing interface should not change.
Adding a new optional STANDARD field to pass a template name should work. if the field does not exist, it would behave the same but if it exists, it wold query to get the cr_sysid and create a change with that cr_sysid
the integration only support the creation of a normal Change but nowadays a lot of team simply use Standard Changes.
The existing interface should not change.
Adding a new optional STANDARD field to pass a template name should work. if the field does not exist, it would behave the same but if it exists, it wold query to get the cr_sysid and create a change with that cr_sysid