We have plan to move to SAAS sometime in future and before that we want to make ourself SAAS compliant.
I would like to seek input on converting custom DB functions (which has cursor statement in it and it also does some db update and then returns some value) into reusable SAAS compliant thing.
One approach is to put the whole logic in the individual gel scripts, but in this case if there is a change required in future then we may need to change all of the gel scripts.
Could there be a generic architecture/solution for this (re-usability is the key here) ?
GEL scripts can initiate other processes (by calling InvokeAction webservices), so if you could code your main "custom function" as a standalone GEL script it could be called from other GEL script processes - so you would end up with just one piece of code to maintain.
Thanks for the quick response David.
Assume there are 5 Processes wherein we are calling(reusing) the main "Custom function" gel script/process. Now if there is a scenario where all 5 processes triggers at the same time, would this be able to handle the scenario properly ?
Well I was rather assuming that each of your 5 other processes would be initiating your common process with a different "parameter" (I might be confusing myself here with 'jobs' though?) ? Or perhaps the "Do not start a new process if one is already running" option on a process is needed? Or perhaps your GEL code would need to cater for that (if its going to cause you a problem!).
[ I am obviously just GUESSing at what you are trying to do ]
You might also want to look at these discussions about "reusable GEL components"...
RE: Using core:include in Gel Scripts
GEL Script : "Subprocedures"?
RE: Reuse XOG SOAP in GEL as subprocess?