Something More....

“With great power comes great responsibility” is what Oracle wants to remind us by assigning certain methods in Groovy classes as privileged methods. Privileged methods restrict executing these methods in groovy rules unless user has administrator privileges. Privileged Methods: delete: Delete method in the Member Class. This method deletes the member and all its descendants from Planning outline saveMember: saveMember method in the Dimension Class. This method returns the member that was created based on the properties map defined for the member execute: execute method in DataMap Class. This method executes the already defined data map in the application So what happens if a user with non admin privileges attempt to execute any groovy rule using any of these three functions? Here’s an example where a non admin user tries to execute a rule with data map and receives following error. It’s obvious that these three functionalities should be controlled and hand...

Groovy is the buzz word in Oracle EPM world and why shouldn’t it be. With the introduction of Groovy on EPBCS and PBCS+1 cloud options, it has made things so easy that everything seems to refreshed with Oracle EPM. On-premise version can also be enabled for Groovy, but it does not offer the groovy classes available on cloud. EPBCS is the E nterprise P lanning and B udgeting C loud S ervice while PBCS + 1 is the base PBCS service with at least one Oracle module enabled. This module could be either one of Financials, Project Financials, Workforce or Capex.  Having either one of these opens up the system to have groovy capabilities. Having capabilities to code in groovy programming language essentially makes PBCS a mini platform to play around with PBCS objects and anything with the data grid. Long back in the days of on-premise planning, we had the option to provide form validations using javascript which were replaced with data grid validation rules.  Now imagine, hav...