Workday Connector 8.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: Basic* or  *Workday: Advanced*, depending on your Workday implementation.
. Click  *OK*
. Enter the global element properties.
.. For *Workday: Basic* Configuration:
+
image:wd7-global-element-properties.png[wd7_global_elements]
+
[width="100a",cols="50a,50a",options="header",]
|===
|Field |Description
|*Name* |Enter a name for 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 usually has the suffix "pt_1" appended to it, 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 Global Element Properties image, the placeholder values refer to a configuration file in the `src` folder of your project. See link:/mule-user-guide/v/3.7/configuring-properties[Configuring Properties]. Either enter your credentials in the global configuration properties, or reference a configuration file containing 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: Advanced* Configuration:
+
[width="100a",cols="50a,50a",options="header",]
|===
|Field |Description
|*Name* |Enter a name of the configuration to reference it later
|*Requester Config* |Enter an HTTPRequester 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 *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 green plus sign *+* next to the *Connector Configuration* field:
+
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 follows:
+
[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 8.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 green plus sign *+* next to the *Connector Configuration* field and select *Workday: Basic* as the "global type"
+
image:wd7-choose-global-type.png[Choose Global Type]
+
. Configure the Workday global element, using credentials stored in a properties file, for example `src/main/resources/credentials.properties`:
+
image:wd7-global-element-properties.png[wd7 global element properties]
[NOTE]
For more information on setting credentials inside a properties file, refer to this section on  link:/mule-user-guide/v/3.7/configuring-properties#properties-files[Properties Files].
+
. 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 8.0 element from the dropdown.
|*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 *Transform Message* (DataWeave) component into the flow before the Workday Connector.
. Click the *DataWeave* component and then click the scaffold button image:scaffold-button.png[dataweave scaffold button] which appears above the code editor.
+
. Select the desired fields.
+
image:wd7-dataweave-scaffold-window.png[wd7_scaffold_window]
+
. Modify the DataWeave content so it matches the code below:
+
[source,dataweave,linenums]
----
%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
       }
     }
  }
}
----
. Save and run the project as a Mule Application. Then enter http://localhost:8081 in your browser and wait for the result. You should receive an XML response that looks like:
+
[source,xml,linenums]
----
<wd:Put_Fund_Response xmlns:wd="urn:com.workday/bsvc" wd:version="v25.0">
<wd:Fund_Reference wd:Descriptor="I.M.F">
<wd:ID wd:type="WID">THE_WID_ID_NUMBER</wd:ID>
<wd:ID wd:type="Fund_ID">FUND-6-399</wd:ID>
</wd:Fund_Reference>
</wd:Put_Fund_Response>
----
+

....
[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 the credentials into the file named `mule-app.properties` in the  `src/main/app` folder to provide the values for each variable, or as below, using a file called `credentials.properties` stored at `src/main/resources`.

[source,xml,linenums]
----
<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:context="http://www.springframework.org/schema/context"
	xmlns:dw="http://www.mulesoft.org/schema/mule/ee/dw"
	xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:wd-connector="http://www.mulesoft.org/schema/mule/wd-connector" xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:spring="http://www.springframework.org/schema/beans" version="EE-3.7.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-current.xsd
http://www.mulesoft.org/schema/mule/ee/dw http://www.mulesoft.org/schema/mule/ee/dw/current/dw.xsd
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/wd-connector http://www.mulesoft.org/schema/mule/wd-connector/current/mule-wd-connector.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd">
<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>
</mule>
----

....