Workspaces, Processes, and Files

Ed organizes work into workspaces, processes, and files. Keeping those levels clear helps prevent accidental edits to the wrong model.

Workspaces

A workspace is the top-level container for related process models. Use separate workspaces when projects have different repositories, audiences, or configuration needs.

Common workspace patterns include:

  • One workspace for a product or client project.

  • One workspace for shared examples.

  • One configuration workspace for Ed sync configuration.

Processes

A process groups related files. A process usually contains one primary BPMN file and any supporting files that BPMN file references.

Supporting files often include:

  • *-schema.json files for RJSF forms.

  • *-uischema.json files for form display settings.

  • DMN files used by Business Rule Tasks.

  • JSON files used by data stores or examples.

Files

Ed can edit BPMN diagrams and supporting text files in the browser. When a User Task references form files, keep the schema and UI schema paired by form purpose.

For example:

  • request-details-schema.json

  • request-details-uischema.json

Avoid reusing an unrelated UI schema with a copied User Task. A mismatched pair can still run but render a confusing form.

Configuration Files

Some workspaces use an Ed configuration process to define sync and connector proxy settings. Keep configuration files separate from ordinary process model files when possible so they are easier to find and less likely to be synced accidentally.

See GitHub Sync for the public configuration pattern.