DTD Formats

Element	Description	Example Value
actions	Defines the actions that were performed. Defines zero or more occurrences of the following subelements: error setvariable activatetask dotask marktaskdone unmarktaskdone unassigntask settaskcomment settaskpriority settaskproperties settaskduedate rerouted assigntask instantiated auditentry evaluatecondition workflowaborted setworkflowcomment	See Audit DTD Example.
activatetask	Defines the following attributes: time: Time at which the task was activated. taskid: ID of the task that has been activated. name: Name of the task that has been activated.	<activatetask time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
assigntask	Defines the following attributes: time: Time at which the task was assigned. taskid: ID of the task that has been assigned. name: Name of the task that has been assigned.	<assigntask time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
auditentry	Defines the following attributes: time: Time at which the audit entry was logged. taskid: ID of the task for which an audit entry has been logged. name: Name of the task that for which an audit entry has been logged.	<auditentry time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
completed	Time at which the task execution completed.	<completed>2001-06-12 12:45:45.115 </completed>
dotask	Defines the following attributes: time: Time at which the task was executed. taskid: ID of the task that has been executed. name: Name of the task that has been executed.	<dotask time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
error	Defines the following attributes: time: Time at which the error occurred. id: Error ID.	<error time="2001-06-12 12:45:44.824" id="2"/>
evaluatecondition	Defines the following attributes: time: Time at which a condition was evaluated. taskid: ID of the task for which a condition has been evaluated. name: Name of the task for which the condition has been evaluated.	<evaluatecondition time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
instanceid	ID of the workflow instance that is the target of the response document.	<instanceid> 2 </instanceid>
instantiated	Defines the following attributes: time: Time at which the task was instantiated. name: ID of the task that has been instantiated.	<instantiated time="2001-06-12 12:45:44.824" name="Start Test"/>
marktaskdone	Defines the following attributes: time: Time at which the task was marked complete. taskid: ID of the task that has been marked as complete. name: Name of the task that has been marked as complete.	<marktaskdone time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
requestor	ID requestor.	<requestor> wlisystem </requestor>
rerouted	Defines the following attributes: time: Time at which the task was rerouted. taskid: ID of the task that has been rerouted. name: Name of the task that has been rerouted.	<rerouted time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
settaskcomment	Defines the following attributes: time: Time at which the task comment was set. taskid: ID of the task for which a comment has been set. name: Name of the task for which a comment has been set.	<settaskcomment time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"> This is a comment. </settaskcomment>
settaskduedate	Defines the following attributes: time: Time at which the task due date was set. taskid: ID of the task for which a task due date has been set. name: Name of the task for which a task due date has been set.	<settaskduedate time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"> </settaskduedate>
settaskpriority	Defines the following attributes: time: Time at which the task priority was set. taskid: ID of the task for which a priority has been set. name: Name of the task for which a priority has been set.	<settaskpriority time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"> </settaskpriority>
settaskproperties	Defines the following attributes: time: Time at which the task properties were set. taskid: ID of the task for which properties have been set. name: Name of the task for which properties have been set.	<settaskproperties time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"> </settaskproperties>
setvariable	Defines the following attributes: time: Time at which the variable was set. variable: Name of the variable in XML name token (NMTOKEN) format.	<setvariable time="2001-06-12 12:45:44.824" variable="test1"> value1 </setvariable>
setworkflowcomment	Defines the following attributes: time: Time at which the workflow comment was set. taskid: ID of the task for which a comment has been set. name: Name of the task for which a comment has been set.	<setworkflowcomment time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"> </setworkflowcomment>
started	Time at which the task execution started.	<started> 2001-06-12 12:45:44.824 </started
templatedefinitionid	ID of the workflow template definition that is the target of the response document.	<templatedefinitionid> 2 </templatedefinitionid>
templateid	ID of the workflow template that is the target of the response document.	<templateid> 2 </templateid>
template-name	Name of the workflow template.	<template-name> Start Test </template-name>
unassigntask	Defines the following attributes: time: Time at which the task was unassigned. taskid: ID of the task for which assignment has been revoked. name: Name of the task for which assignment has been revoked.	<unassigntask time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
unmarktaskdone	Defines the following attributes: time: Time at which the task was marked as incomplete. taskid: ID of the task that has been marked as incomplete. name: Name of the task that has been marked as incomplete.	<unmarktaskdone time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>
wlpirequest	Defines the request, including the following subelements: started requestor templateid templatedefinitionid instanceid actions completed	See Audit DTD Example.
wlpiresponse	Root element. Defines the following subelements: instanceid templatedefinitionid wlpirequest	See Audit DTD Example.
workflowaborted	Defines the following attributes: time: Time at which the workflow was aborted. taskid: ID of the task that caused the workflow to be aborted. name: Name of the task that has been marked as incomplete.	<workflowaborted time="2001-06-12 12:45:44.824" taskid="2" name="Task 1"/>

Element	Description	Example Value
calendar	Root element. You must define the following subelements: id name timezone interval (zero or more)	See Business Calendar DTD Example.
date	Date to be included or excluded. This date must be specified using the following format: month dd, yyyy where month specifies the name of the month (such as January), dd specifies the day, and yyyy specifies the year.	<date> December 25, 2001 </date>
dateinterval	Interval of time to be included in or excluded from the calendar. You must define the following subelements: fromdate todate	<dateinterval> <fromdate> January 1, 2001 </fromdate> <todate> January 1, 2002 </todate> </dateinterval>
days	Day to be included or excluded. The value of this element is a text string specifying the name of the day (such as Sunday).	<days>Saturday</days>
exclude	Rule that defines an interval of time to be excluded from the main interval. You can define the following subelements: months (zero or more) days (zero or more) date (zero or more) timeinterval (zero or more) dateinterval (zero or more)	<exclude> <days> Saturday, Sunday </days> <date> January 1, 2001 </date> </exclude>
fromdate	Subelement of interval or dateinterval. When used as subelement of interval, specifies the start date for an interval. When used as subelement of dateinterval, it is specific to the include or exclude. This date must be specified using the following format: month dd, yyyy where month specifies the name of the month (such as January), dd specifies the day, and yyyy specifies the year.	<fromdate> January 1, 2001 </fromdate>
fromtime	Start time from which the business calendar is in effect, or a subelement of timeinterval, in which case it specifies a range of time to include or exclude. This time must be specified using the following format: hh:mm, where hh specifies the hour and mm specifies the minutes.	08:00
id	Unique ID.	<id>10234</id>
include	Rule that defines an interval of time to be included in the main interval. You can define the following subelements: months (zero or more) days (zero or more) date (zero or more) timeinterval (zero or more) dateinterval (zero or more)	<include> <timeinterval> 08:00, 17:00 </timeinterval> </include>
interval	Interval of time that the calendar is in effect. You must define the following subelements: fromdate todate exclude (zero or more) include (zero or more)	<interval> <fromdate> 20010101 </fromdate> <todate> 20020101 </todate> <exclude> <date> 20011225 </date> <days> Saturday, Sunday </days> </exclude> <include> <timeinterval> 08:00. 17:00 </timeinterval> </include> </interval>
months	Month to be included or excluded. The value of this element is a text string specifying the name of the month (such as January).	<months> August </months>
name	Calendar name.	<name> MyCalendar </name>
timeinterval	Interval of time to be included in or excluded from the calendar. You must define the following subelements: fromtime totime	<timeinterval> <fromtime> 17:00:00 </fromtime> <totime> 08:00:00 </totime> </timeinterval>
timezone	Calendar time zone. (See Note following table for valid values.)	<timezone> EST </timezone>
todate	Date until which the business calendar remains in effect. This date must be specified using the following format: month dd, yyyy where month specifies the name of the month (such as January), dd specifies the day, and yyyy specifies the year.	<todate> January 1, 2002 </todate>
totime	Time until which the business calendar is in effect. This time must be specified using the following format: hh:mm, where hh specifies the hour and mm specifies the minutes.	<totime>17:00</totime>

