|
|
Link CriteriaThe Link Criteria is used to let Update, Lookup and Delete Connectors know what record to access in the external data-source. The Link Criteria is accessible in the admin tool through a tab that you will find in Update, Lookup and Delete Connectors. There are to variants of Link Criteria: Simple and Advanced. Note that usually the Connector will go to the On Error Hook if more than one record match the link criteria. Simple Link CriteriaIn the simplest case it links a value from the AssemblyLine with a value from the Data-source. To be more precise it links the value of an attribute in the work entry to a value of an attribute in the raw Connector. As an example, imagine we have a work entry with an attribute called Name. We want from a database the row of table Student where column ID is equal to work.Name. Using Simple Link Criteria (default), the syntax would be
As you will see from the Link Criteria tab, dropdowns for these three columns are provided (For the Connector Attribute column you must have previously done a Connect/Query Schema in the Configure/Attribute window in order to get dropdown values). A Connector can have many link criteria: They are added by using the Add button. If you have several link criteria, there is an implicit AND operator between them. Note that in the example above, the Value was set to $Name . The possible formats for Value are
Advanced Link CriteriaSometime, the Simple Link Criteria is not enough, because multiple link criteria are always ANDed. If you select the Advanced Link Mode checkbox, you are able to script your link criteria. You will have to populate a text string called ret.filter that will provide the Link Criteria or filter. However, you will have to know the syntax used by the underlying Raw Connector: An LDAP and an SQL Connector will have different syntax. A simple JavaScript example for a SQL Connector would be The example assumes an example where the Raw Connector has an attribute called ID (typically a column name) and that we want to match it with work.name. Note:
|
|
|