wizardStep Element
Specifies a tasklet that defines a step in a wizard. A wizard consists of one or more sequential steps. The user can navigate between these steps. The order of the <wizardStep> elements within the <wizardSteps> element determines the sequence of the wizard steps.
For more information on wizards, see Defining a Wizard in Microsoft Dynamics Mobile Orchestration Guide online.
<wizardStep tasklet="tasklet name" />
The following sections describe attributes, child elements, and parent elements.
Attributes
| Attribute | Description |
|---|---|
|
|
Required attribute. Specifies the tasklet for the wizard step. The value must match the value for the |
Child Elements
None.
Parent Elements
| Element | Description |
|---|---|
|
Specifies the tasklets to use in the wizard steps. |
The following example demonstrates how to define a three-tasklet wizard that creates a new customer.
<orchestration name="NewCustomerWizard" text="New Customer">
<confirmClose text="The customer data will be lost. Are you sure you want to close?" />
<requestDocument name="CreateCustomer" stamps="1" text="Create a customer">
<requiredRequests>
<request name="CustomerDetails"/>
<request name="CreditLimit"/>
<request name="ContactDetails"/>
</requiredRequests>
</requestDocument>
<wizardSteps>
<wizardStep tasklet="CustomerDetails" />
<wizardStep tasklet="CreditLimit" />
<wizardStep tasklet="ContactDetails" />
</wizardSteps>
<actions>
<exitOrchestration priority="-1" text="Cancel" submitRequestDocument="false" result="Cancel"/>
</actions>
<tasklets>
<tasklet name="CustomerDetails" text="Customer Details" type="CustomerDetailTasklet. CustomerDetailTasklet, CustomerDetailTasklet ">
<outputMappings>
<outputMapping propertyName="CustomerType" stateKey="CustomerType"/>
<outputMapping propertyName="CustomerName" stateKey="CustomerName"/>
</outputMappings>
<actions>
<next priority="2" text="Next" validate="true"/>
</actions>
</tasklet>
<tasklet name="CreditLimit" text="Credit Limit" type="CustomerCreditLimitDetailTasklet. CustomerCreditLimitDetailTasklet, CustomerCreditLimitDetailTasklet ">
<outputMappings>
<outputMapping propertyName="CreditLimit" stateKey="CreditLimit"/>
</outputMappings>
<inputMappings>
<inputMapping propertyName="CustomerType" stateKey="CustomerType"/>
<inputMapping propertyName="CustomerName" stateKey="CustomerName"/>
</inputMappings>
<actions>
<previous priority="1" text="Previous" />
<next priority="2" text="Next">
<constraints>
<required stateKey="CreditLimit"/>
</constraints>
</next>
</actions>
</tasklet>
<tasklet name="ContactDetails" text="Contact Details" type="CustomerContactDetailTasklet.CustomerContactDetailTasklet, CustomerContactDetailTasklet">
<inputMappings>
<inputMapping propertyName="CustomerName" stateKey="CustomerName"/>
</inputMappings>
<actions>
<previous priority="1" text="Previous"/>
<exitOrchestration priority="2" text="Finish" submitRequestDocument="true" result="OK"/>
</actions>
</tasklet>
</tasklets>
</orchestration>
Reference
wizardSteps Elementnext Element
previous Element
orchestration Element
tasklets Element
inputMapping Element
outputMappings Element
constraints Element
Concepts
UserRole Schema Hierarchy StructureDefining a Wizard
Defining Orchestrations in the UserRole
Defining Tasklets
Other Resources
Mobile OrchestrationHow to: Build a Mobile Application Using Orchestration
Working with Actions for Soft Keys and Menu Items