Diagrams rely on very precise configuration and realtime data from external services that will often be on separate computers, which can in turn rely on data coming from other machines. This means that while diagrams can be very powerful tools, they can also be 'fragile'.

If a diagram doesn't seem to be working and the suggestions below don't help, please contact the Prophecy Consulting Group for assistance.

Why are my tag values blinking?

First off, it's important to be aware that a diagram can only work with the data it has available. In the event of a network outage, problems with the Data Acquisition Engine, lack of resources on the machine the diagram is running on, etc., the data can get 'behind'.

When we're able to determine that the diagram is working with bad or stale data, any tag values being displayed directly (like some tag value shapes) will flash to indicate that there's a problem with the data.

Why are my tag-based rules not updating when I expect them to?

As noted above, under certain conditions the diagram can end up working with bad or stale data. In the case of dynamic rules based on tag data, they will continue to evaluate using the last available data.

Why am I getting a generic red error message at the top of my diagram?

In the case of a communications problem with CSI (either reading or writing), the diagram will show an error message at the upper right of the screen. This can happen in edit mode and in live mode. Sometimes the error will provide enough detail for the user to take corrective action, but it will more often be a generic message like 'One or more errors occurred'. Operators will need to be trained on what to do in those cases until the issue can be tracked down.

When I load a diagram, I get this error: 'Number of filter values supplied does not match the filter template'

This will only happen on diagrams using Mongoose data shapes. It happens when an IDO definition has had indexes added to or removed from the filter after a Mongoose shape was configured in the diagram. When that happens, the Mongoose shape tries to supply the wrong number of filter values on the IDO call. To fix the error, the Mongoose shape(s) in the diagram will need to be updated.

If new filter indexes were added, you can simply edit the config for the shape(s) in the diagram editor and provide the new filter values.

If filter indexes were removed or reordered, it can be more complicated. If they were removed from the end of the filter (for example, Username='{0}' AND SuperUserFlag='{1}' AND UserDesc='{2}' became Username='{0}') you can simply open the editor, click OK, and re-save the diagram. The excess filter values that were configured on the shape will be removed, and it should start working again. If the filter indexes were reordered or indexes were removed from the middle of the list, you will need to edit the config for the shape(s) and update the filter values.

The copy/paste hotkeys don't always work when editing diagrams.

This is only an issue with shapes that accept user input. Sometimes the browser has a hard time determining whether a shape was selected for editing in the diagram (in which case copy/pasting the shape will work), or selected to provide input (copy/paste will not work). If need be, the shape can be selected by clicking and dragging on the diagram to highlight it, and the copy/paste hotkeys will work.