Issue 95 Proposal - SubTask data

["Phil Allen (SHAREPOINT DESIGNER)" <phillipa@exchange.microsoft.com>]

http://www.osoa.org/jira/browse/BP-95

 

Based off of CD-05, and the resolution to issue 94:

Section 3.7.5 Paragraph 1 becomes:

 

To support sub tasks the task instance data gets enhanced by the following (optional) parameters:         

·         sub tasks    ą A list of task identifiers for each already-created subtask of the task, including both non-terminated and terminated instances.

ą A list of the names of the sub tasks available for creation in the definition of the task, based on the compositiionType, instantiationPattern, and already created tasks.

·         parent task  ą The identifier of the superior composite task of this task if it is a sub task.

 

 

Add the following row to the operations table (section 7.1.1):

instantiateSubTask

Creates an instantiateable subtask for the task from the definition of the task. The fault hta:illegalArgumentFault MUST be returned if the task does not have an instantiateable subtask of the given name. Returns the identifier for the created subtask.

In task identifier subtask name Out task identifier

No

Reserved In Progress

(no state transition)

 

And to 7.1.5, Operation Authorizations:

 

Role   Operation		Task Initiator		Task Stakeholders	Potential Owners		Actual Owner			Business Administrator	Notification Recipients
instantiateSubTask	-		-			-		+	n/a		n/a

 

Thanks,

Phil