AdemeroHelp

When a project is closed, move all its documents to an archive catalog

Set a project's status to Closed on one of its documents, and within minutes every document for that project moves to an archive catalog, each keeping its document type and field values. The same two rules work for employees who leave, expired contracts, closed cases, and any record with an ID and a status.

Catalog administratorsContent Central 7.8+1 hour, plus a few minutes per document typeVerified 2026-10-30

Before you begin

  • An archive catalog whose document types have the same names and fields as the source catalog's (copying the source catalog is the easy way)
  • Every document for a project carries the same project number, typed the same way
  • Access to Administration > Global Fields and Administration > Workflow

When you're done, setting Project Status to Closed on one of a project's documents moves every document for that project from your Projects catalog to your Closed Projects catalog within a few minutes, each keeping its own document type and field values.

The example is a Projects catalog for active work and a Closed Projects catalog made as a copy of it. The same two rules move an employee's file when they leave, a contract's paperwork when it expires, or a case file when it's closed. The table near the end shows what to swap in.

The planGlobal scope
  1. Trigger
    1. Content Field Values › Global-Field Value Updated in the SystemField: Project Status · Field Evaluation: Selected Field Value(s) · Closed
  2. Action
    1. Content - Update Shared Fields by Key FieldKey Field: Project Number
  3. Rule
    1. "Closed → mark all the project's documents", enabled
The planGlobal scope
  1. Trigger
    1. Content Query › Content in a CatalogCatalog: Projects · Query: by Field Value(s) · Field: Project Status · Closed · Process Interval: Every 5 Minutes
  2. Action
    1. Content - Change CatalogCatalog: Closed Projects
  3. Rule
    1. "Closed in Projects → Closed Projects", enabled

How the two rules work together

  1. Someone sets Project Status to Closed on one of the project's documents.

  2. Rule 1 finds every other document with the same Project Number and sets its Project Status to Closed too (Update a field on every document that shares an ID).

  3. Every five minutes, Rule 2 finds the documents in Projects whose Project Status is Closed and moves each one to Closed Projects (Move documents to another catalog automatically).

It takes two rules because the documents Rule 1 updates don't start any workflow of their own. A single "when the status changes, move it" rule would move only the one document someone edited. The scheduled Rule 2 picks up the rest. Each document leaves Projects once it's moved, so Rule 2's search stays small no matter how many projects you close.

Before you start

  • Matching document types. Every document type in Projects has a type with exactly the same name, and the same field names, in Closed Projects. Copying the catalog gives you this (Duplicate a catalog). Recheck any type added or renamed since the copy.
  • A project number that matches exactly. Every document for a project carries the same value in one field. 2026-014 and 26-014 are different values, so a document with the second one won't be found.
  • A test project. Two or three documents of different types in Projects for a project that isn't real.
Important

Matching is by exact name and exact value. A document whose type has no same-named type in Closed Projects is skipped and stays in Projects, with no message on screen. Check both before you rely on the rules.

Set up the two global fields

Both rules work only with global fields: fields defined once and shared by every document type that uses them.

  1. Go to Administration > Global Fields and click Add Field. Name: Project Status. Type: Text. Turn on Create drop-down from choices., enter Active and Closed under Field Entry Choices, one per line, and click Create.

  1. Add a second global field the same way for the project number, without choices, unless you already have one.

  1. In Administration > Catalogs & Document Types, select a document type and click Fields.

    • If the type already has a project number field, open it, turn on Use Global Field, and pick the project number field under Global Field:. Its existing values stay with it.
    • Otherwise click Add Field, turn on Use Global Field, and pick the project number field.

    Then add Project Status the same way.

  1. Repeat step 3 for every document type in both catalogs.

Note

Linking both catalogs' document types to the same global fields also guarantees the field names match, which is what lets the values carry over during the move.

Build Rule 1: mark all the project's documents

  1. Go to Administration > Workflow, click Triggers, then New Trigger.

  1. Type: Content Field Values and Global-Field Value Updated in the System. Trigger Name: Project Status changed to Closed.

  1. Field: Project Status. Field Evaluation: Selected Field Value(s), then choose Closed under Selected Choices:.

  1. Leave User Evaluation: at All Users and Groups and click Save.

  1. Click Actions, then New Action. Type: Content - Update Shared Fields by Key Field. Action Name: Mark all the project's documents. Key Field: your project number field. Click Save.

  1. Click Rules, then New Rule. Rule Name: Closed → mark all the project's documents. Leave Enabled checked. Add Trigger: Project Status changed to Closed. Add Action: Mark all the project's documents. Click Apply.

What you should see: the rule in the Rules list with its Enabled switch on.

