Library Folders

A Library Folder is a collection of reusable Rules, Templates, and Scripts with no Pod behind it. Nothing in it is connected to Oracle, so nothing is ever Pulled into it or Pushed out of it. It is the place for the snippets and starting points you reuse across Pods: a standard aggregation script, a currency template, the header comment block your team puts at the top of every rule.

Library Folders are available on every tier. No Seat Key is involved.

Create a Library Folder

1. Click the EPM Workbench icon in the Activity Bar and open the Pod picker at the top of the sidebar.
2. Click Create New Library Folder at the bottom of the picker. (EPM Workbench: Create New Library Folder in the Command Palette, Ctrl+Shift+P / Cmd+Shift+P, does the same thing.)
3. Type a name, for example Workforce, and press Enter.

The folder is created and selected right away. In the picker it appears under the Library group, alongside your Domains. Every Library Folder you create later lands in that same group.

What the tree looks like

Select a Library Folder and the Rules module shows three folders directly: Rules, Templates, and Scripts. All three are always there, even when empty, so you always have somewhere to add a file. You can nest subfolders inside them.

Two things you see on a Pod are missing here, and both for the same reason:

• There is no application level and no plan type level. A Library has neither.
• There are no sync badges. Badges compare your copy against the Pod’s copy, and there is no Pod to compare against.

The Pull from EPM, Push to EPM, Deploy, and Execute actions do not appear in the right-click menu of a Library Folder either. The rest of the menu is the same as a Pod’s: Open in New Tab, Add New on a folder, Rename, Copy Rule, Add Validation Exception…, and Delete.

The Dimensions and Artifacts tabs are disabled while a Library Folder is selected. Hover one and the tooltip says so.

Editing

A rule in a Library Folder opens in a normal VS Code tab and behaves like any other rule file: completion for calc functions and the EPM Groovy API, hover documentation, formatting on save, and inline errors and warnings from Validation Rules. A Library Folder has its own validation-rules.json, so its rules can be tuned independently of any Pod. The inline errors and warnings work on every tier; configuring rules and recording Exceptions is part of the Offline and Full tiers, like everywhere else (see Validation Rules).

What a Library cannot offer is member and alias completion. That comes from a Pod’s Pulled dimensions, and a Library has none.

Copy a rule into a Pod

Copying is the one outward path from a Library.

1. Right-click a rule, template, or script in the Library Folder and choose Copy to Pod….
2. Pick a connected Pod from the list. Only connected Pods appear, since a Library has nothing to Push a copy to.
3. If a file with that name already exists in the target Pod, choose Overwrite or Keep Both. Keep Both saves it as <name> Copy, then <name> Copy 2, and so on.

The copy lands in the matching Rules, Templates, or Scripts folder in the Pod and opens in an editor tab. It is new until you Push it, exactly like a rule you created with Add New. Nothing is sent to Oracle by the copy itself.

Copies are independent. Editing the Library original later does not change the copy in the Pod, and editing the copy does not change the Library.