Move documents to another catalog automatically
The Content - Change Catalog workflow action moves documents into another catalog, and each one keeps its document type and field values. How it works, how to set it up, which trigger to pair it with, and ideas from archiving closed projects to sorting a shared inbox.
Before you begin
- A destination catalog whose document types have the same names as the source catalog's (copying the catalog is the easy way)
- Access to Administration > Workflow
At the end of this guide you'll have a rule that moves documents into another catalog on its own, each keeping its document type and field values, and you'll know which trigger to use for what you want to move.
The workflow action Content - Change Catalog does the moving. A trigger decides which documents go and when. Together they can archive closed projects, retire finished contracts, move a departed employee's file, or sort a shared inbox into department catalogs.
Why workflow, and not cut and paste?
From Content Central 7.8.10223, people can move documents into another catalog themselves, with cut and paste or Move to..., and each document keeps its document type, as long as your administrator has turned on Allow catalog changes and the other catalog has a type with the same name (Move or copy documents between folders). That suits moves someone decides on at the time.
Workflow is for moves that should happen by themselves, when something about the document changes (a status, a date, its age), without anyone having to remember. It's also the way to keep document types on versions before 7.8.10223. There, cut and paste and most copy commands won't put documents into a different catalog, even if a success message appears, and copying one document at a time gives the copy your default document type for that catalog, not the one with the same name.
Content - Change Catalog matches each document's type by name, for every document its trigger finds.
What the action does to each document
| Part of the document | What happens |
|---|---|
| Document type | It gets the type with exactly the same name in the destination catalog. If there's no such type, the document is skipped and stays where it is, with no message on screen |
| Field values | Every field with the same name in both types keeps its value. A field that exists only in the old type isn't carried over |
| Folder | It's filed by the destination type's folder building pattern. Without one, it lands in the destination catalog's base folder |
| File name | It's rebuilt by the destination type's file building pattern, if there is one. Otherwise it's unchanged, unless a file with the same name is already in that folder, in which case the moved file is renamed so nothing is overwritten |
| History | View History shows a line like From Catalog [Projects], Document Type [Change Order] to Catalog [Closed Projects], Document Type [Change Order] |
Before you start
- Matching document types. Every type you'll move has a type with exactly the same name in the destination catalog. Copying the catalog gives you this (Duplicate a catalog). Recheck any type added or renamed since.
- Matching field names. The fields you want to keep have the same names in both types.
- Folder building on the destination types, if documents should land in folders by their values rather than all together in the base folder.
- A few test documents you don't mind moving.
Set up the action
Go to Administration > Workflow, click Actions, then New Action.
Type:
Content - Change Catalog. Action Name: something that says where documents go, likeMove to Closed Projects.
Catalog: the destination catalog. Click Save.
Content - Change Catalog is only offered in Administration > Workflow, not in a document type's Workflow tile, so build its trigger and rule there too.
Pick the trigger
| You want documents to move… | Trigger (Type › sub-type) | When it runs |
|---|---|---|
| As soon as someone sets a field on one document type | Content Field Values › Field Value Updated in a Document Type | Right away, for the document that was saved |
| As soon as someone sets a global field, on any type that uses it | Content Field Values › Global-Field Value Updated in the System | Right away, for the document that was saved |
| Whenever documents in a catalog have a certain value, including ones set before the rule existed | Content Query › Content in a Catalog, with Query: by Field Value(s) | On a schedule |
| Once documents reach an age, like 7 years | Content Age › Age of Content in a Catalog | On a schedule |
A few things decide between them:
- Right away, or on a schedule. The first two react when someone saves a document. The scheduled ones check the catalog every interval, so they also pick up documents that already matched before you built the rule.
- One document type, or all of them. Field Value Updated in a Document Type watches one type's field, and you pick the Catalog: and Document Type: on the trigger. To cover several types with one trigger, make the field a global field and use one of the others.
- Catalog-wide triggers use global fields. In Content in a Catalog and Age of Content in a Catalog, the fields you can test are global fields.
- One document, or a whole group. The right-away triggers move only the document that was saved. To move every document that shares an ID, like all of one project's or one employee's documents, follow When a project is closed, move all its documents to an archive catalog.
Example: move a contract when it's marked Expired
In Administration > Workflow, click Triggers, then New Trigger.
Type:
Content Field ValuesandField Value Updated in a Document Type. Trigger Name:Contract marked Expired.
Catalog:
Contracts. Document Type:Service Agreement.
Field:
Status. Field Evaluation:Selected Field Value(s), then chooseExpiredunder Selected Choices:. (If Status is a plain text field rather than a drop-down, typeExpiredunder Field Value: instead.) Leave User Evaluation: atAll Users and Groupsand click Save.
Build the action as above, with Catalog:
Expired Contracts.
Click Rules, then New Rule. Rule Name:
Expired contracts → Expired Contracts. Leave Enabled checked. Add Trigger:Contract marked Expired. Add Action: your Change Catalog action. Click Apply.
What you should see: after you set a service agreement's Status to Expired and save, it shows up in Expired Contracts with the same document type and values.
This trigger watches one document type. For contracts of several types, check Use Multiple Triggers on the rule, set Combine Method to OR, and add a trigger for each type. Or make Status a global field and use Global-Field Value Updated in the System instead.
Ideas: what people move with it
| Goal | Trigger and setting | Moves to |
|---|---|---|
| Archive closed projects | Content in a Catalog on Projects, Project Status is Closed | Closed Projects |
| Retire finished contracts | Field Value Updated in a Document Type, Status set to Expired | Expired Contracts |
| Move everything for an employee who leaves | Two rules, one to mark the documents and one to move them (recipe) | Separated Employees |
| Sort a shared inbox by department | Global-Field Value Updated in the System, Department set to Accounting; one rule per department | Each department's catalog |
| Keep sensitive documents apart | Global-Field Value Updated in the System, Confidential set to Yes | A catalog whose document types only certain groups can see |
| Move old records out of the everyday catalog | Age of Content in a Catalog, Minimum Age: 7 Years | Records Archive |
| Close out cases, claims, or matters | Content in a Catalog, Case Status is Closed | Closed Cases |
| Bring a reopened record back | The same rule in reverse, on the archive catalog | The original catalog |
Sorting an inbox only works for document types the department catalog also has. A document whose type isn't there stays in the inbox.
Test it
Set up the trigger on a test catalog or test document type first, or narrow it to a value only your test documents have.
Make the change or wait for the schedule, then look in the destination catalog.
Open View History on a moved document.
What you should see: each test document in the destination catalog with its own document type and field values, and the From Catalog […], Document Type […] to Catalog […], Document Type […] line in its history. If a document the trigger should have matched stayed put, its document type has no same-named type in the destination catalog.
A scheduled trigger's first run matches every document that already qualifies. On a big catalog that can be thousands of moves at once. Test on a small catalog first, or start with a narrower value or a longer age.
Things to know
| Situation | What happens |
|---|---|
| A document's type has no same-named type in the destination | It stays where it is, with no message on screen |
| A Content in a Catalog trigger has no Reprocess Matching Records After: value | It never matches anything. Keep the default 1 Days unless you have a reason to change it |
| You check who moved a document | View History normally shows the person who saved the change for right-away triggers, and an administrator account for scheduled ones |
| Documents were in hand-made folders | They're refiled by the destination type's folder building pattern, or land in the base folder. Existing folders are reused when the names match |
| A document is moved, then the value changes back | Nothing moves back unless you build a rule for that direction |
| A field exists only in the source document's type | Its value isn't carried over. Matching document types avoid this |
Still stuck?
If the rule never fires, start with A scheduled workflow didn't run. If it fires but a document doesn't move, compare its document type name with the destination catalog's types. Still stuck? Contact support with the rule name, the name of one document that didn't move, and what its View History shows.