Build Rule 2: move them to Closed Projects

  1. In Administration > Workflow, click Triggers, then New Trigger.

  1. Type: Content Query and Content in a Catalog. Trigger Name: Closed documents in Projects.

  1. Catalog: Projects. Query: by Field Value(s). Leave Return: at All Matching Content (Multiple Records).

  1. Field Evaluation: Selected Field Value(s). Field: Project Status, then choose Closed under Selected Choices:.

  1. Process Interval: Every 5 Minutes. Leave Reprocess Matching Records After: at 1 Days. Click Save.

Figure

The Content in a Catalog trigger for Rule 2: Catalog set to Projects, Query by Field Value(s), the Project Status field with Closed selected, Process Interval Every 5 Minutes, and Reprocess Matching Records After 1 Days.

  1. Click Actions, then New Action. Type: Content - Change Catalog. Action Name: Move to Closed Projects. Catalog: Closed Projects. Click Save.

  1. Click Rules, then New Rule. Rule Name: Closed in Projects → Closed Projects. Leave Enabled checked. Add Trigger: Closed documents in Projects. Add Action: Move to Closed Projects. Click Apply.

What you should see: the trigger in the Triggers list with Event Scheduled, and the rule in the Rules list with its Enabled switch on.

File them into the right folders

Content - Change Catalog files each document by the destination document type's folder building pattern. Without one, the documents all land together in the catalog's base folder rather than in a folder per project.

To file each project into its own folder, for example 2026-014, set this up on each document type in Closed Projects. Go to Administration > Catalogs & Document Types, select the document type, and click Folder & File Building:

  1. Check Enable Folder Building.

  1. Under Folder Building Items, set Type: to Field, pick your project number field, and click Add Item.

  1. Fill in Folder name when field is empty: with something easy to find, like Empty, and click Apply.

Important

Folder names come from field values, so documents only land in existing folders when the folder names match the values. Check the Example: line against your existing folders. A different spelling makes a new folder beside the old one. Once folder building is on, editing a document's fields later can also move it to the folder its fields now point to.

Test it

  1. Open one of your test project's documents in Projects, change Project Status to Closed, and save. Change nothing else in the same save.

  1. Wait up to five minutes, then look in Closed Projects.

  1. Open View History on one of the moved documents.

What you should see: every test document in Closed Projects with its own document type and field values, nothing left for the test project in Projects, and a history line like From Catalog [Projects], Document Type [Change Order] to Catalog [Closed Projects], Document Type [Change Order].

If a document stayed in Projects, its document type or its project number didn't match. If nothing moves at all, scheduled rules depend on the Workflow Service, so start with A scheduled workflow didn't run.

The same recipe for other records

Swap the names and keep everything else:

RecordStatus field and valueKey fieldFrom → to
An employee who leavesEmployment Status: InactiveEmployee IDPersonnel → Separated Employees
A contract that endsContract Status: ExpiredContract NumberContracts → Expired Contracts
A client who leavesAccount Status: ClosedAccount NumberClients → Former Clients
A case, claim, or matterCase Status: ClosedCase NumberOpen Cases → Closed Cases
A student who graduatesEnrollment Status: GraduatedStudent IDStudents → Alumni
A lease that endsLease Status: EndedLease NumberLeases → Ended Leases

Things to know

SituationWhat happens
Only the document you edited movedEither the other documents' project number doesn't match exactly, or Rule 2 moved the edited document before Rule 1 ran. If the numbers match, open the moved document in Closed Projects, set Project Status to Active and save, then set it to Closed and save. Rule 1 runs wherever the document is
A document's type has no same-named type in Closed ProjectsIt stays in Projects. After you add the missing type, it moves once the Reprocess Matching Records After time (1 day) has passed
A document is filed for the project after it's closedIt stays in Projects until its Project Status is set to Closed
Someone changes another global field in the same saveThat value is copied to all of the project's documents too. Change only Project Status in that save
The project has documents in other catalogs that use Project StatusIf their types also use the project number global field, they're set to Closed as well, but they don't move unless you build a Rule 2 for that catalog
Projects uses folder or file buildingWhen Rule 1 updates a document, Projects' pattern is applied first, so it can be refiled or renamed in Projects before it moves
You check View History on a moved documentThe move is normally recorded under an administrator account, because scheduled rules run as one
A moved document is set back to ActiveNothing moves back. Build the same pair of rules in the other direction if you need that
A field exists only in the source document's typeIts value isn't carried over. Matching document types avoid this

Variations

Want this insteadChange this
Move documents out of more than one catalogAdd a Rule 2 for each catalog pair. Rule 1 already marks the project's documents wherever Project Status is used
React only when certain staff change the statusRule 1 trigger: User Evaluation: Selected Group(s), and pick the group
Check less oftenRule 2 trigger: Process Interval: Every Hour or Every Day
Move only one document at a time, as soon as it's markedSkip Rule 1, and use a right-away trigger with Content - Change Catalog (guide)

Still stuck?

Contact support with the names of both rules, the name of one document that didn't move, and what its View History shows.