Quick dive in PBCS to show a clever approach to Restricting Form Triggered Business Rules with User Variable Selections. Enjoy!
In this post we look at on-demand data loads from source to PBCS. In on-premise Hyperion, if the requirement is to trigger on-demand data loads from within Hyperion they are a few options like Calc Manager command line triggers or Workspace Generic Jobs both of which can trigger batch scripts on the underlying servers to trigger the load from source systems to Hyperion. In PBCS this is a lot more difficult due to limitations of PBCS being a cloud solution that is not able to directly integrate with all source systems due to both technology and locations of these systems.
Lets now get a little bit more practical with an example to show how we will Login to PBCS and run some commands, but with a twist.... Why ordinary!!!! That would only be boring. Today our example, will run a program that will interact with the triggering user and execute commands based on the entered input. This program/mini-application will allow the user to list files, delete files, upload and download files to and from PBCS and execute Jobs in PBCS using Groovy commands. Please note this example can be further expanded to do much more in PBCS and leverage all the PBCS REST API functions, however the commands listed will be used as the example in this post.
This is how we do it - Write Back data to Oracle Fusion Cloud or Fusion Financials from Oracle PBCS. Not your typical blog post.
Nothing special here just a basic how to install Groovy for PBCS integration and a simple test to show is working: Hello World Println from the Hyperion Jedi.
An introduction on Groovy for PBCS. What is Groovy and Why is it relevant for Oracle PBCS. Why should you care.