Registro — How to Use

Last Updated: January 1, 2025

The Three Commands at a Glance

Button What it does
Parameter Registry View, search, edit, compare, and create/bind shared parameters in the active model
Concat Rules Compute and write derived parameter values from drag-and-drop formula rules
Workset Assignment Filter elements by parameter conditions and assign them to worksets

Before You Start

Registro writes output files to Documents\AvantLeap\Tools\Registro\. This folder is created automatically on first use. No setup or configuration is required before running the first command.

Core Workflow

Parameter Registry (export) → Concat Rules (apply formulas) → Workset Assignment (sort elements)

Each command is independent. Run them in any order that suits your project stage.

Step-by-Step Scenarios

Scenario 1 — Audit the Shared Parameters in a New Project

Context: A project model has arrived and you need to know exactly which shared parameters are bound, what categories they cover, and whether the definitions match your office standard.

  1. Open the model in Revit 2026.
  2. Click Registro > Parameter Registry.
  3. Tab 1 (Model View) lists every bound shared parameter with name, GUID, data type, group, binding type (Instance or Type), and all bound categories.
  4. Use the filter box at the top to search by parameter name, data type, or category name.
  5. Click Export to save the list to a JSON file. Save it to your project folder as the baseline export.
  6. Close the window. The export is saved to Documents\AvantLeap\Tools\Registro\ for future comparison.

Scenario 2 — Compare the Model Against the Office Standard

Context: Parameters may have been added, removed, or re-categorised since the office standard was last defined. You want to see the diff.

  1. Open Parameter Registry → Tab 2 (Compare).
  2. Click Load Previous Export… and pick the standard JSON file (from your network or a previous export).
  3. The grid shows rows colour-coded: Added, Removed, Changed, Unchanged.
  4. Check the Apply box on the rows you want to sync back into the model (typically Removed and Changed rows).
  5. Click Apply. Registro executes the selected rebinds or creates missing parameters.

Scenario 3 — Create and Bind New Shared Parameters

Context: The model is missing several shared parameters required for a COBie or FM export. You want to define and bind them in one step without touching a shared parameter file manually.

  1. Open Parameter Registry → Tab 3 (Create / Bind).
  2. Click + Add Row for each new parameter. Fill in:
    • Name — the shared parameter name
    • Data Type — Text, Integer, YesNo, etc.
    • Group — the parameter group (e.g. Data, Identity Data)
    • Binding — Instance or Type
    • Categories — click Edit Categories… to open the searchable checklist and select categories
  3. Optionally click Import from Export… to load parameter definitions from an existing JSON export (only parameters not already in the model will be added).
  4. Click Apply. Registro creates a temporary shared parameter file, defines each parameter, binds it to the selected categories, then cleans up the temporary file.

Scenario 4 — Fill Computed Parameters from Formulas

Context: You have parameters like LO_Reference that should be computed as {LO_Grid}_{LO_Level} for all Doors. The values need to be written across all elements.

  1. Open Registro > Concat Rules.
  2. The left panel lists all parameters available in the model. Drag a parameter row to a Formula cell in the right panel to insert its token (e.g. {LO_Grid}).
  3. Click + Add to create a rule row. Configure:
    • Target Parameter — select from the dropdown (e.g. LO_Reference)
    • Formula — build by dragging tokens or typing directly (e.g. {LO_Grid}_{LO_Level})
    • Categories — type category names separated by commas, or click Edit Categories…
    • On — check to enable the rule
    • Overwrite — check to overwrite elements that already have a value
  4. Click Save Rules to save the rule set to a JSON file for reuse.
  5. Click Apply to Model & Close.
  6. A result dialog shows per-rule counts: rules run, elements updated, skipped. If any elements were skipped, click Open journal in Notepad for full per-element diagnostics.

Available built-in tokens:

Token Resolves to
{FamilyName} The family name of the element
{TypeName} The type name of the element
{UniqueId} Revit UniqueId string
{ElementId} Revit integer element ID

Scenario 5 — Assign Elements to Worksets by Parameter Values

Context: Mechanical equipment should go on the M - Equipment workset, structural columns on S - Structure. You want this applied automatically without manually selecting elements.

  1. Open a workshared (central or local copy) model.
  2. Click Registro > Workset Assignment.
  3. Choose Generate Template to create a starter JSON rules file. Registro pre-fills the file with your live worksets and a list of available parameter tokens.
  4. Edit the JSON file: for each rule, set:
    • parameterName — the parameter to filter by
    • parameterValue — the value to match
    • targetWorkset — the workset name to assign matching elements to
    • "enabled": true
  5. Click Workset Assignment again and choose Load Rules….
  6. Pick the JSON file. Registro evaluates each rule in sequence (AND logic for multiple conditions), assigns matching elements to their target workset, and creates any missing worksets automatically.

Scenario 6 — Reload a Saved Rule Set Across Projects

Context: You have a concat-rules JSON file from a previous project. The parameter names and categories are the same. You want to reuse the rules without reconfiguring them.

  1. Open the new project model.
  2. Click Registro > Concat Rules.
  3. Click Load Rules… and pick the saved JSON file.
  4. The rules grid populates. Review the Target Parameter column — if any parameter names differ, update them from the dropdown.
  5. Click Apply to Model & Close to run.

Tips and Good Practices

  • Run Parameter Registry first on any new project to establish the baseline export — the exported JSON is the reference every other operation builds on.
  • Save your concat-rules JSON files in a shared network folder per project template so all BIM managers on the team can reuse the same standards.
  • In Concat Rules, set the Order field to chain rules — a value written by a lower-order rule can be read as a token by a higher-order one.
  • The concat-journal.txt at Documents\AvantLeap\Tools\Registro\ is overwritten on each run. If you need to keep a history, copy it after each session.
  • For Workset Assignment, use Generate Template on a clean model first — it pre-fills the workset names and all available parameter tokens, which is faster than authoring the JSON from scratch.
  • Category names in Concat Rules and Workset Assignment must match Revit's English built-in category names exactly (e.g. Walls, Doors, Air Terminals). Use the Edit Categories… picker to avoid typos.