AdemeroHelp

Move a document to the right folder when its type is changed

When someone re-classifies a document into this type, it lands in this type's folder automatically — a Content DocType Change trigger and a Move to Folder action — so a fixed classification never leaves a misfiled document behind.

Catalog administratorsContent Central 7.8+10 minutesVerified 2026-09-05

Before you begin

  • Users are allowed to change document types after filing (see Change a document's type, catalog, or fields after filing)
  • The destination folder exists, and a Content Central administrator to set its document type

When you're done, a document that someone changes into this document type moves itself into this type's folder, so a corrected classification also corrects the filing.

The planDocument type scope
  1. Trigger
    1. Content DocType Change › Changed to this Document TypeAny user
  2. Action
    1. Content - Move to FolderFolder Path: this type's folder · the folder's Document Type set to this type
  3. Rule
    1. "Changed to this type → move to its folder", enabled

Changing a document's type updates its fields and rules, but the file stays wherever it was filed under the old type. This rule finishes the job.

Build the trigger

  1. Go to Administration > Catalogs & Document Types, pick the Catalog and the destination Document Type (the one documents are being changed into), click the Workflow tile, then Triggers > New Trigger.

  1. Type: Content DocType Change and Changed to this Document Type. Trigger Name: Re-classified into this type.

  1. Click Save.

What you should see: a Live trigger. It fires for every document whose type is changed to this one, from any other type.

Give the destination folder this document type

Content - Move to Folder also sets the document type. The document takes the Document Type set on the destination folder; if the folder has none, it becomes the catalog's default document type. Unless this type is the catalog default, that undoes the change the user just made, and fields with no same-named field in the default type lose their values.

  1. In the Folder Browser, right-click the folder this type belongs in and choose Properties.

  1. Clear Inherit settings, then pick this document type under Document Type. Click Save.

What you should see: Folder properties updated. Reopen Properties: Inherit settings is clear and Document Type shows this document type.

Note

Only Content Central administrators can change folder properties; anyone else sees Only administrators can modify folder properties. Picking a type also ticks Hide folder if no view permission on its own.

Build the action

  1. Click Actions > New Action.

  1. Type: Content - Move to Folder. Action Name: Move to this type's folder.

  1. Under Folder Path, use Select a subfolder… (and Move Up) until the displayed path is the folder this type belongs in. Click Save.

Wire the rule

  1. Click Rules > New Rule. Rule Name: Changed to this type → move to its folder.

  1. Add Trigger: Re-classified into this type. Add Action: Move to this type's folder. Apply.

Test it

  1. Pick a test document of a different type in the same catalog and change its document type to this one.

  1. Browse to the destination folder.

What you should see: the document now in the destination folder, Document Type in its Properties panel still this type, and View History showing the type change followed by the workflow move. If the change was blocked before it happened, that's permissions, not workflow — see the linked guide on changing types.

Variations

Want this insteadChange this
Catch changes out of a type (to clean up the old folder)There's no "changed from" sub-type; put this rule on every destination type instead
Move to a folder based on a field valueAdd a trigger per value under Use Multiple Triggers with AND, or split into one rule per value. Give each destination folder this type
Start this type's approval after re-classificationAdd Approval Process - Start Process — type changes don't start a process on their own
Copy instead of moveAction Content - Copy to Folder. The copy also takes the folder's type, so the folder setup still applies
React to catalog-wide changesRepeat this recipe on each type. One catalog-wide rule with one move would send every re-classified document to one folder and give it that folder's type, undoing the other changes