tasklet Element
Defines a tasklet for use in an orchestration. When a tasklet is called, the tasklet definition is used to create and configure an instance of the tasklet assembly.
For more information, see Defining Tasklets in Microsoft Dynamics Mobile Orchestration Guide online.
<tasklet context="text description" name="reference name" icon="icon file name" text="title text" type="namespace.class, assemblyname" />
The following sections describe attributes, child elements, and parent elements.
Attributes
| Attribute | Description | |
|---|---|---|
|
|
Optional attribute. Information about the value of the | |
|
|
Required attribute. Specifies a name for the tasklet. Referencing the name, the tasklet can be called from other parts of the UserRole.xml file, including orchestrations and tasklets. If the tasklet element is defined in an
| |
|
|
Configures the icon that displays in the header section. The icon file must be placed in the application root folder. You can include the icon file in a subfolder of the root folder. If so, include the folder path in the value, for example, Graphics\myicon.png. Note If nothing is specified, a system icon displays. | |
|
|
Optional attribute. A text string that is displayed in the title bar of the tasklet page. | |
|
|
Optional attribute. Specifies the fully qualified type name of the tasklet. The type includes the namespace, class, and assembly name, and has the following format:
|
Child Elements
| Element | Description |
|---|---|
|
Contains one or more actions that can be initiated from a tasklet. | |
|
Contains elements for customizing tasklets, including application settings and text labels. | |
|
Specifies a tasklet output that must be set before an action is enabled in the tasklet user interface. | |
|
Maps output parameter values from other tasklets to the input parameters of the tasklet. | |
|
Maps output parameters of the tasklet to a memory state from which they can be mapped as input to other tasklets. |
Parent Elements
| Element | Description |
|---|---|
|
Contains one or more tasklet declarations. |
This example demonstrates how to use the <userRole> element in a three-tasklet orchestration for showing customer details:
-
CustomerDetailTaskletdisplays information about a customer. -
CustomerContactDetailTaskletdisplays information about the customer's contact person. -
CustomerCreditLimitDetailTaskletdisplays 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>
Reference
orchestrations Elementtasklets Element
actions Element
constraints Element
configuration Element
inputMapping Element
outputMapping Element
Concepts
UserRole Schema Hierarchy StructureDefining Orchestrations in the UserRole
Defining Tasklets
Developing Mobile Application Solutions and Tasklets
Other Resources
Mobile UserRole Schema ReferenceMobile Orchestration
How to: Build a Mobile Application Using Orchestration
Working with Actions for Soft Keys and Menu Items
Developing Tasklets
Note