If a sequence flow connects to a shape inside the boundary of the rectangle, it is treated as a BPMN Group symbol, but since Oracle BPM does not support the Group symbol, it will be ignored.Īny shape that does no match the above rules is imported as a Task. If a shape is a connector (usually a line used to connect other shapes), it is imported as a SequenceFlow.Ī rectangle shape that contains text, but has no border and no fill color is imported as a Text Annotation.Ī shape that is a circle or an ellipse is imported as an event.Ī rectangle that encloses other shapes is imported as an expanded Sub Process if no sequence flows cross the boundary of the shape. If a Visio master name or shape name is not matched by any entry in VisioUserMap.xml or VisioMasterMap.xml, the BPMN object type is determined by examining the shape attributes. For example, the following entries use the "*" wildcard to match entries based only on a shape property value: In this scenario, the shape master is set to the original master, even though the shape has been changed to look like a different symbol. This is useful for Visio templates that allow the user to change the BPMN object type (such as from Task to Sub Process) after adding the shape to the diagram.
The VisioUserMap.xml file is processed first, so any matching master map entries in this file supersedes all other entries with the same name in VisioMasterMap.xml.Ī special master map entry name of "*" is used to match all masters. If no conditional entries match, the first unconditional master map entry for the master name is used.
If there are more than one master map entry with the same name, the first one encountered with conditions that are all true is used. The following master map entry is matched if the master name is Start Event and it contains a property named Prop.StartEvent_Trigger: For example, the following entry uses a condition to detect whether an Intermediate Event shape from the TrisoTech BPMN stencil is a Throwing or Catching event:Ī special condition attribute of NotNull (not case sensitive) can be used to test if a specific Visio property exists. This is useful when two different Visio stencils use the same master names, but use different Visio properties to store BPMN attribute values. The master map files also support conditional mapping. Property names can also be derived from the XML tag hierarchy in Visio files saved in the *.vdx format. The most common properties are defined in the Custom Properties and User-defined Cells sections, which correspond the Prop and User prefixes respectively.
To view the ShapeSheet of a Visio shape, select the shape and choose Window > Show ShapeSheet. Setting srcType to visio indicates that the value is defined in the Visio object's "ShapeSheet".
#BIZAGI MODELER XML FORMAT HOW TO#
The XML attribute "srcType" tells the converter how to interpret the attribute value. The following master map entry for a task shape in the Visio 2010 BPMN stencil sets the BPMN attributes TaskType and Implementation from corresponding shape properties. The following entry maps the Visio master named gateway to the BPMN Gateway symbol, but also sets some BPMN attribute values:Īttributes can be set to a text, numeric, or boolean value (true and false) depending on what the BPMN standard requires.Īttribute values can also be derived from properties defined in the Visio shape itself. Master map entries can also define additional BPMN properties.
Master names are not case sensitive, so task matches Visio masters task, Task, and TASK.