Choosing Flow Designer for dynamic shares makes use of ServiceNow’s Flow Designer to create a flow that will send records out of your ServiceNow instance as they are created and/or updated.
Because business rules may not always trigger when records are created and/or updated (due to changes done utilizing a script where setWorkflow is set to false to disable running business rules), this option is an alternative to ensure these changes are captured and shared out of your instance.
For more information, see ServiceNow Flow Designer and setWorkflow.
NOTE: In ServiceNow Orlando release, SLA Task has its own application trigger. You cannot create a dynamic share using SLA Task Application Trigger. However, you can still select task_sla in the dynamic share's table field. The flow designer record for SLA Task will not be accessible, however, the dynamic share will still apply.
- Because of how flows and business rules are created in ServiceNow, dynamic shares created with Flow Designer cannot be changed to a dynamic share created with a business rule (and vice versa). You will have to delete the dynamic share and create a new one if you want to change the dynamic share from one approach to the other.
- Also because of the many tables used by ServiceNow to build the Flow Designer engine, records will be inserted/updated in the following tables when a flow is created/updated and the first time each flow is triggered:
sys_hub_action_input
sys_hub_action_output
sys_hub_action_type_snapshot
sys_hub_flow
sys_hub_flow_block
sys_hub_flow_input
sys_hub_flow_snapshot
sys_hub_step_ext_input
sys_hub_step_ext_output
sys_documentation
NOTE: To ensure that the tables listed only grow to reasonable size, use ServiceNow's table rotation on the tables listed above. See ServiceNow Table Rotation on how to apply table rotation in your ServiceNow instance.
This will result in text_index events being created for these tables for updates by Flow Designer. Note that if you are running flows in a domain-separated instance with versions of New York or earlier, it may create these records in each domain. This issue has been resolved as of Orlando. The approximate updates are as follows: