Well as far i Know....
- Planning administrators can edit the calc manager rules deployed into their Planning application ---Its aspected , as admin have to maintain the application and nothing wrong in that....
- Planning interactive users can create their own calc manager rules in their Planning application--They can create thir own rules only when they have proper access to calc mgr..if you don't have given access to calc mgr then they can't.....
Thanks Sh!va for your help.
For interactive users : What calc mgr role do you mean ? My experience is that interactive users provisionned with the 2 Planning roles Interactive User and Essbase Write Acces on their planning application (and no calculation manager role) are able to create their own rules.
For administrators : yes they have to maintain the application, but in our organisation they maintain the dimensions but not the calc mgr rules, and anyway we think it is a dangerous practice to enable to create, edit and test calc mgr rules directly in the production environment.
So, for us any tip and trick is welcome.
An interactive will be able to create and deploy the rule in Calculation Manager but I don't think they would be able to run the rule in Planning until they were given access permissions on it.
Thanks John, I think you are right for interactive users !
And to disable Planning administrators ? A stupid idea : what if we create in the planning application not the original rules, but shortcuts of the original rules created in a "library" application. Will the planning administrator be able to edit the original rule through its shortcut ? Or to create a new rule by save as of the shortcut ?
Thanks Celvin (and sorry for this late reply). You are right.
By the way, its a pitty we can't currently create a business rule shorcut in another plan type of the same application, in order to run an application rule which is common to its plan types. I guess the workaround is to create 2 rules sharing a common script component.
As a result from this whole discussion, to disable the Planning application administrators to edit the business rules on the production platform : I think the only way is, when deploying with LCM from development to production platform :
- do not deploy calcmgr artifacts, so that they will not be visible at all and thus not editable on the production platform (but the planning administrator will be able to create new business rules)
- deploy the planning application artifacts (with its embedded deployed and launchable rules)
Do you agree ? Thanks