inputMappings Element

Contains <inputMapping> elements that transfer tasklet output parameter values from state memory to the input parameters of a tasklet. You set up an <inputMappings> element on an action of a tasklet or orchestration or directly on a tasklet that requires an input parameter.

For more information on tasklet output and input mapping, see Transferring Data Between Tasklets in Microsoft Dynamics Mobile Orchestration Guide online.

userRole Element

    orchestrations Element

         orchestration Element

             actions Element

                 open Element

                     inputMappings Element

                     exitOrchestration Element

                         inputMappings Element

             tasklets Element

                 tasklet Element

                     inputMappings Element

                     actions Element

                         exitOrchestration Element

                             inputMappings Element

                         exitTasklet Element

                             inputMappings Element

                         next Element

                             inputMappings Element

                         open Element

                             inputMappings Element

                         previous Element

                             inputMappings Element

    tasklets Element

         tasklet Element

             inputMappings Element


<inputMappings>
    <inputMapping>…</inputMapping>
    <inputMapping>…</inputMapping>
</inputMappings>

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

Attributes

None.

Child Elements

Element Description

inputMapping Element

Optional element.

Maps a tasklet output parameter to the input parameter of the target tasklet using the stateKey identifier assigned to the output parameter.

Parent Elements

Element Description

exitOrchestration Element

Closes an orchestration.

exitTasklet Element

Closes a tasklet.

next Element

An action that opens the tasklet used in the next step of a wizard as defined in the <wizardSteps> element. For more information, see the wizardSteps Element.

open Element

An action on a tasklet or orchestration that opens another tasklet or orchestration.

previous Element

An action that opens the tasklet used in the previous step of a wizard as defined in the <wizardSteps> element.

tasklet Element

Defines the instance of a tasklet in the application or orchestration.

If the <inputMappings> element is defined under an action, then the tasklet output parameter values map from state to the first tasklet that opens as a result of the action. So an <inputMappings> element on action under an orchestration maps the tasklet output parameter values to the first tasklet of the target orchestration.

If the <inputMappings> element is defined directly under the <tasklet> element for a given tasklet definition, then the output parameter values map to the tasklet whenever the tasklet opens.

NoteNote

Tasklet output parameters are mapped to state using the <outputMapping> element. State is a memory representation of a tasklet output parameter that allows it to be mapped as an input parameter to one or more tasklets. The <outputMapping> element assigns a value to the tasklet output parameter using the stateKey attribute. The <inputMapping> element uses this state key to identify the state and make the transfer to the tasklet input parameter.

This example shows how to use the <inputMappings> element to transfer data among tasklets of 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>

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

Yes

Community Additions

ADD
Show: