appSettings Element

Defines key-value pairs for configuring or customizing instances of tasklets in the application. A tasklet can be developed to include key-value pairs that you can set in the UserRole.xml file to change its configuration and behavior. You can set up <appsettings> element on a global basis for all instances of a tasklet in the application, on an orchestration basis for instances of a tasklet in a specific orchestration, or directly on the instance of a tasklet.

userRole Element

    appSettings Element

    orchestrations Element

        orchestration Element

            appSettings Element

            tasklets Element

                tasklet Element

                    configuration Element

                        appSettings Element

    tasklets Element

        tasklet Element

            configuration Element

                appSettings Element


<appSettings>
    <add key="unique identifier" value="setting" />
</appSettings>

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

Attributes

None.

Child Elements

Element Description

add Element (under appSettings element)

Species the configuration setting using two values: key and value. key is a string that species the unique identifier for the setting, and value is a string that specifies the actual setting.

Parent Elements

Element Description

configuration Element

Customizes the tasklet in the application. When used in this element, the <appSettings> element key-value pairs pertain to instances of the associated tasklet only.

orchestration Element

Defines a specific orchestration of tasklets in the application. When used in this element, the <appSettings> element key-value pairs pertain only to the tasklet instances in the orchestration.

userRole Element

The root element for the UserRole.xml file. When used in this element, the <appSettings> element key-value pairs pertain to the entire application.

The following example displays an orchestration that shows details of a customer and a contact for the customer. The tasklets of the orchestration have a key-value pair that changes the tasklets between two modes: Edit and View. Edit sets the tasklets to a read-write mode that allows the user to change information about the customer and contact; View sets the tasklet to a read-only mode that prevents the user from making changes. So given the purpose of this orchestration, an <appSettings> element is added to include a key-value pair that sets tasklets of the orchestration to the View mode.

<orchestration text="Customer detail" name="CustomerDetailReadOnly">
  <appSettings>
    <add key = "TaskletMode" value = "View"/>
  </appSettings>
  <tasklets>
    <tasklet name="CustomerDetailTasklet" text="Customer Details" type="CustomerDetailTasklet.CustomerDetailTasklet, CustomerDetailTasklet">
      <actions>
        <open text="Contact" tasklet="CustomerContactDetailTasklet">
          <inputMappings>
            <inputMapping propertyName="CustomerId" stateKey="CustomerID"/>
          </inputMappings>
        </open>
      </actions>
    </tasklet>
    <tasklet name="CustomerContactDetailTasklet" text="Contact Details" type="CustomerContactDetailTasklet.CustomerContactDetailTasklet, CustomerContactDetailTasklet">
    </tasklet>
  </tasklets>
</orchestration>

Required

No

Max occurrences

1 within parent element.

Namespace

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

Schema Name

UserRole Schema

Validation File

Orchestration.vsd

Can be Empty

Yes

Community Additions

ADD
Show: