Workday Connector 7.0

[tab,title="Studio Visual Editor"]
....

. Click the *Global Elements* tab at the base of the canvas.
. On the Global Mule Configuration Elements screen, click *Create*.
. In the Choose Global Type wizard, expand *Connector Configuration,* and then select *Workday Connector: configuration* or  *Workday Connector: configuration (advanced)*, depending on your Workday implementation.
. Click  *OK*
. Enter the global element properties.
.. For *Workday Connector: Configuration*:
+
image:wd6_global_elements.png[wd6_global_elements]
+
[width="100a",cols="50a,50a",options="header",]
|===
|Field |Description
|*Name* |Enter a name of the configuration to reference it later
|*Username* |Enter the username to log in to Workday.
|*Password* |Enter the corresponding password.
|*Tenant Name* |Enter the Workday Tenant ID. It is usually appended with pt_1, such as acme_pt1.
|*Host Name* |Enter the host name of one of the Workday Cloud Servers. By default, the connector sets the host name to `impl-cc.workday.com`.
|===
+
[NOTE]
====
In the image above, the placeholder values refer to a configuration file placed in the `src` folder of your project (learn about link:/mule-user-guide/v/3.7/configuring-properties[Configuring Properties].) You can either enter your credentials into the global configuration properties, or reference a configuration file that contains these values.

For simpler maintenance and better re-usability of your project, Mule recommends that you use a configuration file. Keeping these values in a separate file is useful if you need to deploy to different environments, such as production, development, and QA, where your access credentials differ. See link:/mule-user-guide/v/3.7/deploying-to-multiple-environments[Deploying to Multiple Environments] for instructions on how to manage this.
====
+
.. For *Workday Connector: Configuration (Advanced):*
+
[width="100a",cols="50a,50a",options="header",]
|===
|Field |Description
|*Name* |Enter a name of the configuration to reference it later
|*Requestor Config* |Enter an HTTPRequestor configuration.
|*Username* |Enter the username to log in to Workday.
|*Password* |Enter the corresponding password.
|*Tenant Name* |Enter the Workday Tenant ID. It is usually appended with pt_1, such as acme_pt1.
|*Host Name* |Enter the host name of one of the Workday Cloud Servers. By default, the connector sets the host name to `impl-cc.workday.com`.
|===
. Keep the *Pooling Profile* and the *Reconnection* tabs with their default entries.
. Click *Test Connection* to confirm that the parameters of your global Workday connector are accurate, and that Mule is able to successfully connect to your Workday instance. Read more about link:/docs/display/current/Testing+Connections[Testing Connections].
. Click *OK* to save the global connector configurations. 

....
[tab,title="XML Editor"]
....

To configure the Workday global element:

. Ensure you have included the following namespace in your configuration file:
+
[source,xml]
----
xmlns:wd-connector="http://www.mulesoft.org/schema/mule/wd-connector"
----
. Create a global Workday configuration outside and above your flows, using the following global configuration code:
+
[source,xml]
----
<wd-connector:config name="Workday_Connector__Configuration" username="${workday.username}" password="${workday.password}" tenantName="${workday.tenantname}" doc:name="Workday Connector: Configuration"/>
----

....

[tab,title="Studio Visual Editor"]
....

. Create a Mule project in your Anypoint Studio.
. Drag an HTTP connector into the canvas, then select it to open the properties editor console.
. Add a new HTTP Listener Configuration global element:
.. In *General Settings*, click the plus *+* button:
+
image:wd6_http_config.png[wd6_http_config]
+
.. Configure the following HTTP parameters:
+
image:wd6_http_listener_configuration.png[wd6_http_listener_configuration]
+
[width="100%",cols="50a,50a",options="header",]
|===
|Field|Value
|*Port* |8081
|*Host* |localhost
|*Display Name* |HTTP_Listener_Configuration
|===
+
. Add a Set Payload transformer after the HTTP connector, and configure it as follow:
+
[width="100%",cols="50a,50a",options="header",]
|====
|Field |Value
|*Display Name* |Enter a name for the transformer.
|*Value* |`#[['FundName':' I.M.F' , 'FundTypeID' : ' FUND_TYPE-6-3']]"`
|====
+
. Drag the Workday Connector 7.0 into the flow.
+
image:wd6_palette.png[wd6_palette]
+
. If you haven't already created a Workday global element, add one by clicking the plus sign *+* next to the *Connector Configuration* field.
. Configure the global element:
+
image:wd6_global_elements2.png[wd6_global_elements2]
+
. Click *Test Connection* to confirm that Mule can connect with the Workday instance. If the connection is successful, click *OK* to save the configurations of the global element. If unsuccessful, revise or correct any incorrect parameters, then test again.
. Back in the properties editor of the connector, configure the remaining parameters:
+
image:wd6_connector2.png[wd6_connector2]
+
[cols=",",]
|===
|*Field* |*Description*
|*Display Name* |Enter a unique label for the connector in your application.
|*Connector Configuration* |Select a global Workday connector 7.0 element from the drop-drown.
|*Operation* |Invoke.
|*Service* |Select a Workday service, such as Financial Management.
|*Operation* |Select an operation to perform in the service, such as Put Fund.
|===
+
. Drag a DataWeave component in to the flow, and place it before the Workday Connector.
. Click the Data Weave component and click the scaffold button. 
. Select the desired fields.
+
image:wd6_scaffold.png[wd6_scaffold]
+
. Modify the Weave content as shown in the image below:
+
image:wd6_mapping.png[wd6_mapping]
+
. Save and run the project as a Mule Application.

....
[tab,title="XML Editor"]
....

[NOTE]
For this code to work in Anypoint Studio, you must provide the credentials for the Workday instance. You can either replace the variables with their values in the code, or you can add a file named `mule.properties` in the  `src/main/properties` folder to provide the values for each variable.

[source,xml,linenums]
<context:property-placeholder location="credentials.properties"/>
 <http:listener-config name="HTTP_Listener_Configuration" host="0.0.0.0" port="8081" doc:name="HTTP Listener Configuration"/>

 <wd-connector:config name="Workday_Connector_Configuration" username="${workday.username}" password="${workday.password}" tenantName="${workday.tenantname}" doc:name="Workday Connector: Configuration"/>

 <flow name="demoFlow">
   <http:listener config-ref="HTTP_Listener_Configuration" path="/" doc:name="HTTP"/>
   <set-payload value="#[['FundName':' I.M.F' , 'FundTypeID' : ' FUND_TYPE-6-3']]" doc:name="Set Payload"/>
   <dw:transform-message doc:name="Transform Message"> +
   <dw:set-payload><![CDATA[%dw 1.0
  %output application/xml
  %namespace ns0 urn:com.workday/bsvc
  ---
  {
   ns0#Put_Fund_Request @(ns0#Add_Only: true , ns0#version: "v25.0"): {
     ns0#Fund_Data: {
        ns0#Fund_Name: payload.FundName,
          ns0#Fund_Type_Reference: {
            ns0#ID @(ns0#type: "Fund_Type_ID"): payload.FundTypeID
          }
        }
     }
  }]]></dw:set-payload>
   </dw:transform-message>
   <wd-connector:invoke config-ref="Workday_Connector_Configuration" type="Financial_Management||Put_Fund" doc:name="Workday Connector"/>
 </flow>
 ----

....