Flow Designer related table

shun6
Giga Sage

Hi all,

Could someone tell me the table related to Flow Designer Flow as many as possible?

I'm currenty working on the privilege around flow designer.

 

Regards,

1 ACCEPTED SOLUTION

Mark Roethof
Tera Patron
Tera Patron

Hi there,

 

Just have a look in sys_db_object and search for *sys_hub_flow. That gives you most (not all!) tables related. For example that way you will miss a table like sys_variable_value.

 

Searching for *sys_hub_flow as mentioned:

sys_hub_flow_logic
sys_hub_flow_logic_definition
sys_hub_flow_safe_edit
sys_hub_flow_logic_ext_input
sys_hub_flow_logic_variable
sys_hub_flow_snapshot
sys_hub_flow_logic_input
sys_hub_flow_output
sys_hub_flow_stage
sys_hub_flow_variable
sys_hub_flow_base
sys_hub_flow
sys_hub_flow_component
sys_hub_flow_input
sys_hub_flow_logic_instance_v2
sys_hub_flow_designer_co_template
sys_hub_flow_block

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

View solution in original post

6 REPLIES 6

PJ 3000
Tera Expert

so if i wanted to protect create case from email data in a flow between Prod, dev and Test during clone back, separating the different instance emails in each flow, I can exclude and preserve sys_hub_flow and that's it?  

Seems to be what i can see there 🙂

Mike Tharp
Tera Expert

I stumbled into your question by chance. You will get better visibility on your questions if you make new posts in the community instead of commenting on old ones.

You are currently hard coding your "different instance emails" in your flows and not keeping things consistent across instances. I would recommend that you store this instance-specific information in system properties or add logic to your flow that provides different behaviors when the flow is run on each instance.  You can use a script on a "set flow variable" to read the "instance_name" system property (or use an action), then return whatever value you need or use it with some additional logic to set other flow variables. This can be put into a subflow to make it reusable, then you would just wrap it with if/elseif/else to set your instance-specific parameters.

I'm probably overcomplicating my explanation. All it is is this: if instance_name is instance1, then return "production"; if instance_name is instance2, then return "development". Use that to set your instance email in the flows. Alternatively, just put your instance email in a system property and pull the value into your flow.