Creating and Organizing Rules

Everything you create in the Rules tree is a file in your Pod Folder first. None of these four actions talks to EPM, so each of them tells you what the Pod still holds afterwards.

Add New

Hover a folder row in the Rules tree and click the + icon, or right-click the folder and choose Add New. The folder decides the kind: the + under Rules makes a Rule, under Scripts a Script, under Templates a Template.

1. Choose the scripting language, Calc Script or Groovy. Every kind supports both.
2. Type a name. It cannot contain / \ : * ? " < > |, cannot start or end with a dot, cannot have leading or trailing spaces, and has to be unique in that folder. The field tells you before you commit.
3. On a connected Pod, pick the plan type. Plan types already in the Pod are listed, and New Plan Type… lets you name one that is not there yet. When you clicked + inside a plan type, this step is answered for you.

The file opens right away in its own tab, and a notification confirms it: Created "Monthly Allocation". It is new until you Push it. The row carries the U badge until that first Push, because nothing by that name exists in EPM yet.

New Rules start from your own boilerplate, taken from the epmWorkbench.newRule.groovyStarter and epmWorkbench.newRule.calcScriptStarter settings, so a new Groovy Rule can arrive with your RTPS header and imports already in place. Both are described in Settings. Scripts and Templates always start empty.

Rename

Right-click the artifact and choose Rename. The name you type is checked the same way Add New checks it.

Renaming is local. EPM has no rename, so the old name still exists there until you delete it in Calculation Manager yourself, and a Push of the renamed file creates the new name alongside the old one rather than replacing it. The extension says exactly that in a notification after the rename, and the renamed row goes back to the U badge because, under its new name, EPM has never seen it.

Copy Rule

Right-click the artifact and choose Copy Rule, then name the copy. The name is pre-filled with the original plus Copy, which you can overwrite. The copy opens in a tab and is new until you Push it, exactly like something you created from scratch.

Delete

Right-click the artifact and choose Delete. A confirmation dialog names the artifact and tells you which of two cases you are in:

• The artifact was Pulled from the Pod. It still exists in EPM and comes back on the next Pull unless it is deleted from Calculation Manager.
• The artifact only exists locally, so deleting it is the end of it.

Confirming deletes the local copy and nothing else. The extension has no remote delete, because Oracle exposes no dependable way to delete a Calculation Manager artifact. Delete it there yourself when you want it gone from EPM.

All four work the same inside a Library Folder, where there is no Pod to be out of step with, and none of them needs a paid tier.