# Call operation
This action makes use of the Workday Web Services (WWS) to execute SOAP-based operations in a connected Workday instance.
The full set of operations available can be found on Workday Web Services Directory.
The Workday connector works with v29.0 and v32.2 of WWS.
First, define the operation that you want to execute in your Workday instance, next supply the data to the sent with the operation. This set of input fields depends on the type of operation that was selected.
|Operation||Name of the Workday Web Services operation to execute. This must be selected before the rest of the input fields can be determined.|
|Fields with attributes||
Select the fields that require values assigned to attributes. These are attributes that will be included in the XML tag of the selected field.|
This field is present only for operations that have at least one field with attributes.
|Fields with multiple values||
Select the fields that need to be repeated in the operation data.|
This field is present only for operations that have at least one field that can be repeated.
Select Maintain Contact Information
This is a full list of all operations in Workday Web Services. To find the operation that you want, simply use keywords to filter and narrow down the list of possible matches.
In this example, we are looking for the Maintain Contact Information operation. Here, we are creating a recipe to update the email address of a Workday record when the employee's email changes.
# Fields with attributes
Selecting Email Address Data to include attribute values
Suppose we want to add new email addresses to a particular contact without replacing any existing email addresses. This can be done by setting the Do_Not_Replace_All attribute of the Email address data field to
Maintain Contact Information Data/Worker.../Email Address Data. This will generate all possible attributes for the Email address data field, including Do_Not_Replace_All.
# Fields with multiple values
Selecting Email Address Data field to be repeated
Suppose that our use case may involve more than one email address. To support this, we will have to send multiple email addresses in a single operation.
Maintain Contact Information Data/Worker.../Email Address Data. This will change the Email address data into a list type input field. With that, you can map one or more email addresses using a list.
The complete set of fields and attributes for the selected operation will be available in the output datatree.