The dacsin type

A dacsin type object represents the integration message that triggered the workflow script.

Remarks

The dacsin object is read-only.

A dacsin object is available only in scripts that are triggered by an incoming integration message, and so have the for dacsdacsem-nametrigger declaration. You can access the fields of the trigger-message using the dacs variable. The names and structure of the data in the triggering message is determined by its dacsem integration message schema file. The following sections show examples the most common incoming integration message patterns and the way workflow scripts can process them.

For further details on integration message schema and scripting, see the dedicated reference guide.

Accessing elements and attributes in an incoming integration message

The workflow scripts in the samples below are triggered by incoming integration messages. To try the following samples out for yourself, you'll need to upload an intconf.xml file that defines an inbound integration endpoint and the integration messages and schema that they accept, so that these workflow scripts can reference them. You'll also need to create the inbound endpoint on your Cloud instance that match the name specified in the intconf.xml file.

For integration messages with simple XML elements, such as the one below,

elementWithContent.dacsem

schema elementWithContent meta 'rockyJupiter:elementWithContent'
  namespace "http://schemas.rockyjupiter.com/elementWithContent"
dragee: element {
  biddie: attribute of type dtl (dtf yyyy"-"MM"-"dd);
  feute: content of type int;
}

the element and attribute values are accessible as fields of the dacs variable.

elementWithContentRead.rfs

server program elementWithContentRead for dacs elementWithContent
{
  trace dacs.dragee;
  trace dacs.dragee.biddie;
  trace dacs.dragee.feute;
}

Accessing optional elements in an incoming integration message

When the integration message schema defines a child element as optional,

optionalElement.dacsem

schema optionalElement meta 'rockyJupiter:optionalElement'
  namespace "http://schemas.rockyjupiter.com/optionalElement"
cuca: element {
  edna: optional element {
    svelte: attribute of type string;
  }
}

the workflow script that accesses the optional values first needs to test whether the element exists in the message or not.

optionalChoiceRead.rfs

server program optionalElementRead for dacs optionalElement
{
  if(dacs.cuca.edna != null) {
    trace dacs.cuca.edna.svelte;
  }
}

Accessing lists in an incoming integration message

If an integration message schema defines a list element,

listSample.dacsem

schema listSample meta 'rockyJupiter:listSample' namespace "http://schemas.rockyjupiter.com/listSample"
esm: element Fremd {
  carls: optional wrapped list of element carl {
    lewis: attribute of type float;
    bolt: content of type int;
  }
  grapes: list of element grape of type string without whitespace;
}

the items in the list are accessible as values of a conventional list object.

listSampleRead.rfs

server program listSampleRead for dacs listSample
{
  if (dacs.esm.carls != null)
  {
    foreach(var carl in dacs.esm.carls) trace carl;
  }
  foreach(var grape in dacs.esm.grapes) trace grape;
}

For more details on how inbound integration works, read the relevant tutorial.

Mobile form submission processing

The dacstype type

Developer Documentation

Workflow Script Reference Guide

The dacsin type