3) Inline Scripts Allocation for Fraud Prevention using Account Financial Transactions.

This Blog entry is from the Getting Started in Jube section in Learn Jube.

The Entity Models inside Jube are quite extensible via the use of Inline Scripts, which are documented comprehensively in a separate section of this document. Inline Scipts once registered in the database are available for all Entity Models, however they must be registered in a model. The Inline Script page is to facilitate the linking of Inline Scripts registered in the Jube platform and this model.

The page is available by navigating through the menu as Entity Models > References > Inline Scripts. The page is presented as a tree objects for the purposes of administering a model child objects:


Add a new Inline Script by clicking an Entity Model entry in the tree towards the left hand side:


The parameters available to Inline Script allocation are described in the following table:



This Example

Inline Script

The Inline Script to be invoked on each request being made to the Entity Model. Inline Scripts are documented extensively in another section of this documentation and this functionality serves to link that Inline Script with a model. In this example, the model has been linked with an Inline Script responsible for taking an IP address and looking up the geographic location of the IP address.


Complete the Inline Script page as the above table of parameters:


Click Add to create the first version of this Inline Script allocation in the Entity Model:


Allow the platform a few moments to syncronise the Inline Script Allocation across all of the nodes, then repeat the HTTP Post as described in previous Blog Entries using Account Financial Transactions.


Any properties that have been specified as Response Payload will be written out, more importantly all properties will be available for the creation of Gateway Rules, as dealt with in subsequent Blog entries.