Flow Designer trigger of 'record created' not triggering on extended tables.

[Philip Green]

I have a small workflow in Flow Designer aimed at eliciting approvals when records are created in certain CI classes. The trigger for the flow is 'record created' in the Configuration Item (cmdb_ci) table, but when records are created in extended tables (e.g., Application) the workflow doesn't trigger.  Any ideas?

[Pradeep Sharma]

Hi Phil,

That is expected behavior. A flow created against a parent table will not be triggered on extended tables. You will have to define each flow against an extended table based on your use case.

-Pradeep Sharma

[Philip Green]

Ok thanks for confirming that.  It seems a bit artibrary if not disappoining (and a complete nuisance as the CMDB has hundreds of classes and it's impractical to put a flow onto each) as creating a record in an extended table will by default create a record in the base table.  Also, when the workflow is tested before publishing, it tests successfully on an extended table (e.g., business applications) without giving any indication that it will only work on the base configuration item table.

Is there any workaround to this, e.g., using a business rule to invoke a workflow when a record is inserted into cmdb_ci?

[jake_burman]

Please note, not triggering on extended tables is the same behavior of the legacy Workflow product. Triggering on extended tables is planned in a coming release, tenatively Paris, where user can set the Flow trigger configuration to run on extended tables.

In the mean time, the work around is to create a business rule that calls the flow API as the triggering mechanism. The business rule will run on extended tables, and trigger the flow just as if the Flow trigger system picked it up.

[jake_burman · Accepted solution]

Circling back on this thread, in Paris we updated Flow Triggers with a configuration option, to run on extended tables. See docs link here, for more information