about a flow deactivation

Mamidi
Tera Contributor

8 hours ago

Hi all,

actually i deactivated a OOB flow in EAM  which i just wanted to edit that's why i did that and that too in vendor instance and we tried to install and uninstall so that the spokes will get like that and the flow is in asset management common application and a security admin also can not able to make the active true it is showing security prevention i don't know why and i have admin role for your information and we know that when i copy and make the exact same it won't work as  OOB flow as it won't bind and wired that much strongly with the system as a OOB flow as it has a similar visual design but the back thing has more to do i guess ,so can you please help me to make it activate

0 Helpfuls
  • 63 Views
1 REPLY 1

Itallo Brandão
Giga Guru

5 hours ago

Hi Mamidi,

You are absolutely correct regarding the Copy of the flow. In Enterprise Asset Management (EAM), many workflows are triggered via backend scripts (Script Includes) that call the flow by its exact Internal Name. A copy would have a different name/ID, so the system triggers would fail to launch it.

The "Security prevention" error typically happens for two reasons:

  1. Wrong Scope: You are trying to edit a record in the "Asset Management Common" scope while your session is in "Global".

  2. Restricted Application: The vendor application is set to prevent editing of protected artifacts.

How to fix this (Restore to OOB):

Since you simply want to revert it to the original "Active" state, the best method is not to edit the flow, but to remove your customization record. When you deactivated the flow, ServiceNow created a "Customer Update" record that overrides the OOB state.

Steps to Force-Reactivate:

  1. Select the Correct Scope:

    • Click the Application Picker (Globe icon) in the top header.

    • Select Asset Management Common (or the specific scope where the flow lives).

    • Note: Even admins cannot write to these records if the picker is in Global.

  2. Delete the Customer Update (The "Undo" Button):

    • Type sys_update_xml.list in the filter navigator.

    • In the "Name" column, search for the internal name of your flow (e.g., *sys_hub_flow_YOUR_FLOW_NAME).

    • Look for the record created recently by you (check the "Updated by" and "Updated" fields).

    • Delete this record.

What happens next? Once you delete the sys_update_xml entry, the system essentially "forgets" that you ever deactivated it. It will immediately revert to the underlying OOB version, which is Active by default.

If this response helps you solve the issue, please mark it as Accepted Solution.
This helps the community grow and assists others in finding valid answers faster.

Best regards,
Brandão.

0 Helpfuls