This weeks short groovy tip looks at how to call your custom groovy scripts from an external application. As a SaaS application there is no way to publish your...
This weeks short groovy tip looks at how to call your custom groovy scripts from an external application. As a SaaS application there is no way to publish your groovy as a new web service using Oracle Sales Cloud, however with a little creativity it is possible to fire your code from remote systems. This is done by creating groovy scripts using the on-create or on-update Triggers of a Custom Object. The records for this custom object can then be manipulated using the generic...
This weeks short groovy tip looks at how to call your custom groovy scripts from an external application. As a SaaS application there is no way to publish your groovy as a new web service using...
This article supplements our existing discussion of the trigger event points available in Oracle Sales Cloud. Here we add some reasons around using the more...
This article supplements our existing discussion of the trigger event points available in Oracle Sales Cloud. Here we add some reasons around using the more commonly accessed trigger event points and simple illustrative use cases. Use this in combination with the technical overview to put your groovy in the right place. After Create Trigger Use this trigger when you want to programmatically set default values for a new record. The values are set immediately and will appear...
This article supplements our existing discussion of the trigger event points available in Oracle Sales Cloud. Here we add some reasons around using the more commonly accessed trigger event points and...
This brief post follows on from our series informing users of Sales Cloud how to best structure their groovy code to ensure effective performance. These is...
This brief post follows on from our series informing users of Sales Cloud how to best structure their groovy code to ensure effective performance. These is based on real investigation by our performance experts on issues that have been encountered in the past. We've already covered querying record rows using a a well formed view criteria as the most important performance tuning exercise, however one of the issues found was that some scripts repeatedly called the newView()...
This brief post follows on from our series informing users of Sales Cloud how to best structure their groovy code to ensure effective performance. These is based on real investigation by...
Did you know that if you use the file-based loaders for importing business transaction records it will bypass any custom groovy logic and object/field...
Did you know that if you use the file-based loaders for importing business transaction records it will bypass any custom groovy logic and object/field validation rules you've added through Application Composer. If you don't want that to happen, then you should use the related web services for creating/updating transaction records. This is because unlike the loaders the web services are built-into the functional flows and enforce the same validation as that on the UI. Also...
Did you know that if you use the file-based loaders for importing business transaction records it will bypass any custom groovy logic and object/field validation rules you've added through...
Introduction With Application Composer it is easy to access more than one object record using the relationships feature. All existing and newly created...
Introduction With Application Composer it is easy to access more than one object record using the relationships feature. All existing and newly created relationships are supported by the Groovy Palette to allow your scripts to manage all important records within the context of your current object. As a re-cap (see this post for more), the majority of seeded relationships you'll see in Application Composer are one-to-many, such as Opportunity to Revenue Lines, and access is...
Introduction With Application Composer it is easy to access more than one object record using the relationships feature. All existing and newly created relationships are supported by the Groovy...
This small article explains some quick facts that the Application Composer developer needs to be aware of so their valuable work done in a Sandbox does not get...
This small article explains some quick facts that the Application Composer developer needs to be aware of so their valuable work done in a Sandbox does not get lost. They key thing to understand is that once someone (any user on the whole environment) publishes a sandbox to the mainline, all existing sandboxes become invalid. As such care needs to be taken to ensure development that is intended for publication (and not just testing) is done is a systematic sequential manner....
This small article explains some quick facts that the Application Composer developer needs to be aware of so their valuable work done in a Sandbox does not get lost. They key thing to understand...
On the 17th June we partnered up with two colleagues from Oracle UK Solution Consulting and ran the first of hopefully a repeatable one day workshop covering...
On the 17th June we partnered up with two colleagues from Oracle UK Solution Consulting and ran the first of hopefully a repeatable one day workshop covering the basics of using Groovy in Oracle Sales Cloud. It was based on a requirement where we'd seen many basic Groovy usage questions from Oracle Partners and needed to offer them something more. The intention was simply to help people understand the basics of when, where, why and how to use Groovy and did not require...
On the 17th June we partnered up with two colleagues from Oracle UK Solution Consulting and ran the first of hopefully a repeatable one day workshop covering the basics of using Groovy in Oracle...
As mentioned in the overview article, we found that the single most important way to avoid performance issues is to ensure you query and fetch the fewest...
As mentioned in the overview article, we found that the single most important way to avoid performance issues is to ensure you query and fetch the fewest possible rows and fields from the database. As such this article summarizes the different techniques to do this in your Groovy scripts. Using Related Objects and Related Collections Using relationships is the recommended way to access data in your Groovy scripts, as it leverages the underlying View Objects that are already...
As mentioned in the overview article, we found that the single most important way to avoid performance issues is to ensure you query and fetch the fewest possible rows and fields from the database....
This article is a quick tip that I discovered whilst writing a script for an unrelated testcase. When writing integrations you don't not always know how much...
This article is a quick tip that I discovered whilst writing a script for an unrelated testcase. When writing integrations you don't not always know how much data you are going to get back from an API. You'll test it of course, and hopefully get some good ideas based on its specification, but we all know if complexity and variation can get in, then they will. So whilst you should ensure your calls limit the data returned as much as possible, and you parse the results for only...
This article is a quick tip that I discovered whilst writing a script for an unrelated testcase. When writing integrations you don't not always know how much data you are going to get back from an...
