Alternatives to PickDocsInTree for Modern Evolution CMS Workflows

Older Evolution CMS projects often relied on document-picker TVs or helper widgets such as PickDocsInTree. They solved a real problem: editors needed to choose related resources without typing IDs manually.

The problem is that older picker tools can feel rigid or outdated once the project grows. The real question becomes less “where is the exact replacement?” and more “what document selection pattern fits the project now?”

What teams usually need

• A way to choose one or more related resources without memorizing IDs.
• A UI that stays usable even when the tree becomes large.
• Stored values that templates can work with reliably.

Reasonable replacement directions

Depending on the build, the answer may be a cleaner TV type, a custom manager field, a relation table, or a lighter picker that searches rather than forcing editors through the whole tree.

For modernized Evo workflows, searchable relation selectors usually age better than pure tree-only pickers. They scale better and reduce the friction of huge site structures.

Main takeaway

Do not replace an old picker tool mechanically. First decide whether the project really wants a tree picker, a searchable relation field, or a controlled list of linked resources. That decision matters more than the exact widget name.

Source: Manager category on Extras.Evolution.