Element	Description	Example Value
actionid	Action ID.	<actionid> 959395846210 </actionid>
call-addin	Root element. You must define the following subelements: actionid parm (zero or more) You must define the following attributes: name: Fully-qualified Java class name of the worklist addin to invoke, which must implement the com.bea.wlpi.client.worklist.WorklistAddIn interface. This attribute is required. mode: Program mode specifying whether or not the run-time client blocks while executing the client request. This value can be set to sync (synchronous mode), to block the run-time client until completion of the request, or async (asynchronous mode), to execute the client request as a background task. This attribute defaults to async.	See Client Call Addin Request DTD Example.
parm	Parameter. This value can be any character string.	<parm> itemNumber </parm>

Element	Description
call-addin	Root element. The value of this element can consist of any combination of elements and text.

Element	Description	Example Value
call-program	Root element. You must define the following subelements: actionid parm (zero or more) env-var (zero or more) You must define the following attributes: mode: Program mode specifying whether or not the run-time client blocks while executing the client request. This value can be set to sync (synchronous mode), to block the run-time client until completion of the request, or async (asynchronous mode), to execute the client request as a background task. This attribute defaults to async. name: Program name. This attribute is required.	See Client Call Program Request DTD Example.
actionid	Action ID.	<actionid> 992456131534 </actionid>
parm	Parameter definition. This value can be any character string.	<parm> C:\WLPI\readme.txt </parm>
env-var	Environment variable definition. You must define a name attribute that specifies the name of the environment variable in XML name token (NMTOKEN) format.	<env-var name="TEMP"> C:\TEMP </env-var>

Element	Description	Example Value
call-program	Root element. This element is empty. You must define the exit-value attribute to specify a numeric exit code, as retrieved by the operating system, that is meaningful within the context of the calling workflow. Consult the appropriate program documentation for more information on valid exit codes. This attribute is required.	See Client Call Program Response DTD Example.

Element	Description	Example Value
actionid	Action ID.	<actionid> 990705990915 </actionid>
message-box	Root element. You must define the actionid subelement. You must define the following attributes: title: Text that appears in the title field of the message box. This attribute is optional. style: Message box style. The value of this element can be set to error, information, plain, question, or warning. It defaults to plain. options: Message box button options. Table A-8 defines the message box options that are valid based on the style value assigned.	See Client Message Box Request DTD Example.

Message Box Style	Message Box Options
error	ok, ok_cancel
information	ok
plain	ok, ok_cancel, yes_no, yes_no_cancel
question	yes_no, yes_no_cancel
warning	ok, ok_cancel

Element	Description	Example Value
message-box	Root element. This element is empty. You must define the option attribute to specify the option entered by the user. This value can be ok, yes, no, or cancel. This attribute is required.	See Client Message Box Response DTD Example.

Element	Description	Example Value
call-addin	Request for client to call a java addin that is compliant with the Client Call Addin Request DTD.	See Client Call Addin Request DTD Example.
call-program	Request for client to call an external program that is compliant with the Client Call Program Request DTD.	See Client Call Program Request DTD Example.
custom	Custom request consisting of any combination of elements and text.
instanceid	ID of the workflow instance that is the target of the response document.	<instanceid> 3 </instanceid>
message-box	Request for client to respond to a message that is compliant with the Client Message Box Request DTD.	See Client Message Box Request DTD Example.
set-variables	Request for client to set variables that is compliant with the Client Set Variables Request DTD.	See Client Set Variables Request DTD Example.
templatedefinitionid	ID of the workflow template definition that is the target of the response document.	<templatedefinitionid> 2 </templatedefinitionid>
wlpiresponse	Root element. You must define the following subelements: wlpiresponse instanceid templatedefinitionid call-program \| call-addin \| set-variables \| message-box \| custom (zero or more)

Element	Meaning
calladdin	Client Call Addin Request DTD, ClientCallAddInReq.dtd
callpgm	Client Call Program Request DTD, ClientCallPgmReq.dtd
msgbox	Client Message Box Request DTD, ClientMsgBoxReq.dtd
setvars	Client Set Variables Request DTD, ClientSetVarsReq.dtd

Element	Description	Example Value
actionid	Action ID.	<actionid> 991408825931 </actionid>
set-variables	Root element. You must define the following subelements: actionid variable (one or more) You can also define the title attribute to specify the text that appears in the title field of the set variables box. This attribute is optional.	See Client Set Variables Request DTD Example.
variable	Variable to be set. You must define the following attributes: name: Name of the variable to be set, specified in XML name token (NMTOKEN) format. This attribute is required. prompt: Text displayed in a dialog box as a cue to the user, specified in XML name token (NMTOKEN) format. This attribute is optional.	<variable name="ShipToState" prompt="An error has occurred in processing this order. Please enter the valid US state abbreviation for shipping:"> </variable>

Element	Description	Example Value
set-variables	Root element. You must define one or more variable subelements.	See Client Set Variables Response DTD Example.
variable	Variable value. You must define the name attribute specifying the name of the variable that was set in XML name token (NMTOKEN) format. This attribute is required.	<variable name="ShipToState"> CA </variable>

Element	Description
message	Single message. You must define the following subelements: text parm (zero or more)
messages	List of messages. You must define the following subelements: title (zero or one) message (zero or more)
parm	Parameter value with which to replace the corresponding parameter marker in the localized message. You can define the following attribute. type: Parameter type.
text	Message formatted in the locale of the server. You must define the following attribute. msg-num: Message number.
title	Title for the message list. You must define the following subelements: text parm (zero or more)

Element	Description
from	Date from which the statistics report should be generated. This date must be specified using the following format: yyyyMMddHHmm, where yyyy specifies the year, MM specifies the month, dd specifies the day, HH specifies the hour, and mm specifies the minutes.
group	Boolean flag specifying whether or not to group the totals.
id	ID of the task to include in the report.
include	List of users and/or roles to include in the report. You can define the following subelements: user (zero or more) role (zero or mroe)
name	Name of task to include in thes report.
org	Organization for which you are generating a report.
role	Name of role to include in the report.
statisticsrequest	Root element. You must define the following subelements: org templatedefinitionid tasks (from, to) (zero or one) include group
task	Task to include in the report. You must define the following subelements: name id
tasks	List of tasks to include in the report. You must define zero or more occurrences of the following subelement: task
templatedefinitionid	ID of the template definition for which you are generating a report.
to	Entity date of the period for which the statistics report should be generated. This date must be specified using the following format: yyyyMMddHHmm, where yyyy specifies the year, MM specifies the month, dd specifies the day, HH specifies the hour, and mm specifies the minutes.
user	Name of user to include in the report.

