Element and relationship properties
Select an element or relationship and choose Details. Name and Type describe the record. Parent places an element inside another element. Relationship From and To select endpoints by their names. A BPMN step's Pool and Lane fields control its swimlane membership.
Add a custom field
- Open Details and find Custom properties.
- Enter Owner in New property name and select + Add property. Edit its value to Student services.
- Apply the edit by leaving the field, then inspect the Systems or Interactions table.
- Use that property in colour mapping or a catalogue, then save the model.
Use consistent spelling and values across records. Owner and owner can become different property columns. Keep display values short; put long explanations in the surrounding documentation.
Model settings
Choose Menu → Edit model properties or the Model tab. Settings include title, model type, layout and direction. The available metadata controls depend on the model. Changing notation does not translate existing records into that notation.
Reserved structure
Do not reuse ID, TEXT, TYPE, PARENT, FROMID or TOID as custom-property names. Preserve import metadata beginning _src_ in externally edited files. Avoid manually editing internal selection or deletion flags. Use the editor's Parent and endpoint controls instead of typing IDs.
Rovo input rules
Rovo custom values must be strings, finite numbers, booleans or null; arrays and objects are rejected. Its action inputs use lower-case core field names and reject reserved metadata. These are Rovo contract rules, not a promise that every import path validates values identically. For a model shared across editing routes, prefer simple scalar values.