Vault structure
Everything the CtrlProcesses configuration binds is listed here. Nothing can be filled in until the thing it names exists.
The shape to build
Section titled “The shape to build”Each Elements.cloud entity you bring across needs three things: an object type, a class within it, and a text property holding the Elements.cloud id.
The id property is what makes the synchronisation idempotent. Without it every run creates another copy; with it, a run updates what it created last time.
Beyond that, how much structure you build depends on how much of Elements.cloud the vault needs. Releases and process maps alone are a working deployment; activities and reference model nodes are the ones that generate the most objects, because there is one per box and one per clause.
Workflow states
Section titled “Workflow states”Only URL publishing needs workflow states — the states that publish a link, mark it published, and retire it. If the vault is not publishing links back to Elements.cloud, none of them are required.
CtrlProcesses binds 84 settings to something that has to exist in the vault, 10 of them required. Everything below is generated from the shipping application, so nothing it needs is missing from this list.
Object types
Create these first; classes and properties hang off them.
| Needed for | Configuration section | Required |
|---|---|---|
| Object type | Object creator configuration | Yes |
| Employee object type | Person configuration | Yes |
| Resource object type | Resource configuration | Optional |
| Release object type | Release sync configuration | Optional |
| Process map object type | Map sync configuration | Optional |
| Process diagram object type | Diagram sync configuration | Optional |
| Process activity object type | Activity sync configuration | Optional |
| Resource object type | Resource sync configuration | Optional |
| Reference model object type | Reference model configuration | Optional |
| Reference model node object type | Reference model node configuration | Optional |
Classes
Each belongs to one of the object types above.
| Needed for | Configuration section | Required |
|---|---|---|
| Class | Object creator configuration | Yes |
| Class | Object click mapping | Yes |
| Release class | Release sync configuration | Optional |
| Process map class | Map sync configuration | Optional |
| Process diagram class | Diagram sync configuration | Optional |
| Process activity class | Activity sync configuration | Optional |
| Resource class | Resource sync configuration | Optional |
| Reference model class | Reference model configuration | Optional |
| Reference model node class | Reference model node configuration | Optional |
Properties
The data type is not advice. A property of the wrong type cannot be selected for the setting at all.
| Needed for | Configuration section | Data type | Required |
|---|---|---|---|
| Elements object ID property | Viewer configuration | Any | Optional |
| 'Initiated by' property | Object creator configuration | Any | Yes |
| Target property | Form value | Any | Yes |
| Related object property | Object click mapping | Any | Optional |
| Diagram ID property | Object click mapping | Any | Yes |
| Activity ID property | Object click mapping | Any | Optional |
| User account property | Person configuration | Any | Yes |
| Name property | Resource configuration | Any | Optional |
| Description property | Resource configuration | Any | Optional |
| Type property | Resource configuration | Any | Optional |
| Elements object ID property | URL publish configuration | Any | Optional |
| Description property | URL publish configuration | Any | Optional |
| Document property tags | URL publish configuration | Any | Optional |
| Elements Object ID property | Sync configuration | Any | Optional |
| Release name property | Release sync configuration | Any | Optional |
| Major version property | Release sync configuration | Any | Optional |
| Minor version property | Release sync configuration | Any | Optional |
| Patch version property | Release sync configuration | Any | Optional |
| Release date property | Release sync configuration | Any | Optional |
| Target release date property | Release sync configuration | Any | Optional |
| Release description property | Release sync configuration | Any | Optional |
| Diagrams changed in this release property | Release sync configuration | Any | Optional |
| Map name property | Map sync configuration | Any | Optional |
| Top diagram id property | Map sync configuration | Any | Optional |
| Diagram name property | Diagram sync configuration | Any | Optional |
| Diagram number property | Diagram sync configuration | Any | Optional |
| Diagram version property | Diagram sync configuration | Any | Optional |
| Process map lookup property | Diagram sync configuration | Any | Optional |
| Parent diagram lookup property | Diagram sync configuration | Any | Optional |
| Last changed in release property | Diagram sync configuration | Any | Optional |
| Resources used on this diagram property | Diagram sync configuration | Any | Optional |
| Reference models used on this diagram property | Diagram sync configuration | Any | Optional |
| Reference model nodes used on this diagram property | Diagram sync configuration | Any | Optional |
| Activity name property | Activity sync configuration | Any | Optional |
| Activity number property | Activity sync configuration | Any | Optional |
| Process diagram lookup property | Activity sync configuration | Any | Optional |
| Resources lookup property | Activity sync configuration | Any | Optional |
| Reference-model nodes lookup property | Activity sync configuration | Any | Optional |
| Attachments lookup property | Activity sync configuration | Any | Optional |
| RASCI: Responsible property | Activity sync configuration | Any | Optional |
| RASCI: Accountable property | Activity sync configuration | Any | Optional |
| RASCI: Supporting property | Activity sync configuration | Any | Optional |
| RASCI: Consulted property | Activity sync configuration | Any | Optional |
| RASCI: Informed property | Activity sync configuration | Any | Optional |
| Resource name property | Resource sync configuration | Any | Optional |
| Resource type property | Resource sync configuration | Any | Optional |
| Resource description property | Resource sync configuration | Any | Optional |
| Reference model name property | Reference model configuration | Any | Optional |
| Reference model description property | Reference model configuration | Any | Optional |
| Node name property | Reference model node configuration | Any | Optional |
| Node number / custom id property | Reference model node configuration | Any | Optional |
| Node description property | Reference model node configuration | Any | Optional |
| Parent node lookup property | Reference model node configuration | Any | Optional |
| Reference model lookup property | Reference model node configuration | Any | Optional |
| 'Deleted in Elements' property | Deletion configuration | Any | Optional |
Workflows
One per object type that the application drives through states.
| Needed for | Configuration section | Required |
|---|---|---|
| Default workflow | Object creator configuration | Yes |
| Workflow | Publish class mapping | Optional |
| Archive workflow | Deletion configuration | Optional |
Workflow states
States within the workflows above. Entering one is what triggers the work.
| Needed for | Configuration section | Required |
|---|---|---|
| Default state | Object creator configuration | Yes |
| Publish State | Publish class mapping | Optional |
| Published State | Publish class mapping | Optional |
| Retire State | Publish class mapping | Optional |
| Archive (deleted) state | Deletion configuration | Optional |
| Restored state | Deletion configuration | Optional |
User groups
| Needed for | Configuration section | Required |
|---|---|---|
| User group | User group mapping | Optional |
Generated from CtrlProcesses 1.26.9.14.
- One object of each kind you plan to synchronise can be created by hand, with the Elements.cloud id property present.
- That property is hidden or read-only on the metadata card, so nobody can edit it.
- If URL publishing is in use: the publish, published and retire states exist on the workflow the documents follow.
Set up CtrlProcesses — step four, configuring the synchronisation.