5) Lists for Fraud Prevention using Account Financial Transactions.

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

The Lists Page is facilitates the creation of lists of data that can be referenced as an operator in all rules recalled in the Entity subsystem. For example, in Fraud, the Lists page can be used to maintain a list of bad customers which can be referenced using an 'is in list' or 'is not in list' operator in the Rule and Code Constructor. Lists are a good way to create Deny and Accept lists without having to embed large amounts of complexity into the Rule and Code Constrictor.

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

1.PNG

To create a list, click on the Entity Model in the tree towards the left hand side:

2.PNG

Creating a list by the name of Bad_Customers:

3.PNG

Click the Add button to confirm creation of the List:

4.PNG

In the following example, the Bad_Customer list is now available for comparison in the Gateway Rule using the 'is in list' operator:

5.png

Upon creation of the List it can be seen that the child values of this list can be administered. The list values are maintained using a List control facilitating the addition, updating and removal of List Values:

6.PNG

To add a value to the list, a button is implemented titled 'Add Value':

7.PNG

Clicking the Add button will overlay a form and create a new entry in the List control:

8.PNG

Enter the required value, in this case a Bad Customer AccountID:

9.PNG

To commit the new value, click on the tick icon:

10.PNG

Or to cancel the creation of the Value click the opposing icon:

11.PNG

Upon the successful commit of the Value, it will appear in the List control:

12.PNG

To update a List Value, click on the pen icon for the list value to be updated:

13.PNG

Upon clicking the Pen icon, a form with a text box will be over lay:

12.PNG

Update the text box with the new value:

14.PNG

Commit by clicking on the Tick icon:

10.PNG

Or to cancel the creation of the Value click the opposing icon:

11.PNG

Upon the successful commit of the Value, it will appear updated in the List control:

15.PNG

To delete a List value entry, it is a simple matter of clicking on the Disk Icon next to the List Value targeted for deletion:

16.PNG

A confirmation of the delete will be sought:

17.PNG

Upon confirming the delete, it will be removed from the list of values:

18.PNG

2) Introducing Postman

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

Integration can of course be accomplished by any tool or programming framework that facilitates HTTP interactions with a web server (e.g. .Net, Java, PHP etc). For testing it is quite common to use a HTTP Post Tool, Utility or Client application. Jube has created a page to support manual testing of HTTP messaging in the application, called Postman.

To navigate to Postman, navigate through the the menus Administration >>> HTTP Post Tools >>> Postman:

1.png

The Postman page will be presented:

2.PNG

There are three input parameters worthy of discussion in this Blog entry, keeping in mind that subsequent Blog entries will set about posting to the pre-configured models. The first parameter is represented as radio buttons and select the format of the message to be posted:

3.PNG

The Format option has no bearing on the message being submitted to the server via HTTP and only serves to tell the page how to format the input in the code editor, which affords certain parsing and formatting in the input box.

The second parameter is the URL that the message is to be posted to, which hard codes the Jube https://api.jube.io endpoint and query string delimiter, then expects only querystring parameters separated by the & character:

4.PNG

The final parameter is the Request body, which accepts ether XML or JSON to be posted to the endpoint alongside the querystring parameters:

5.PNG

An important consideration when deciding to use the embedded utility over another tool is that all requests and responses are logged to a database available to Jube support staff. Should any requests not behave as expected, then Jube support can provide more timely intervention having access to the messages and internal error messages.

As mentioned, there are several pre-configured models which exist for the purposes of training and integration testing and comprise the content of several subsequent Blog entries.