Allow User to See Active Flows/Workflows

[jmiskey]

On many of our REQ, RITM, and CHG records, under "Related Links", we are able to see the active flow/workflow path by clicking on "Show Workflow" (for Workflows) or "Flow Context" (for Flows).

We know that anyone with an "itil" role can see these related links, but we want to extend it out to our "fulfillers" who do not necessarily have the "itil" role (and we DON'T want to give it to them, as that gives them more permissions than we want they to have).

What roles do we need to add to a user (via a group or as part of another role) so that they can see/view these two Related Links to see the active flow/workflow path?  We do NOT want to give them the ability to create/edit/delete/check-out/publish Workflows or Flows, only the ability to see where in the current workflow/flow a record is (view only access).

Thanks

[Dr Atul G- LNG]

Hi @jmiskey 

Try this:

[nemamuskan]

Hello @jmiskey,

The UI action is working for "Flow context" related list.

UI action name: Flow Context

This UI action is having certain roles for the visibility in related list which are 

* flow_operator

* catalog_manager 

* catalog_editor

* catalog_admin

Please have a look in the screenshot attached.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Thanks,

Muskan

[Ankur Bawiskar]

@jmiskey 

why would fufillers see that? what business purpose it serves?

The flow context or workflow context table will have it's own table level ACL and roles.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[jmiskey]

I tried a combination of the first two replies, and tried adding both the "fd_read_roles" and the "flow_operator" roles, as that sounded it like it should give them just the access they should have (the ability to see/read Flow contexts, and not edit them at all.  However, it did not seem to work.  When I impersonated a user who got these two new roles and broke up an active RITM with a Flow in it, they could not see any Related Lists.

As for the business purpose, we have some Citizen Developers and Consultants whose Flows are not quite as mature as the ServiceNow Engineers Flows, and sometimes get "stuck", without gracefully exiting the flow.  The Citizen Developers only have advanced privileges in our Development environment, and not in Prod.  So neither they (nor the Team supporting these processes) are able to see the Flow context of a particular RITM to see where it might be stuck.  So they have to ask one of the ServiceNow Engineers to view it for them.

We would like these Citizen Developers, and other teams that support various processes in Production, to be able to see the active Flow/Workflow context for particular transaction to see where they might be stuck.  But we want to limit it so that they can only have Read only access to these in Prod.  They should not have rights to update any Flow, Workflows, or Catalog Items in Production.