Hi,
Has anyone practiced this automation in your work? Is it useful?
Services
If a change to one service potentially impacts your other services, you can create a service relationship. You can then use this service relationship and automation rules to flag changes that could impact a critical service, before those changes go live.
Thanks,
YY Brother
Hi YY,
In some cases you may have a form for a System change of one Application. Let call this Application A.
A change to Application A (that is a core Application may trigger changes to other application as B,C,D)
The use case is the following:
1.A Customer will raise a change in App A.
2.An Agent will evaluate the change and if the change will "Impact Other System/s" (dropdown field Yes and No)
3.Automation will be created( When the Dropdown field "Other System/s" is change to yes, An email will be send to each Other Systems stakeholders to check if this change is or is not affecting their system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.