Copyright © Cloud Software Group, Inc. All Rights Reserved

Editor

The Editor tab is used to specify a data schema for input or output of an activity. This is useful when the data does not have a well-known structure. The Editor tab is usually named for the type of schema you are creating. For example, the tab may be named "Input Editor" or "Output Editor".

For example, an email message has a well-known data structure, and therefore does not need a special datatype for its input. A JMS message, however, can have application-specific properties of any datatype. The Editor tab allows you to define the schema for any activities that require a specialized input or output schema.

You can use a simple datatype, or you can define a group of data elements on this tab. You can also reference XML schema or ActiveEnterprise classes stored in the project. Once defined, the schema appears on the appropriate tabs of the activity. The data in the schema then becomes available to other activities in the process definition.

The following illustrates the Editor tab. In this example, the Editor tab is labeled "Input Editor" indicating this is the activity’s input.

To define a schema on this tab, use the icons above the schema tree to add, delete, or move data items. Then use the fields of the dialog to specify the datatype of each item.

 

Field	Description
Content	Defines the content of the element. The other fields that appear depend upon which content type is selected. See Table 13 for more information about the content type.
Name	The name of the element.
Cardinality	The qualification for the data item. Data items can be specified as one of the following: • Required — the data item is required and must be supplied when the process is called. • Optional (?) — the data item is optional. • Repeating, Zero or More (*) — The data item is a list that has zero or more elements. • Repeating, One or More (+) — The data item is a list that has one or more items.
Type	The type of data. Can be any of the following: • XML Type Reference — must locate the stored XML schema definition. • Any of the datatypes described in Table 14.
Schema Name	Stored XML schema that contains the element or type you want to reference.
Type Name	Type in a stored XML schema you want to reference.

Table 13 describes the potential content types for data elements.

Table 13 Content types for schema elements

Content Type	Description	Other Fields for This Content Type
Complex Element	An element that contains other elements. This is like a structure in a programming language. The complex element can contain zero or more elements of other types, and it can contain other complex elements.	Name Cardinality
Element of Type	An element with a specified datatype. You can specify a scalar datatype (string, integer, and so on), you can reference an XML type, or specify the TIBCO ActiveEnterprise Any dataype.	Name Cardinality Type   Other fields depending upon the datatype selected
XML Element Reference	A reference to an element in a stored XML schema. See TIBCO Designer documentation for more information about XML schema.	Cardinality Schema Element
Attribute of Type	An attribute with a specified datatype. You can specify a scalar datatype (string, integer, and so on), you can reference an XML type, or specify the TIBCO ActiveEnterprise Any datatype.	Name Cardinality Type Other fields depending upon the datatype selected.
Sequence	A sequence of elements. Each item in the sequence is a structure of the sub-elements of this element.	Cardinality
Choice	A choice of elements. The datatype of this element can be one of the sub-elements defined.	Cardinality
All	The datatype of this element can be all of the datatypes of the sub-elements defined.	Cardinality
XML Group Reference	A reference to an XML group in a stored XML schema. See TIBCO Designer documentation for more information about XML schema.	Cardinality Schema Model Group
Any Element	A reference to any XML Element. You can use the Coersion button to supply a reference to the XML Element for this item when it appears in the input or process data.	Cardinality Validation
WSDL Message	A reference to a message defined in a WSDL File resource. Use the Browse button to bring up a dialog for locating WSDL files within the project.	WSDL Message

Table 14 describes the datatypes available for data.

Table 14 Icons for schema datatypes

Icon	Description
	String or character value. You can specify the type of string as one of the following: • String • Normailzed String • Token • Language • Name • NC-Name • Q-Name • Name Token • Name Tokens • ID • ID ref • ID refs • Entity • Entites
	Integer value. You can specify the size of the integer as one of the following: • Byte • Short • Int • Long • Unsigned Byte • Unsigned Int • Unsigned Long • Integer • Positive Integer • Negative Integer • Non-positive Integer • Non-negative Integer
	Floating point number. You can specify the size of the schema item as float, double, or decimal.
	Boolean value.
	Date or Time. This can be any of the following datatypes: • Time • Date • Date & Time • Duration • Day • Month • Year • Year & Month • Month & Day
	Base 64 or hexidecimal value.
	An HTTP Uniform Resource Identifier.
	Complex element. Container for other datatypes.
	XML element or group reference.
	Sequence. Signifies that the contained sub-elements are repeated in an ordered sequence.
	Any Type. Represents a schema item with the TIBCO ActiveEnterprise datatype any. This node can be specified as any other datatype or a reference to an XML Type or AE Class.
	Any Element. Represents a schema item that can be a reference to any XML Element. You can use the Coersion button to supply a reference to the XML Element for this item.
	Choice. Specifies that the schema element can be one of a specified set of datatypes.

 

Copyright © Cloud Software Group, Inc. All Rights Reserved