Element	Description
average	Average amount of time spent performing a task.
item	Item for which you are gathering the workload report. You must define the following subelements: task user (zero or one) number total average stddev min max
max	Maximum amount of time spent performing a task.
min	Minimum amount of time spent performing a task.
number	Number of tasks performed.
statistics	Root element. You must define zero or more occurrences of the following subelement: item
stddev	Standard deviation of the times spent performing a task; indicates how much the AVERAGE truly represents the numbers upon which it was calculated.
task	Task upon which the following are calculated.
total	Total amount of time spent performing a task.
user	User that performed the task.

Element	Description
name	Name of the template.
plugin	Plug-in entry. One element appears for each plug-in referenced by a template, and for each plug-in that defines its own template property. Optionally, you can define the following subelement: plugin-data. You must define the following attributes: name: Plug-in name major-version: Major version of the plug-in software minor-version: Minor version of the plug-in software vendor: Vendor name url: URL (defaults to an empty string) For more information about programming plug-ins, see Programming BPM Plug-Ins for WebLogic Integration.
plugin-data	Plug-in data consisting of any combination of elements and text. You must define the following attributes: name: Name of the plug-in. This attribute is required. ID: Unique ID, provided by the plug-in, for the associated value object. This attribute is required. For more information about programming plug-ins, see Programming BPM Plug-Ins for WebLogic Integration.
plugins	Plug-in definition, used only if plug-in is provided. You can define zero or more occurrences of the following subelements: plugin For more information about programming plug-ins, see Programming BPM Plug-Ins for WebLogic Integration.
template	Root element. You must define the following subelements: templateId name plugins (zero or one)
templateId	ID of the template.

Table A-18 Template Definition DTD Elements

