Follow-On Topics

Related Topics

# About the Mapping Tab

About the Applications Platform Connector

The Applications Platform Connector tool allows communication between Applications Platform and King Task Centre. All communication uses XML. You use the Connector to map King Task Centre data to Applications Platform objects and operations — see Supported Objects.

The XML responses received back from Applications Platform can be saved to file, or passed to another King Task Centre tool for further processing. The responses can include details of the object requested, any errors, or the values of any automatically generated ID fields.

You can use the Applications Platform Connector to provide an indirect link from your Applications Platform installation to other systems that King Task Centre is connected to. For example, if you make use of the Web Portal in Applications Platform, and have your CRM system connected to King Task Centre, you can make CRM data available to the Web Portal via the Applications Platform Connector.

Click the image to view full size.

Here you define links between the data source XML (see About the General Tab) and that required by Applications Platform. This defines how, at runtime, the incoming XML is to be translated into the XML required for the relevant object and operation.

The Object drop-down shows the available Applications Platform objects. The Operations drop-down shows the operations available for the selected Object. For more information, see Supported Objects.

Further down, the left-hand XML tree structure shows those data source fields available for mapping (see About the General Tab). The right-hand XML tree structure displays those input fields for the selected Object and Operation.

TIP:

If you have selected No data source in the General tab, you must add King Task Centre formulas and variables to the left-hand data source XML tree structure before mapping.

## Adding a New Task Step (cont.)

1. You create links by clicking and dragging a data source field (left) onto its corresponding Applications Platform Connector input field (right). Only linked fields are used in the output XML.

   King Task Centre formulas and variables can be included in the source data even when using a Task step or Custom schema (see About the General Tab) — drag them from the King Task Centre Browser to the data source’s XML; these can then be linked to the relevant input fields. King Task Centre recordsets must first be converted to XML using either the Convert Recordset to XML or Transform Data tool before they can be used here.

   Each operation has an additional field, `SupplementaryReference`, which allows for traceability when transferring data from one place to another. When mapped, the data resides locally at runtime. It is added to the output, and creates a record for reference purposes only — you can choose to map any field to `SupplementaryReference` to assist with checking where the data originated from or at what time the data transfer occurred, for example.

   Additionally, reference fields are available which are suffixed with `_id`, `_name`, or `_code`, which reference lookup fields or pick-list items in the Rollbase tenant. These can be mapped as required.

2. The Applications Platform Connector tool uses eXtensible Stylesheet Language Transformations (XSLT) to translate the received XML. The Advanced Translations (XSLT) tab shows the XSLT generated for the links created for the object and operation. Use Enable Free Type Mode to directly edit the XSLT — this is particularly useful when translating a non-standard requirement.

3. Go to the Options tab.

Using Filters with Objects

When using `get` and `upsert` `search` operations, you can make use of filters to limit the data involved. At runtime, these fields are treated as “where clauses”. Available filter conditions are:

`<>` — Not equal to | `<=` — Less than or equal to
`=` — Equal to | `>=` — More than or equal to
`<` — Less than | `LIKE`
`>` — Greater than |

The following filter conditions are also available, but require options in the global configuration's Option tab to be set (see About the Options Tab):

|  | `=(CS)` — Use this filter for case-sensitive queries. This filter uses the database collation specified for the User Collation parameter.

|  | `=(CS-CAST)` — If the mapped-to input field is a blob data type, use this filter to instruct the Applications Platform Connector to use the data type specified in the String Cast Type parameter instead.

The presence of multiple filter fields implies that all conditions must be met.

Nominated fields must be mapped to be included in the output XML. You add filter conditions by right-clicking the output XML field, and selecting Set as Filter. By default, all filters are set to “equal to”. To change the filter condition, right-click the field again, and select Set Filter Condition. Change the filter condition as required.

A Note About the Comment Field in Applications Platform

The `comment` field in an Applications Platform object is only available for `CREATE` and `UPDATE` operations. However, it should be noted that an `UPDATE` operation only appends new text to the field rather than overwriting.

Copyright © 2018 Quadrant Software B.V. All rights reserved.