Extra information for delivered items

OMD stores changed quantities and checklist values in a local extra field, similar to the extra field on itemsPlanned attachments. To display the content of the entered quantities and checklist values, a stylesheet can be used. The stylesheet must be defined in the itemsPlannedLocalExtraTemplate. The resulting HTML code will be displayed on the Details and Signature overview screens of OMD Mobile.

Alternatively, the itemsPlannedLocalExtraSignature can be applied should the display of information on the signature overview screen differ.

The following attachment attributes are always injected into the first Data element before starting the transformation:

planned, format, content, reference, unitOfMeasure, processFlow, subType, language

In case the extra field of the attachment also contains an XML document, this document will be appended to the Data element:

<Data planned="...">
  <Extra>
   ... content of the extra value (possibly an XML document, otherwise plain text)
  </Extra>
</Data>

If items are aggregated, multiple <Data/>elements are grouped in the following way:

<Group> 
   <Data ...> 
      <Extra> 
         <Data ... /> 
      </Extra> 
   </Data> 
   <Data ... > 
      <Extra> 
         <Data ... /> 
      </Extra> 
   </Data> 
</Group>

Template Example

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="text" omit-xml-declaration="yes" indent="no"/>
    <xsl:template match="/Data">(<xsl:value-of select="@planned"/>) <xsl:value-of select="@Q1"/>/<xsl:value-of select="@Q2"/>/<xsl:if test="@lastDelivery='true'">Letzte Lieferung</xsl:if>/<xsl:value-of select="@Q3"/>
    </xsl:template> 
    <xsl:template match="/Group">(<xsl:value-of select="sum(./Data/@planned)"/>) <xsl:value-of select="sum(./Data/@Q1)"/>/<xsl:value-of select="sum(./Data/@Q2)"/>/<xsl:if test="./Data/@lastDelivery='true' and (./Data/@lastDelivery='false' or ./Data[not(@lastDelivery)])">Teilw. letzte Lieferung</xsl:if><xsl:if test="./Data/@lastDelivery='true' and not((./Data/@lastDelivery='false' or ./Data[not(@lastDelivery)]))">Letzte Lieferung</xsl:if>/<xsl:value-of select="@Q3"/>
    </xsl:template> 
</xsl:stylesheet>

The attributes used in the stylesheet must match the widget codes in the Mobile UI as defined by the process flow of the itemsPlanned attachment.

Note that, while filling the Usage / Request activity on the mobile App, the localExtra Data element contains an additional attribute called committed with value false. This allows the stylesheet to distinguish between the filling and the listing of already confirmed usage / material request.

ERP systems can query itemsDelivered and other attachments by using the Gateway HTTP request². They can then process the tasks internally according to the quantities and values provided.

The output of the XSL transformation can contain low-level HTML and is rendered accordingly, if itemsPlannedLocalExtraAsHtml is set to true. This is an underdocumented Android feature. By now, support for the following Tags is known, plus some attributes, e.g. style=:

<br/>, <p/>, <div/>, <em/>, <b/>, <strong/>, <cite/>, <dfn/>, <i/>, <big/>, <small/>, <font/>, <blockquote/>, <tt/>, <monospace/>, <a/>, <u/>, <sup/>, <sub/>

The process flow preference itemsDeliveredShowDetails enables the enrichment of the XML data in an itemsDelivered's extra field, with prompts and values of all widgets, including default values.

The process flow preference removeVariableVisibilityAttributes activates the removal of attributes from the XML in the extra-field, when the related widgets are hidden from the Mobile UI by a dynamic visibility-rule expression. Attributes of widgets with a constant expression (e.g. the visibility expression "false" or "1 == 2") are always included in the XML.

². See Integration Documentation for details ↩