Element	Description	Example Value
ActionAuditEntry	Action used to define audit entries that are published to the JMS wlpiAudit topic, in addition to the default audit entries that include major interactions and/or changes. In the Studio, you define this action by selecting Make Audit Entry within the Miscellaneous actions category of the Add Actions dialog box. You must define the following subelements: notes audittext	<ActionAuditEntry> <notes></notes> <audittext> "Workflow cancelled." </audittext> </ActionAuditEntry>
ActionBusinessOperation	Action used to invoke predefined business operations on an EJB or Java class. The results of invoking the business operation can be assigned to workflow variables. In the Studio, you configure business operations by selecting Business Operations from the Configuration menu. You invoke them, when defining actions, by selecting Perform Business Operation within the Integration actions category of the Add Actions dialog box. You must define the following subelements: notes descriptorid description result result-type instance-variable instance-variable-type parms iviewx (zero or one) iviewy (zero or one)	<ActionBusinessOperation> <notes> This is a note. </notes> <descriptorid> 1 </descriptorid> <description> Check Inventory </description> <result> Inventory </result> <result-type> integer </result-type> <instance-variable> PobeanHandle </instance-variable> <instance-variable-type> session </instance-variable-type> <parms> <parm> ItemNumber </parm> </parms> <iviewx>150</iviewx> <iviewy>70</iviewy> </ActionBusinessOperation>
ActionCallProgram	Action used to invoke predefined executable program. The results of invoking the program can be assigned to workflow variables. In the Studio, you define this action by selecting Call Program within the Integration actions category of the Add Actions dialog box. You must define the following subelements: notes program arguments	<ActionCallProgram> <notes> This is a note. </notes> <program> ProgramA </program> <arguments> CurrentUser() </arguments> </ActionCallProgram>
ActionCancelEvent	Action used to cancel a workflow event that is defined within a workflow. In the Studio, you define this action by selecting Cancel Workflow Event within the Miscellaneous actions category of the Add Actions dialog box. You must define the following subelements: notes target	<ActionCancelEvent> <notes> This is a note. </notes> <target> 987445252339 </target> </ActionCancelEvent>
ActionCondition	Action used to evaluate a conditional expression at run time and depending on the result, to perform alternative sequences of subactions. In the Studio, you define this action by selecting Evaluate Condition within the Miscellaneous actions category of the Add Actions dialog box. You must define the following subelements: notes condition actions	<ActionCondition> <notes> This is a note. </notes> <condition> CurrentUser()= "joe" </condition> <actions> <ActionTaskUnassign> <notes> This is a note. </notes> <target> 963511923442 </target> </ActionTaskUnassign> </false> <true> <ActionTaskDone> <notes> This is a note. </notes> <target> 963511923442 </target> </ActionTaskDone> </actions> </ActionCondition>
ActionExitErrorHandler	Action used to exit an exception handler. In the Studio, you define this action using the Exit Exception Handler dialog box. You can access the dialog box by clicking the Add button in the Exception Handler Properties dialog box when the Actions on Commit or Actions on Rollback tab is selected. You must define the following subelement: notes You must specify one of the following values for the exit-type attribute to specify a method to be used by the existing error handler: rollback - Marks the user transaction as rollback only, returning the workflow to the state in which it existed prior to the start of the transaction. The exception is propagated to the client (if any) as a WorkflowException. In the rollback path, this is the only option available. Certain EJBs can either mark a transaction for rollback only, by calling a UserTransaction method, or they can throw an unchecked exception across a container boundary. In either case, WebLogic Server rolls back the transaction. stop - Exits the error handler and does not execute any follow-on actions. retry - Exits the error handler and attempts to retry the failed operation. (The failed operation is an action or the setting of a variable.) continue - Stops the execution of the exception handler and attempts to continue the execution of the workflow at the next operation. (The next operation is the next action to be performed or variable to be set.)	<ActionExitErrorHandler exit-type="rollback"> <notes> This is a note. </notes> </ActinoExitErrorHandler>
ActionExpression	Action used to set a workflow variable. In the Studio, you define this action by selecting Set Workflow Variable within the Workflow actions category of the Add Actions dialog box. You must define the following subelements: notes variable (expression \| xml)	<ActionExpression> <notes> This is a note. </notes> <variable> CustomerState </variable> <expression> "NJ" </expression> </ActionExpression>
ActionInvokeErrorHandler	Action used to enable the invocation of the specified exception handler. Upon execution of this action, WebLogic Process Integrator sends the user-defined XML document to the exception processor and invokes the specified handler. In the Studio, you define this action by selecting Invoke Exception Handler within the Exception Handling Actions category of the Add Actions dialog box. You must define the following subelements: notes xml (zero or one) You must specify a text string specifying the name of a valid exception handler for the error-handler-name attribute. This attribute is required.	<ActionInvokeErrorHandler error-handler-name= "EH Wrong data to Pobean"> <notes> This is a note. </notes> </ActionInvokeErrorHandler>
ActionNoOp	Action used as a placeholder for a future action. This action performs no function. In the Studio, you define this action by selecting No Operation within the Miscellaneous actions category of the Add Actions dialog box. You must define the following subelements: notes description	<ActionNoOp> <notes> This is a note. </notes> <description> Replace with task assignment. </description> </ActionNoOp>
ActionPlugin	Generic container for all plug-in actions. You must define the following subelements: id plugin-data notes actions (zero or more) You must specify a text string providing a description of the plug-in the name for the label attribute. This attribute is required. Note: If a plug-in is available, the Studio displays the description of it in the actions lists. For more information about programming plug-ins, see Programming BPM Plug-Ins for WebLogic Integration.	<ActionPlugin label='Send Confirm Order Event'> <id>1000936287350 </id> <plugin-data name="com.bea.wlpi.SamplePlugin" ID="2"> <statusvariable> OrderStatus </statusvariable> <totalpricevariable> OrderTotalPrice </totalpricevariable> </plugin-data> <notes></notes> </ActionPlugin>
ActionPostXMLEvent	Action used to post an XML event. In the Studio, you define this action by selecting Post XML Event within the Integration actions category of the Add Actions dialog box. You must define the following subelements: notes topic \| queue transaction addressees (zero or one) message-properties (zero or one) delivery-mode priority time-to-live orderkey (zero or one) variable \| xml iviewx (zero or one) iviewy (zero or one)	<ActionPostXMLEvent> <notes> This is a note. </notes> <transaction> false </transaction> <delivery-mode> PERSISTENT </delivery-mode> <priority>4 </priority> <expression>false </expression> <time-to-live>0 </time-to-live> <xml> <order> "new" </order> </xml> <iviewx>240</iviewx> <iviewy>20</iviewy> </ActionPostXMLEvent>
actions	Action definition. For a Task node, you must define the following subelements: created activated executed markeddone For a Decision node or an ActionCondition action, you must define the following subelements: false true For a Done, Event, or Start node; or a ActionTaskDueDate, ActionTimedEvent, or ActionWorkflowStart event, you can define zero or more occurrences of the following subelement: %action-types	<actions> <created> </created> <activated> <ActionTaskAssignUser> <notes> This is a note. </notes> <target> 2 </target> <user>joe</user> <expression> false </expression> <role> false </role> </ActionTaskAssignUser> </activated> <executed> </executed> <markeddone> </markeddone> </actions>
ActionSendEMail	Action used to send an e-mail message to a WebLogic Process Integrator user or other individual. The internet standard SMTP protocol is used to transmit the message. In the Studio, you define this action by selecting Send E-mail Message within the Miscellaneous actions category of the Add Actions dialog box. You must define the following subelements: notes subject message to cc bcc	<ActionSendEMail> <notes> This is a note. </notes> <subject> "Order " </subject> <message> "This is the message. " </message> <to> <addressee> <name> joe@work </name> <expression> false </expression> <type> address </type> </addressee> </to> <cc> </cc> <bcc> </bcc> </ActionSendEMail>
ActionSendXMLToClient	Action used to send an XML document to the client, This action allows communication between the WebLogic Process Integrator and a client program via an XML message. In the Studio, you define this action by selecting Send XML to Client within the Integration actions category of the Add Actions dialog box. The XML document must be compliant with one of the following DTD formats, based on the request that is being sent: Client Call Addin Request DTD Client Call Program Request DTD Client Message Box Request DTD Client Set Variables Request DTD Custom clients can define their own services and XML formats. You must define the following subelements: id notes xml variables iviewx (zero or one) iviewy (zero or one)	<ActionSendXMLToClient> <id>959395846210</id> <notes>This is a note. </notes> <xml> <message-box title= ""Order Confirmation"" style=""question "" options= ""yes_no""> "Do you Confirm this order?" <actionid> "959395846210 " </actionid> </message-box> </xml> <variables> <variable> <name> Confirm</name> <expression> XPath(" /message-box/ attribute:: option") </expression> </variable> </variables> <actions> <ActionTaskDone> <notes> This is a note. </notes> <target>2</target> </ActionTaskDone> </actions> </ActionSendXMLToClient>
ActionSetErrorHandler	Action used to set a specified exception handler as active for a specific workflow template definition. This exception handler persists for the workflow instance until a subsequent ActionSetErrorHandler action is executed within the same workflow. By default, the system exception handler is used. In the Studio, you define this action by selecting Set Workflow Exception Handler within the Exception Handling Actions category of the Add Actions dialog box. You must define the following subelements: notes. You must specify a text string specifying the name of a valid exception handler (as a text string) for the error-handler-name attribute. This attribute is required.	<ActionSetErrorHandler error-handler-name= "EH Wrong data to Pobean"> <notes> This is a note. </notes> </ActionSetErrorHandler>
ActionTaskAssignRole	Action used to assign a task to a role. In the Studio, you define this action by selecting Assign Task to Role within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target role expression	<ActionTaskAssignRole> <notes> This is a note. </notes> <target> 963511923442 </target> <role> Role1 </role> <expression> false </expression> </ActionTaskAssignRole>
ActionTaskAssignRoutingTable	Action used to assign a task to a user or role, depending on a set of conditions. A condition specifies the circumstances under which a task should be assigned to a specific assignee (user or role). At runtime, the system selects the assignee associated with the condition that evaluates to true. In the Studio, you define this action by selecting Assign Task to Role within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target routeconditions	<ActionTaskAssignRoutingTable> <notes> This is a note. </notes> <target>2</target> <routeconditions> <routecondition> <to>Role1</to> <type> userinrole </type> <condition> a+b </condition> </routecondition> </routeconditions> </ActionTaskAssignRoutingTable>
ActionTaskAssignUser	Action used to assign a task to either a user or user in a role. When assigning a task to a user in a role, the process engine performs load balancing by reviewing the number of tasks assigned to all users in a role (that do not currently have reroutes in effect), indentifying the user with the smallest number of assigned tasks, and assigning the task to this user. In the Studio, you define this action by selecting Assign Task to User within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target user expression role	<ActionTaskAssignUser> <notes> This is a note. </notes> <target> 963511775400 </target> <user>joe</user> <expression> false </expression> <role> false </role> </ActionTaskAssignUser>
ActionTaskDoit	Action used to execute a task. In the Studio, you define this action by selecting Execute Task within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target	<ActionTaskDoIt> <notes> This is a note. </notes> <target> 963511923442 </target> </ActionTaskDoIt>
ActionTaskDone	Action used to mark task complete. This action sets the task completed value to the current date and time, and results in the sequential execution of all of the actions associated with the specified task's Marked Done event. In the Studio, you define this action by selecting Mark Task As Done within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target	<ActionTaskDone> <notes> This is a note. </notes> <target> 963511923442 </target> </ActionTaskDone>
ActionTaskDueDate	Action used to specify a task due date as an interval (expressed in minutes, hours, days, weeks, or months) from the point at which the action is executed. This action results in the execution of all actions associated with the Marked Done event. You can also define a set of actions to be performed if a task becomes overdue. In the Studio, you define this action by selecting Set Task Due Date within the Task Actions category of the Add Actions dialog box. You must define the following subelements: id notes target expression calendartype calendarname actions	<ActionTaskDueDate> <id>987445484073</id> <notes> This is a note. </notes> <target>2</target> <expression> DateAdd(Date(), "m",1) </expression> <calendartype> 0 </calendartype> <calendarname> </calendarname> <actions> <ActionNoOp> <notes> This is a note. </notes> <description> Replace with task assignment. </description> </ActionNoOp> </actions> </ActionTaskDueDate>
ActionTaskSetComment	Action used to specify a comment to be displayed to the user at runtime when the action is executed. Comments typically contain explanatory text. In the Worklist, the comment is displayed as a free-form text message in the comment column. In the Studio, you define this action by selecting Set Task Comment within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target comment	<ActionTaskSetComment> <notes> This is a note. </notes> <target> 963511923442 </target> <comment> This is a comment. </comment> </ActionTaskSetComment>
ActionTaskSetPriority	Action used to set a task priority. In the Worklist, the comment is displayed as a free-form text message in the comment column. In the Studio, you define this action by selecting Set Task Priority within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target priority	<ActionTaskSetPriority> <notes> This is a note. </notes> <target> 963511923442 </target> <priority> 1 </priority> </ActionTaskSetPriority> [Sets priority to medium (1).]
ActionTaskUnassign	Action used to unassign a task. In the Studio, you define this action by selecting Set Task Priority within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target	<ActionTaskUnassign> <notes> This is a note. </notes> <target> 963511923442 </target> </ActionTaskUnassign>
ActionTaskUndo	Action used to mark task incomplete. The action does not result in the execution of the actions associated with the specified task's Activated event. In the Studio, you define this action by selecting Mark Task As Undone within the Task Actions category of the Add Actions dialog box. You must define the following subelements: notes target	<ActionTaskUndo> <notes> This is a note. </notes> <target> 963511923442 </target> </ActionTaskUndo>
ActionTimedEvent	Action used to create a timed event that is triggered at an exact time and date, and will execute any specified actions. In the Studio, you define this action by selecting Timed Event within the Miscellaneous Actions category of the Add Actions dialog box. You must define the following subelements: id notes expression calendartype executionunits scheduleunits executiontime scheduletime recoverable (zero or one) stopwhentaskdone usetimeexpression actions	<ActionTimedEvent> <id>987100768489</id> <notes> This is a note. </notes> <expression> DateAdd(Date(), "m", 1) </expression> <calendartype>0 </calendartype> <executionunits>3 </executionunits> <scheduleunits>0 </scheduleunits> <executiontime>5 </executiontime> <scheduletime> </scheduletime> <recoverable> true </recoverable> <stopwhentaskdone> true </stopwhentaskdone> <usetimeexpression> true </usetimeexpression> <actions> <ActionTaskAssignUser> <notes> This is a note. </notes> <target>2 </target> <user>joe</user> <expression> false </expression> <role>false </role> </ActionTaskAssignUser </actions> </ActionTimedEvent>
active	Flag (true or false) specifying whether or not the workflow template definition is active.	<active> true </active>
activated	Actions associated with the task's Activated event. You can define zero or more occurrences of the following subelement: %action-types.	<activated> <ActionTaskAssignUser> <notes> This is a note. </notes> <target> 2 </target> <user>joe</user> <expression> false </expression> <role> false </role> </ActionTaskAssignUser> </activated>
ActionWorkflowAbort	Action used to abort a workflow. This action permanently stops a workflow and deletes it from the server. In the Studio, you define this action by selecting Abort Workflow within the Workflow Actions category of the Add Actions dialog box. You must define the following subelement: notes.	<ActionWorkflowAbort> <notes> This is a note. </notes> </ActionWorkflowAbort>
ActionWorkflowDone	Action used to mark a workflow as complete. In the Studio, you define this action by selecting Mark Workflow as Done within the Workflow Actions category of the Add Actions dialog box. You must define the following subelement: notes.	<ActionWorkflowDone> <notes> This is a note. </notes> </ActionWorkflowDone>
ActionWorkflowSetComment	Action used to specify a comment to be displayed to the user at runtime when the action is executed. Comments typically contain explanatory text. In the Studio, you define this action by selecting Mark Workflow as Done within the Workflow Actions category of the Add Actions dialog box. You must define the following subelements: notes comment	<ActionWorkflowSetComment> <notes> This is a note. </notes> <comment> "Order Cancelled" </comment> </ActionWorkflowSetComment>
ActionWorkflowStart	Action used to start a workflow, supporting subworkflows. In the Studio, you define this action by selecting Start Workflow within the Workflow Actions category of the Add Actions dialog box. You must define the following subelements: id notes templateid template-name refvariable orgexpression parameters results actions iviewx (zero or one) iviewy (zero or one)	<ActionWorkflowStart> <id> 987445540073 </id> <notes> This is a note. </notes> <templateid> 3 </templateid> <template-name> ShipBill </template-name> <refvariable> Name </refvariable> <parameters> </parameters> <results> </results> <actions> </actions> </ActionWorkflowStart>
ActionXSLTransform	Action used to perform an XML transformation. You must define the following subelements: notes input-expression transform-document transform-source output-variable xsl-parameters (one or more)
addressee	Address of a receipient. You must define the following subelements: name expression type	<addressee> <name> joe@work </name> <expression> false </expression> <type> address </type> </addressee>
addressees	One or more addressees. You must define the following subelement: instanceid
and	Flag specifying whether or not the Join node is an AND (true) or OR (false) node.	<and>true</and>
arguments	Valid workflow expression to be evaluated at runtime and passed to the called program defined by the program element.	<arguments> CurrentUser() </arguments>
audit-enabled	Flag (true or false) specifying whether or not auditing is enabled on the workflow template definition.	<audit-enabled> false </audit-enabled>
audittext	Audit entry expression to be sent to the audit listener for further retrieval at runtime. The audit entry can be an expression built with functions and workflow variables, or a string of text.	<audittext> "Workflow cancelled." </audittext>
bcc	E-mail addresses of the individuals to be blind-copied on the e-mail message, as defined by the ActionSendEMail action. You can define zero or more occurrences of the following subelement: addressee.	<bcc> <addressee> <name> joe@work </name> <expression> false </expression> <type> address </type> </addressee> </bcc>
calendartype	Business calendar type.	<calendartype> Type1 </calendartype>
calendarname	Business calendar name.	<calendarname> MyCalendar </calendarname>
called	Flag (true or false) specifying whether or not the Start node is callable from another workflow.	<called> true </called>
cc	E-mail address(es) of the individuals to be copied on an e-mail message, as defined by the ActionSendEMail action. You can define zero or more occurrences of the following subelement: addressee.	<cc> <addressee> <name> joe@work </name> <expression> false </expression> <type> address </type> </addressee> </cc>
changedby	Valid user that last modified the workflow template definition.	<changedby> joe </changedby>
changeddate	Date at which the workflow template was changed, specified using the following format: yyyyMMddHHmm, where yyyy specifies the year, MM specifies the month, dd specifies the day, HH specifies the hour (00 through 23), and mm specifies the minutes.	<changeddate> 200103220930 </changeddate> [March 22, 2001 9:30AM]
comment	A valid workflow expression or text string that defines a comment and is evaluted at runtime. Comments typically contain explanatory text.	<comment> "Order Cancelled" </comment>
commit-actions	Actions performed when a transaction is committed. You can define zero or more occurrences of the following subelement: %commit-action-types.	<commit-actions> <ActionTaskDone> <notes> This is a note. </notes> <target> 963511775400 </target> </ActionTaskDone> </commit-actions>
condition	Valid workflow condition that is evaluated at runtime and determines which set of subactions to perform.	<condition> status=" complete" </condition>
correlationid	Correlation ID.
created	Actions associated with the task's Created event. You can define zero or more occurrences of the following subelement: %action-types.	<created> <ActionTaskAssignUser> <notes> This is a note. </notes> <target> 2 </target> <user>joe</user> <expression> false </expression> <role> false </role> </ActionTaskAssignUser> </created>
dateexpression	Date to start a time-triggered workflow. This value can be either a workflow expression or a text string, and should result in the following format: yyyyMMddHHmm, where yyyy specifies the year, MM specifies the month, dd specifies the day, HH specifies the hour (00 through 23), and mm specifies the minutes.	<dateexpression> 200007120000 </dateexpression> [July 12, 2000 12:00 am]
Decision	Decision node. You must define the following subelements: %node condition truenexts falsenexts actions	See Template Definition DTD Example.
delivery-mode	Mode used to deliver a posted XML event.	<delivery-mode> PERSISTENT </delivery-mode>
description	Text description of the element.	<description> Start </description>
descriptorid	Descriptor ID of the business operation that is being defined for the ActionBusinessOperation action.	<descriptorid> 31 </descriptorid>
doitifdone	Permission flag (true or false) specifying whether or not the task can be executed once it has been marked done, using the methods described in Executing a Task.	<doitifdone> true </doitifdone>
Done	Done node. For manually started workflows, you must define the following subelements: %node description actions plugin-data (zero or one)	See Template Definition DTD Example.
donewithoutdoit	Permission flag (true or false) specifying whether or not the task can be marked done without having been executed, using the methods described in Marking a Task as Complete or Incomplete.	<donewithoutdoit> true </donewithoutdoit>
effective	Effective date in the following format: yyyyMMddHHmm, where yyyy specifies the year, MM specifies the month, dd specifies the day, HH specifies the hour (00 through 23), and mm specifies the minutes.	<effective> 200007120000 </effective> [July 12, 2000 12:00 am]
error-handler	Error handler. You must define the following subelements: notes variables commit-actions rollback-actions You define the following attributes: name: Error-handler name. initial: Flag (true or false) specifying whether or not this is the default error handler to use. This attribute can be set to true for only one error handler. This attribute defaults to false.	<error-handler name="EH Wrong data to Pobean" initial="false"> <notes> This is a note. </notes> <variables> </variables> <commit-actions> <ActionExitErrorHandler exit-type="continue"> <notes> This is a note. </notes> </ActionExitErrorHandler> </commit-actions> <rollback-actions> <ActionPostXMLEvent> <notes>Notes. </notes> <xml> <order> "new" </order> </xml> </ActionPostXMLEvent> <ActionExitErrorHandler exit-type="rollback"> <notes>Notes. </notes> </ActionExitErrorHandler> </rollback-actions> </error-handler>
error-handlers	Error handlers defined for the workflow template definition. You must define the following subelement: error-handler.	<error-handlers> <error-handler> ... </error-handler> </error-handlers>
Event	Event node. For a standard Event node, you must define the following subelements: %node root description key condition actions variables iviewx (zero or one) iviewy (zero or one) For a plugin Event node, you must define the following subelements: %node plugin-data actions variables iviewx (zero or one) iviewy (zero or one)	See Template Definition DTD Example.
event	Flag (true or false) specifying whether or not the Start node is event-triggered.	<event> true </event>
executed	Actions associated with the task's Executed event. You can define zero or more occurrences of the following subelement: %action-types.	<executed> <ActionTaskDone> <notes> This is a note. </notes> <target> 963511923442 </target> </ActionTaskDone> </executed>
executiontime	Numeric value specifying the number of executionunits units from the current time, that define the amount of time that must elapse before a time-triggered event (defined by the ActionTimedEvent action) is executed.	<executiontime> 5 </executiontime>
executionunits	Units used to express the execution time. Possible values include: 0: Milliseconds 1: Seconds 2: Minutes 3: Hours 4: Days 5: Weeks 6: Months 7: Business hours 8: Business days	<executionunits> 3 </executionunits>
expression	For ActionExpression, ActionTaskDueDate, ActionTimedEvent, or variable, specifies a workflow expression that is meaningful within the context of the parent element. For ActionTaskAssignRole, ActionTaskAssignUser, or addressee, specifies a flag (true or false) that defines whether or not an associated value is represented as a workflow expression.	<expression> XPath(" /order/text()") </expression>
false	Actions associated with a Decision node's false branch. You can define zero or more occurrences of the following subelement: %action-types.	<false> <ActionWorkflowAbort> <notes> This is a note. </notes> </ActionWorkflowAbort></false>
falsenexts	String specifying the next node associated with a Decision node's false branch. You can define zero or more occurrences of the following subelement: next.	<falsenexts> 963410128518 </falsenexts>
id	Unique ID that is meaningful within the context of the parent element.	<id>3</id>
idexpression	Expression used for identifying the workflow template definition.	<idexpression> "Order" +"" +:OrderNumber </idexpression>
in	Flag (true or false) specifying whether or not a variable, defined by a callable Start node, is an input parameter.	<in>true</in>
inmandatory	Flag (true or false) specifying whether or not an input variable, defined by a callable Start node, is a mandatory input parameter.	<inmandatory> true </inmandatory>
input-expression	Workflow expression that identifies the XML document for which an XSL transformation will take place.
instanceid	Workflow instance ID that defines the target of the XML event defined by the ActionPostXMLEvent action.	<instanceid> 10 </instanceid>
instance-variable	Instance variable (name of the variable containing the Java object or EJB) on which WebLogic Process Integrator should invoke the business operation defined by the ActionBusinessOperation action.	<instance-variable> PobeanHandle </instance-variable>
instance-variable-type	Instance variable type of the instance variable defined by the instance-variable element.	<instance-variable-type> session </instance-variable-type>
iviewx	X-coordinate of a Studio interface view shape.	<iviewx>150</iviewx>
iviewy	Y-coordinate of a Studio interface view shape.	<iviewx>150</iviewx>
jmstype	JMS destination type.
Join	Join node. You must define the following subelements: %node and	See Template Definition DTD Example.
key	Workflow expression that evaluates to a key at runtime. The system evaluates the workflow expression against the root element of an incoming XML document (of the specified type) to yield a key value that uniquely identifies that document instance.	<key> $orderid </key>
manual	Flag (true or false) specifying whether or not the Start node is manually startable.	<manual> true </manual>
markeddone	Actions associated with the task's Marked Done event. You can define zero or more occurrences of the following subelement: %action-types.	<markeddone> <ActionWorkflowSetComment> <notes> This is a note. </notes> <comment> "Order Cancelled" </comment> </ActionWorkflowSetComment>
message	E-mail message text to be sent as defined by the ActionSendEMail action. This value can be a valid workflow expression or literal string (in double quotes) that is evaluated at runtime.	<message> The order has been processed. </message>
message-properties	Message properties. You can define one or more occurrences of the following subelement: property.
modifiable	Permission flag (true or false) specifying whether or not the task properties can be modified at run time, using the methods described in Setting Task Properties.	<modifiable> true </modifiable>
name	Unique string specifying the element name that is meaningful within the context of the parent element.	<name> Order Processing </name>
next	String specifying the next node to activate.	<next> 963410128518 </next>
nexts	A list containing zero or more next actions. You can define zero or more occurrences of the following subelement: next.	<nexts> <next> 963410128518 </next> </nexts>
nodes	Nodes defined for the workflow template definition. You can define zero or more occurrences of the following subelements: Decision Done Event Join Start Task	See Template Definition DTD Example.
notes	User-defined notes.	<notes> This workflow is used for order processing. </notes>
orderkey	Order key, used for ordered messaging, as described in Establishing JMS Connections.
orgexpression	Workflow expression that specifies the organization associated with the workflow that you are attempting to start, using the ActionWorkflowStart action.
out	Flag (true or false) specifying whether or not a variable, defined by a callable Start node, is an output parameter.	<out>false</out>
output-variable	Variable to which the result of the XSL transformation is stored.
parameters	Initial parameter values to be set using an explicitly defined variable in the calling workflow. You can define zero or more occurrences of the following subelement: parm.	<parameters> <parm> <name> CustomerId </name> <value> $CustomerId </value> </parm> </parameters>
parm	Parameter definition. For an ActionBusinessOperation action, this element can be any character string. For ActionWorkflowStart action, you can define zero or more of the following subelement pairs: name value	<parm> :ItemNumber </parm>
parms	Parameter list, if required. You must specify zero or more occurrences of the following subelement: parm.	<parms> <parm> :ItemNumber </parm> <parm> :ItemQuantity </parm> <parm> :CustomerState </parm> </parms>
plugin	Plug-in entry. One element appears for each plug-in referenced by a template definition, and each plug-in that defines its own template definition property. Optionally, you can define the following subelement: plugin-data. You define the following attributes: name: Plug-in name. referenced: Flag (true or false) specifying whether or not the template definition uses the plug-in. major-version: Major version of plug-in software. minor-version: Minor version of plug-in software. vendor: Vendor name. url: URL (defaults to an empty string). For more information about programming plug-ins, see Programming BPM Plug-Ins for WebLogic Integration.	<plugin name="com.bea.wlpi.SamplePlugin" referenced="true" major-version="1" minor-version="0"> </plugin>
plugin-data	Plug-in data consisting of any combination of elements and text. You must define the following attributes: name: Name of the plug-in. This attribute is required. ID: Plug-in provided unique ID for the associated value object. This attribute is required. For more information about programming plug-ins, see Programming BPM Plug-Ins for WebLogic Integration.	<plugin-data name="com.bea.wlpi.SamplePlugin" ID="2"> <statusvariable> OrderStatus </statusvariable> <totalpricevariable> OrderTotalPrice </totalpricevariable> </plugin-data>
plugins	Plug-in definition, if plug-in is provided. You can define zero or more occurrences of the following subelements: plugin. For more information about programming plug-ins, see Programming BPM Plug-Ins for WebLogic Integration.	<plugins> <plugin name="com.bea.wlpi.SamplePlugin" referenced="true" major-version="1" minor-version="0"> </plugin> </plugins>
priority	Task priority. Possible values include: 0 (low), 1 (medium), and 2 (high).	<priority> 1 </priority>
program	Fully-qualified path to an executable program.	<program> MyProgram </program>
property	Message property. You must define the following subelements: name value
queue	JMS queue to which an XML document is sent or retrieved. You must define the expression attribute to specify whether or not the value specified is an expression. This attribute defaults to false.	<queue> Queue1 </queue>
reassignment	Permission flag (true or false) specifying whether or not a task can be reassigned to another participant, using the methods described in Assigning a Task.	<reassignment> true </reassignment>
recoverable	Flag specifying whether or not you would like to recover all of the actions lost in the event of system failure.
refvariable	Variable to which the workflow ID is saved when the workflow is started by a ActionWorkflowStart action. This variable can be used in expressions from within the calling workflow to retrieve variables. For example, NewWF.Name retrieves the value of the Name variable.	<refvariable> Name </refvariable>
replyto	Reply-to address
reschedamount	Numeric value. This value specifies the number of reschedunits units from the dateexpression at which a time-triggered Start node is rescheduled.	<reschedamount> 30 </reschedamount>
reschedunits	Units used to express the reschedule time for a time-triggered workflow. Possible values include: 0: Milliseconds 1: Seconds 2: Minutes 3: Hours 4: Days 5: Weeks 6: Months 7: Business hours 8: Business days	<reschedunits> 0 </reschedunits>
result	Result. For an ActionBusinessOperation action, this element can be any character string. For an ActionWorkflowStart action, you must define the following subelements: name value	<result> PobeanHandle </result>
result-type	Type of result-type variable.	<result-type> Session </result-type>
results	Results. You can define zero or more occurrences of the following subelement: result.	<results> <result> PobeanHandle </result> </results>
role	For ActionTaskAssignRole, specifies an existing role or a workflow expression that evaluates to an existing role. If a workflow expression, the expression flag must be set to true. For ActionTaskAssignUser, specifies a flag (true or false) that indicates whether the user element specifies a user (false) or role (true).	<role> "Role1" </role>
rollback-actions	Actions performed when a transaction is rolled back. You can define zero or more occurrences of the following subelement: %rollback-action-types	<rollback-actions> <ActionTaskDone> <notes> This is a note. </notes> <target> 963511775400 </target> </ActionTaskDone> </rollback-actions>
root	Root element of an XML document that triggers the associated event.	<root>order</root>
routecondition	Route condition. You must define the following subelements: to type condition	<routecondition> <to>Role1</to> <type> userinrole </type> <condition> a+b </condition> </routecondition>
routeconditions	Route conditions. You can define zero or more occurrences of the following subelement: routecondition.	<routeconditions> <routecondition> <to>Role1</to> <type> userinrole </type> <condition> a+b </condition> </routecondition> </routeconditions>
scheduletime	Numeric value. This value specifies the number of scheduleunits units from the current time, that define the amount of time that must elapse before a time-triggered event (defined by the ActionTimedEvent action) is rescheduled.	<scheduletime> 5 </scheduletime>
scheduleunits	Units used to express the reschedule time. Possible values include: 0: Milliseconds 1: Seconds 2: Minutes 3: Hours 4: Days 5: Weeks 6: Months 7: Business hours 8: Business days	<scheduleunits> 0 </scheduleunits>
subject	Subject line for the e-mail message to be sent, as defined by the ActionSendEMail action. This value can be a valid workflow expression or literal string (in double quotes) that is evaluated at runtime.	<subject> Urgent </subject>
Start	Start node. For manually startable workflows, you must define the following subelements: %node description manual nexts actions variables iviewx (zero or one) iviewy (zero or one) For callable workflows, you must define the following subelements: %node description called nexts actions variables iviewx (zero or one) iviewy (zero or one)	See Template Definition DTD Example.
Start (cont)	For time-triggered workflows, you must define the following subelements: %node description timed dateexpression reschedamount reschedunits recoverable (zero or one) calendarname startorg nexts actions variables iviewx (zero or one) iviewy (zero or one) For event-triggered workflows, you must define the following subelements: %node description event root key condition startorg nexts actions variables
Start (cont)	For plug-in-triggered workflows, you must define the following subelements: %node description plugin-data startorg nexts actions variables
startorg	Organization associated with the Start node.	<startorg> "ORG1" </startorg>
stopwhentaskdone	Flag specifying whether to stop execution (and rescheduling) when the task (true) or workflow (false) completes.	<stopwhentaskdone> true </stopwhentaskdone>
target	Unique numerical value that identifies the element upon which you are operating, and that is meaningful within the context of the parent element.	<target> 963511923442 </target>
Task	Task node. You must define the following subelements: %node name priority donewithoutdoit doitifdone unmarkdone modifiable reassignment nexts actions	See Template Definition DTD Example.
template-entry	Target of an addressed JMS message.
template-name	Workflow template name.	<template-name> ShipBill </template-name>
templateid	Template ID of the workflow to start, using the ActionWorkflowStart action.	<templateId> 3 </templateId>
time-to-live	Time-to-live value.	<time-to-live> 0 </time-to-live>
timed	Flag (true or false) specifying whether or not the Start node is time-triggered.	<timed> true </timed>
to	E-mail address(es) of the primary receipient(s) to be sent an e-mail message, as defined by the ActionSendEMail action. You can define zero or more occurrences of the following subelement: addressee	<to> <addressee> <name> joe@work </name> . <expression> false </expression> <type> address </type> </addressee> </to>
topic	JMS topic to which an XML document is sent or retrieved. You must define the expression attribute to specify whether or not the value specified is an expression. This attribute defaults to false.	<topic> Topic1 </topic
transaction	Boolean flag specifying whether or not the workflow can be part of a transaction.	<transaction> false </transaction>
transform-document	XSLT document used to transform input-expression
transform-source	Flag that indicates whether transform-document is obtained from a workflow expression (E) or from the path to a XML repository file (R).	<transform-source> E </transform-source
true	Actions associated with a Decision node's true branch. You can define zero or more occurrences of the following subelement: %action-types.	<true> <ActionWorkflowAbort> <notes> This is a note. </notes> </ActionWorkflowAbort></true>
truenexts	String specifying the next node associated with a Decision node's true branch. You can define zero or more occurrences of the following subelement: next.	<truenexts> 963410128518 </truenexts>
type	For a variable, specifies one of the following variable types: boolean, date, double, entity (Entity EJB), integer, object, session (Session EJB), string, or xml. For a routecondition, specifies the type of the addressee (user, userinrole, or role) specified for the to element. For an addressee, specifies the type of the addressee (address, user, or role) specified for the name element.	<type>string</type>
unmarkdone	Permission flag (true or false) specifying whether or not the task can be executed once it has been marked done, using the methods described in Marking a Task as Complete or Incomplete.	<unmarkdone> true </unmarkdone>
user	User or user in role. This value can specify an existing user or role, or a workflow expression that evaluates to the user or role to which the task is assigned by the ActionTaskAssignUser action. If it is a workflow expression, the associated expression flag must be set to true.	<user>true</user>
usetimeexpression	Flag specifying whether to use the specified expression (true) or executiontime (false) to trigger an ActionTimedEvent action,	<usetimeexpression> true </usetimeexpression>
value	Parameter value that is meaningful within the context of the parent element.	<value> 5 </value>
variable	Variable defined for the workflow template definition. For a Workflow, you must define the following subelements: name notes type or plugin-data xmltype inmandatory in out For a Start node or ActionSendXMLToClient action, you must define the following subelements: name expression For an ActionExpression action, you must define the following subelements: name expression	<variable> <name> TotalPrice </name> <notes> This is a note. </notes> <type> double </type> <xmltype> </xmltype> <inmandatory> false </inmandatory> <in>false</in> <out>false</out> </variable>
variables	Variables defined for the workflow template definition. You can define zero or more occurrences of the following subelement: variable.	<variables> <variable> <name> TotalPrice </name> <notes> This is a note. </notes> <type> double </type> <xmltype> </xmltype> <inmandatory> false </inmandatory> <in>false</in> <out>false</out> </variable> <variables>
Workflow	Root element. You must define the following subelements: name effective changedby changeddate notes idexpression active audit-enabled plugins (zero or one) nodes variables error-handlers (zero or one) You must define the following attributes: major-version: Major version of software. Defaults to 1. minor-version: Minor version of software. Defaults to 0. build-number: Build number of software. Defaults to 0.	See Template Definition DTD Example.
x	X-coordinate of a Studio shape.	<x>20</x>
xml	XML document structure consisting of any combination of elements and text.	<xml> <order> "new" </order> </xml>
xmltype	XML document type, if variable type is set to xml.
xsl-parameters	Parameters used for XML transformation. You must define one or more xsl-parameter subelements.
xsl-parameter	Parameter used for XML transformation. You must define the following subelements: name expression
y	Y-coordinate of a Studio shape.	<y>40</y>

