tasklets Element

Contains individual tasklet definitions. A tasklet definition is used to create an instance of a tasklet when it is called in an orchestration. You can define tasklets globally, which means the tasklet definition can be called from any orchestration. You can also define tasklets locally on an orchestration, which means the tasklet definition can only be called from that particular orchestration.

userRole Element

    orchestrations Element

        orchestration Element

            tasklets Element

    tasklets Element


<tasklets>
    <tasklet>…</tasklet>
    <tasklet>…</tasklet>
</tasklets>

The following sections describe attributes, child elements, and parent elements.

Attributes

None.

Child Elements

Element Description

tasklet Element

Defines a tasklet for use in the application.

Parent Elements

Element Description

orchestration Element

Defines an orchestration to control the interaction between one or more tasklets. When the <tasklets> element is defined under the <orchestration> element, the tasklet definitions pertain only to the orchestration; other orchestrations cannot call the tasklet definitions.

userRole Element

Root element for the schema. When the <tasklets> element is used under the <userRole> element, the tasklet definitions pertain to the entire application; all orchestrations can call the tasklet definitions.

The first tasklet defined in the <tasklets> element of an orchestration is the tasklet that opens when the orchestration opens. The first tasklet defined in the first <orchestration> element of the UserRole.xml file is the tasklet that opens when the application starts.

The following example demonstrates how to use the <tasklets> element in a three-tasklet orchestration for showing customer details:

  • CustomerDetailTasklet displays information about a customer.

  • CustomerContactDetailTasklet displays information about the customer's contact person.

  • CustomerCreditLimitDetailTasklet displays the customer's credit limit.

<orchestration text="Customer detail" name="CustomerDetailEdit">
  <tasklets>
    <tasklet name="CustomerDetailTasklet" text="Customer Details" type="CustomerDetailTasklet.CustomerDetailTasklet, CustomerDetailTasklet">
      <actions>
        <open text="Contact" priority="40" tasklet="CustomerContactDetailTasklet">
          <inputMappings>
            <inputMapping propertyName="CustomerId" stateKey="CustomerID"/>
          </inputMappings>
        </open>
        <open text="CreditLimit" priority="40" tasklet="CustomerCreditLimitDetailTasklet">
          <inputMappings>
            <inputMapping propertyName="CustomerId" stateKey="CustomerID"/>
          </inputMappings>
        </open>
      </actions>
    </tasklet>
    <tasklet name="CustomerContactDetailTasklet" text="Contact Details" type="CustomerContactDetailTasklet.CustomerContactDetailTasklet, CustomerContactDetailTasklet">
    </tasklet>
    <tasklet name="CustomerCreditLimitDetailTasklet" text="Credit Limit" type="CustomerCreditLimitDetailTasklet.CustomerCreditLimitDetailTasklet, CustomerCreditLimitDetailTasklet">
    </tasklet>
  </tasklets>
</orchestration>

Required

No

Max. occurrences

1 within the parent element

Namespace

schemas.microsoft.com/Dynamics/Mobile/2007/04/Flow

Schema Name

UserRole Schema

Validation File

Orchestration.xsd

Can be Empty

No

Community Additions

ADD
Show: