outputMappings Element
Dynamics Mobile 1.5
Transfers data between tasklets. Contains <outputMapping> elements that transfer the tasklet output parameter values to a memory state from where they can be mapped as input to other tasklets in the application.
<outputMappings>
<outputMapping>…</outputMapping>
<outputMapping>…</outputMapping>
</outputMappings>
The following sections describe attributes, child elements, and parent elements.
Attributes
None.
Child Elements
| Element | Description |
|---|---|
|
Optional element. Stores a tasklet output parameter to a memory state from where it can be mapped as input to other tasklets. |
Parent Elements
| Element | Description |
|---|---|
|
Defines an instance of a tasklet in the application. |
This example demonstrates how to use the <outputMappings> element to map data between tasklets in a 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>
Tasks
How to: Map a Tasklet Output ParameterHow to: Map a Tasklet Output to a Tasklet Input
Reference
outputMapping ElementinputMapping Element
tasklet Element
actions Element
Concepts
UserRole Schema Hierarchy StructureDefining Orchestrations in the UserRole
Defining Tasklets
Displaying Data on Tasklets
Other Resources
Mobile OrchestrationTransferring Data Between Tasklets
Working with Actions for Soft Keys and Menu Items
Community Additions
ADD
Show: