The output systems "XSuiteArchiveHelix2" and "XSuiteWorkflow" transfer the index data to the xSuite Helix Cloud in the form of JSON documents that correspond to a specified JSON schema. As target field names in the configuration property OutputSystem[].Field[].OutputName, the fields must be specified as they are defined in the data schema.

In the case of grouped fields, separate the individual parts of the name from each other with a period. For example, if a "Street" field is a sub-element of an "Address" group, the target field name must be Address.Street. In the field catalog of xSuite Interface, such groupings are not directly supported. However, target fields nested at any depth can be assigned to the source fields of the flat field catalog.

If the elements of the target field are arrays, there are limitations: For header data fields, only one target array is supported; however, for grouped fields, this array may exist at any level. If the value of the source field is also an array, a corresponding number of elements will be generated in the target array. For a source field containing a single scalar value, the system will generate a target array with a single value as an element. If the source field contains an array but the target field does not, only the first value of the source array will be output.

For item data fields, a target array must exist that adopts the individual items as elements. A maximum of one second array is supported below this item data array. The assignment of values within a single item is analogous to the header data fields.

The data types of the target fields are specified by the data schema. If the type of a source field differs from this schema, an implicit type conversion will be performed. If an .OutputFormat is defined for text formatting of the output value, this format will be used only if a typed source value is to be transferred into a target field of type "string."

If the Allow free fields option is active in the schema, target fields can be generated that are not predefined in the schema. The field values are then transferred unchanged in the existing data type, unless an output format is explicitly configured.