To remove a flow, select it in the model editor, and press [Del].
The location of the validation errors in the model can be seen visually by double-clicking the validation message which will zoom you into the model and position you on the offending element (colored red).
The first validation error, means that the data types on both ends of the flow (the source and target) which should be the same are not (this is also indicated by the flow turning red).If both ends are data elements, the solution should be trivial - just make sure they are the same data element.However, this usually occurs when one (or both) ends are a slot (trigger/exit), because most slots (mainly those you add yourself from the palette) are type-less, in which case Tersus will perform automatic type-completion on Save (that is "guess" the data-type by traveling along flows, and copying the type from one end of a flow to the other), and if the process element with the type-completed slot is reused in some other location in the model connected to a slot/element of a different type, the said validation error will occur.Once a slot has been type-completed it will not be type-completed again, but you can change the type manually by dragging another data-type from the palette or repository and dropping it over the slot.
The second validation error notifies you that some process element in your application will never execute since one of it's mandatory (green-colored) triggers is not the target of any flow. Solution is simple ... create a flow into it. Note that other parts of the application which are not dependent on the process will work, so this situation may actually be modeled on purpose, in cases where you do not wish the process to be executed at present.
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
