Kscope19, ODTUG’s user conference known for providing a rich opportunity for networking and education on Oracle technologies, is taking place this week in Seattle!
I was fortunate enough to attend the session”Getting Started with Groovy for the Non-Technical Superstars” with presenter Kyle Goodfriend, Vice President of Oracle Practice – Accelytics who introduced how to get started with Groovy.
EPBCS API has a lot of functions that can be utilized to perform tasks within Planning. Groovy is the language to interact with such functions and to execute them.
Some helpful things that I learned from attending this KSCOPE19 session about Groovy are:
- Groovy scripting can change the way form validations are done. We could get real-time warnings focusing only on those yellow edited cells on the form by making Groovy focus on that specific set of data. Focusing validation on the yellow edited cells improve a lot of performance and you could get many validations incorporated instead of keeping them out of the form to improve performance.
- I learned that using Grid iteration helps to pass edited cells to the data maps or Essbase calculation scripts and check validation on the input data based on that hence you could get performance improved data validation
- You can use Groovy scripting to add more information to the default log messages that the system generated on the JOBS screen after executing a job or a rule.
- It is also possible to sync data from one data input form to multiple BSO or ASO database within the same application. This could cut the need for more process and also reduce the number of calculation scripts or jobs used to sync multiple apps in one go.
Explore key considerations, integrating the cloud with legacy applications and challenges of current cloud implementations.
If you are wondering where to begin, some of the attached links to the documentation can help and you have to choose Groovy scripting instead of Calculation Script in the edit mode to start writing a groovy script in EPBCS. The editor may not be that friendly to indicate Groovy syntax issues.
Here is further documentation on Groovy: