We are often asked about this, but FlowchartX doesn't provide such engine. It will let you visualize a workflow, and let your users edit the workflow, but cannot do any evaluation based on the diagram structure.

You can bind the visualization provided by FlowChartX to your own engine using the control's API, events, and custom-data properties such as Tag / VariantTag / UserString.

Or you could build an engine based on the FlowChartX API. E.g. have the workflow represented using Box and Arrow objects. Then the evaluation engine can run through the nodes and relations starting from the first box and going through all boxes that can be reached recursively via box.OutgoingArrows and Arrow.DestinationBox.

You can use an integer value to identify your objects and assign that value as a Tag. E.g. that could be the object's index in an array, or a record id in a DB table containing the object data. You might also assign the objects to the VariantTag if they are COM objects.

Stoyan