• State Not Answered
  • Replies 1 reply
  • Subscribers 96 subscribers
  • Views 41 views
  • Users 0 members are here
Options
Related

Leveraging manual approval on read-only target systems

f bozzardini
3 days ago

Hi everyone,

We’re currently analyzing how to implement the IT Shop and workflow for managing access to read-only integrated target systems.

Normally, we use the same workflow as with other targets, including a final approval step by the IT owner, who performs the manual provisioning.
However, the client doesn't want that the IT Owner has to approve each individual request manually.

Do you have any suggestions on how we could design this flow more efficiently, possibly reducing or eliminating the manual intervention from the IT owner?

Thanks in advance!

Francesco

Parents
  • 0 7 hours ago

    You might consider implementing those target system using CSM/UCI. The provisioning can be done manually from the UCI interface. 

    If the provisioning can be automated, for example with a script.call, you can alternatively implement a call to that as an external decisions in the workflow. But strictly speaking the TS is no longer read-only in that case.

Reply
  • 0 7 hours ago

    You might consider implementing those target system using CSM/UCI. The provisioning can be done manually from the UCI interface. 

    If the provisioning can be automated, for example with a script.call, you can alternatively implement a call to that as an external decisions in the workflow. But strictly speaking the TS is no longer read-only in that case.

Children
No Data