ReakTor Labz | ProaKtor

> > > InsertReferenceData


10th July 2016

Sean Hoppe Consulting Group

In a previous tip, we discussed what the User Reference values are, why you should use them, and how to populate them in your Ruleset. In this tip, we’ll discuss how to configure your Rulesets to allow your purchase orders, invoices, and other EDI documents to be searched using Dashboard.

In your Ruleset, there is a rule called InsertReferenceData.

InsertReferenceData rule

This rule can be used to pass important data from Cleo Clarify into Dashboard to search using a custom name, or one of the User_Reference variables that are pre-configured already.

The properties and parameters of the rule are defined below.

InsertReferenceData rule parameters and values

The Log_of_Message_Id property needs to be populated with the internal Log of Message Identifier, which will be used to reference the ST-SE message data during the process.  This value is located in the env category of the variables tab, as shown below.

Log of Message Identifier in the environment category

The Search_Code property is the custom text name of the searchable field inside of Dashboard.  In our example, PO_Num will be the field name and allow you to search on values that have been populated in the Reference_Data property.  The Reference_Data property can be populated by a variable, or simply include the value that you wish to search upon.  

In the example shown below, we are concatenating the Name value in the N102 from our Inbound EDI 850 and the Purchase Order number in the BEG03.  The result will be populated and can be searched for after the process runs successfully.

Concatenting Purchase Order number and trading partner name

By: on