Entity	Description
%action-types	Defines all action types, including the %std-action-typesand the following types: ActionInvokeErrorHandler ActionSetErrorHandler
%commit-action-types	Commit transaction action types, including the %std-action-typesand the following types: ActionExitErrorHandler ActionSetErrorHandler
%node	Node characteristics, including the following: id x y notes
%rollback-action-types	Rollback transaction action types, including the following: ActionAuditEntry ActionBusinessOperation ActionCallProgram ActionCondition ActionExitErrorHandler ActionExpression ActionNoOp ActionPlugin ActionPostXMLEvent ActionSendEMail ActionSendXMLToClient
%std-action-types	Standard action types, including the following: ActionAuditEntry ActionBusinessOperation ActionCallProgram ActionCancelEvent ActionCondition ActionExpression ActionNoOp ActionPlugin ActionPostXMLEvent ActionSendEMail ActionSendXMLToClient ActionTaskAssignRole ActionTaskAssignRoutingTable ActionTaskAssignUser ActionTaskDoit ActionTaskDone ActionTaskDueDate ActionTaskSetComment ActionTaskSetPriority ActionTaskUnassign ActionTaskUndo ActionTimedEvent ActionWorkflowAbort ActionWorkflowDone ActionWorkflowSetComment ActionWorkflowStart ActionXSLTransform

Element	Description
done	Number of tasks marked as complete for item.
inactive	Number of inactive tasks for item.
item	Item for which you are gathering the workload report. You must define the following subelements: name pending inactive done overdue total
name	Name of the item for which you are gathering the workload report.
overdue	Number of overdue tasks for item.
pending	Number of pending tasks for item.
total	Total number of tasks for item.
workload	Root element. You must define zero or more occurrences of the following subelement: item