Follow-On Topics

Related Topics

# Tool Output

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.

The Applications Platform Connector tool outputs three documents:

|  | `InputData`

|  | `OutputData`

|  | `ErrorData`

All outputs can be:

|  | Used directly by subsequent tool steps which consume XML data inputs

|  | If required, use the Convert XML to Recordset tool to convert the XML to a King Task Centre recordset first

|  | Accessed using the output or error objects for response data (`XmlString`), or the output or error schema (`XmlSchema`) present in the Task Browser; for example, saving to file or for inclusion within an email.

## About the InputData XML Document

This document contains the XML received by the Applications Platform Connector tool.

## About the OutputData XML Document

The `OutputData` document contains:

|  | Data returned from Applications Platform for a `READ`, `SEARCH`, `UPDATE`, or `DELETE` operation

|  | The key fields for the entity instances affected by the used operation

For example, if using a `CREATE` operation, the key fields for the top-level object instances that are created are returned.

|  | `SupplementaryReference`

## About the ErrorData XML Document

The ErrorData document is structured as follows:

`<Error>` — All errors are created as an `<Error>` node, with the following sub-nodes:

`<Object />` — The name of the requested object

`<CODE />` — The error code returned by Applications Platform

`<MESSAGE />` — The corresponding error message

`<EXTENDEDINFO />` — A string containing additional information about the error

`<INPUTDATA />` — The header input data (excluding child nodes) mapped for the object, plus all data contained in the `SupplementaryReference` field

`</Error>`

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