SOA Magazine IV 01.2015

Figure 2 - Address Complex Type
Our HTG transformation model Engine is structured on java classes to represent human tasks attributes.
The java classes we have created for that purpose are: HumanTaskAttribute,
HumanTaskAttributeFacade, HumanTaskPayload. Their relationship can be viewed in Figure 3.
Figure 3 - HTG transformation model Engine Java Classes
HumanTaskAttribute java class represent each attribute of the human task payload regardless of being
based on a primitive type, simple type or even complex type. In those cases in which the attribute is a
complex type, each XSD element is represented as a HumanTaskAttribute. The variables we have
defined for this java class are:
name – internal attribute name. If the attribute is a complex type the name is the
concatenation of human task’s attribute name plus the name of the element inside the
XSD.
value – the value the attribute is to be set.
type – contains the type of the attribute, i.e. STRING for string attributes, INTEGER for
integer attributes, and so on. For complex types the type is similar to XSD name in order
to be easily recognized, i.e. ADDRESS for attributes based on address XSD.
isReadOnly – true if the attribute is not editable, otherwise false.
isRequired – true if the attribute is mandatory, otherwise false.
isHidden – true if the attribute must not be displayed on the interface, otherwise false.
This type of attributes behaves like auxiliary variables.
Copyright © 2015 | All Rights Reserved SOA Magazine IV 27