---
nav: wcp_docs
parent_url: /wcp_docs/
title: Create an Edit Page to Submit Workday Data
layout: subsection
---
An Edit page in a Workday Extend custom app is designed to let you input data and submit it to a business object. It centralizes all relevant fields, validations, and conditional logic needed to safely update that object, while respecting security, field-level visibility, and tenant configuration.
In this activity, you’ll:
- Use a Basic Form Layout to build a basic input form with instructions.
- Create three Layout Sections that contain Field Sets and input fields, including a Date field and Instance Lists from which users can select worker names and office locations.
- Configure Inbound API endpoint that gets data from a Workday API.
- Configure an outbound API endpoint that sends data to a custom business object.
## Before You Begin: Create an Account on the Workday Build Platform
To do this activity, you must have an account on the Workday Build platform and a development tenant. If you’ve already created an account and a tenant, you can go to the first task of this activity.
If you haven’t already created an account, you can do so now. It’s free!
1. Go to the [Workday Build Platform](https://developer.workday.com) and create an account with your personal email address.
2. Once you have created an account, sign in to the [Workday Build Platform](https://developer.workday.com).
3. In the upper-left corner, select the hamburger menu, and under Console, select Tenants.
4. On the Tenants page, select Create Tenant. It will take 1 to 2 minutes for the development tenant to be created.
5. Check your personal email for a link to change your tenant password.
Note: Remember the password. You’ll need to sign in to the tenant while you do this activity.
6. Sign in to the tenant with the username lmcneil and the password that you just created.
Note: When you sign in to the development tenant with the username lmcneil, you’re signing in as the persona Logan McNeil. Logan is one of several user accounts that you can use to test the agents and app that you create and deploy to your development tenant.
## Task #1: Create an Extend App from Starter Code
To begin, create an Extend app from starter code that we’ve provided below. The starter code includes a model business object and security domain.
1. Download the [WorkDesignationStarterCode.zip](GUID-90222c69-f297-4535-81b9-36915ad84a3c.zip) file.
2. On your Express Lab laptop, select the browser tab for the[Workday Developer Platform](https://developer.workday.com).
3. On the Developer Site home page, select Build an Extend App.
4. Select Upload a Zip File.
5. In the Name field, enter Get User Input App. The Reference ID will automatically populate based on the app's name.
6. Click Select a File, navigate to your computer’s Download folder, and select the [WorkDesignationStarterCode.zip](GUID-90222c69-f297-4535-81b9-36915ad84a3c.zip) file.
7. Select Create and Edit. This opens App Builder.
Expected result: App Builder should be open with your newly created app, as shown below.
## Task #2: Deploy the App and Configure the Security Domain
To ensure your application is functional and secure, deploy it to your development tenant. In this task, you will deploy your app, create a dedicated security domain, and configure the necessary permissions. These steps are essential for controlling user access and protecting the data processed by your application.
1. In the upper right corner of App Builder, select Save and Deploy.
2. In the Deploy pop-up window, select your tenant, select Deploy to Tenant, and sign in to the tenant.
3. In the Deploy Successful pop-up window, select Manage in Tenant. This launches the App Manager report. App Manager is the central Workday Extend console where you register, configure, secure, deploy, and monitor your Extend applications and their APIs across your tenant.
4. In App Manager, find your app and select Configure.
5. Scroll down the App Details page to the Security Domains section, and to the right of the Work Designation Security Domain, select Create.
6. In the Create Security Policy for Domain pop-up window, check the Confirm box and select OK. This will take you to the Edit Permissions page.
7. On the Create Security Policy for Domain page, in the Report/Task Permissions table, select the + Add Row icon.
8. In the Security Groups field, enter HR Admin, press Enter, and select HR Administrator.
9. Check the View and Modify boxes, select OK, and select Done. This will return you to the App Details page.
10. In the Security Domains section, select Activate Pending Security. You must activate the security changes in order for them to take effect.
11. In the Comment field, enter Create security policy and select OK.
12. On the next page, check the Confirm box and select OK.
✅ Expected result: You must give one or more security groups Report/Task Permissions in a Workday Extend app. This enables Workday to know which users are allowed to access the app’s reports, tasks, and APIs at runtime, enforcing tenant security and preventing unauthorized users from running or viewing the app’s functionality and data.
## Task #3: Create an Inbound Endpoint That Gets Workers Names
In an input form, you can enable users to pick from a list of values, such as worker names or locations. To do this, you must add an Inbound API Endpoint to the page that will get the data you want to display.
An Inbound API Endpoint is designed to retrieve data from an API or external source. Its primary purpose is to fetch this data so it can be used to dynamically populate UI components, such as Instance Lists, allowing users to view or select information directly within the app.
In this task, you’ll create an Inbound API Endpoint from which you can get data and display it in an Instance List, which you’ll configure in the following tasks.
1. Return to App Builder, select the changeWorkLocations page, and select the Page Load tab.
2. In the Inbound Endpoints section, hover above locationValuesGet Endpoint, select + Add Inbound Endpoint > REST Endpoint.
3. In the Enter Name field, enter getAllWorkers.
4. In the HTTP Method field, select Get (default).
5. In the Base URL Type field, enter staffing.This is a key of a dataProvider in the App Metadata (AMD) component. It specifies the base URL of [Staffing REST API](https://developer.workday.com/rest-api-explorer/docs/staffing/v7#get-/workers).
6. In the URLfield, enter /workers.This is the endpoint of the Staffing REST API.
7. In the Auth Type field, enter sso.
8. Select Save to App Hub.
✅ Expected result:The getAllWorkersinbound endpoint should be configured to get a list of workers from the Staffing REST API.
## Task #4: Create Outbound API Endpoint That Submits Form Data
An Outbound API Endpoint is a component configured to submit data from a page to a Workday business object or a custom business object. Its primary purpose is to enable users to submit form data, ensuring that the information is successfully persisted within Workday.
This is a good point to add the Outbound Endpoint because you’ll need to reference it when you configure the Value Out Bindings on the input fields that you’ll create in the following tasks.
1. On the changeWorkLocationpage, select the Page Submit tab.
2. In the Outbound Endpoints section, select + Add Outbound Data > Outbound REST Endpoint.
3. Name the outbound endpoint createWorkDesignation.
4. In the HTTP Method field, select Post (default).
5. In the Base URL Type field, enter app.
6. In the URLfield, enter workdesignations.
7. In the Auth Type field, enter sso.
8. Select the On Send tab, and in the text field, enter:
```
console.info(json:asJSON(self.data)); return self.data;
```
9. Select the Error Handling tab and select + Add Fail On Status Codes:
- In the Codefield, enter 400, and in the Code Name field, enter Bad request.
- Select + Add Item, and in the Codefield, enter 403, and in the Code Name field, enter Forbidden.
10. Select Save to App Hub.
✅ Expected result: The createWorkDesignation Outbound REST Endpoint is successfully configured with the correct method, URL, and error handling settings, making it ready to be referenced by your form's fields to persist user-submitted data to your business object.
## Task #5: Add a Field Set and an Instance List to Display Worker Names
In this task, you’ll add a new Layout Section with a Field Set and an Instance List, which will display a list of workers retrieved by the inbound API endpoint that you created in the previous task.
A Field Set is a layout container used in a Workday Extend app page to group related fields or sections under a specific title, helping to organize the interface into distinct, logical categories.
An Instance List enables you to display a selectable collection of items, providing a user-friendly way for users to browse and pick specific values from a set of data.
1. On the changeWorkLocation page, select the Presentation tab.
2. Scroll down the page below the Rich Text tag, hover over the vertical Basic Form Layer line (see image below), and select + Add Layout Section in Basic Form Layout.
3. On the new Layout Section card, select + Add Child, and select Field Set.
4. In the Field Set tag’s Title field, enter Select an Employee.
5. On the Field Set card, select + Add Child, and select Section.
6. Expand the Section tag and check the Horizontal box so that it’s set to true.
7. Select + Add Column Width Ratios:
1. In the 0 column, enter .3.
2. Select + Add Item, and in the 1 column, enter .7.
8. On the Section tag, select + Add Child, and select Section.
9. On the new Section, select + Add Child, and select Instance List.
10. Select the Expand > icon to show all the Instance List’s attributes:
1. In the ID field, enter workerSearch.
2. In the Label, enter Employee.
3. In the Display Key field, enter descriptor. The Display Key specifies which field from the data source should be displayed in the list. In this case, the descriptor field holds the worker name.
4. In the ID Key field, enter id. The ID Key attribute acts as the unique identifier for each item. When a user selects a name from the list, the ID Key ensures the unique ID is correctly passed to the business object.
5. Check the Required box (true). This means the user must enter data in the field.
6. In the Value Out Binding field, enter createWorkDesignation.worker.id. The Value Out Binding attribute maps the data entered by a user into a UI element (such as an Instance List or Date field) to the corresponding field defined in your Outbound API endpoint.
7. In the Values attribute, enter getAllWorkers.data. This PMD script references the getAllWorkers inbound API endpoint, where .data accesses the root element of the JSON response.
11. Open App Preview, and in the upper-right, select the App Preview pop-up window icon to open it in a new browser tab.
12. Select the Employee instance list to verify that it displays worker names.
13. Save to App Hub.
✅ Expected Outcome: In a new section, you have created an Instance List from which a user can select an employee’s name. It specifies a value out binding that will enable the selected value to be submitted to the business object.
## Task #6: Add and Format a Date Field
In this task, you’ll create a third Layout Section that will contain a Date field and an Instance List from which users can select work locations. (You’ll add the Instance List in the following tasks.)
In a Date tag, you can use a PMD script to ensure data is collected or presented in the correct format.
1. On the changeWorkLocation page, hover over the vertical Basic Form Layer line below the second Layout Section, and select + Add Layout Section in Basic Form Layout.
2. Select + Add Child and select Field Set.
3. In the Field Set Title, enter Request Details.
4. On the Field Set tag, select + Add Child, search for and select Date.
5. On the Date tag’s ID field, enter effectiveDate and in the Label field, enter Effective Date.
6. Select the Value field, and to the right of the field, select Change to scripted value.
7. To the right of the Value field, select to change the field to a scripted value and in the field enter this PMD script: date:now(userTimeZone).format('yyyy-MM-dd')
8. Check the Required box so that it’s set to true.
9. Select + Add Values Out:
1. In the Value field, select the icon to change it to a scripted value and enter self.value.
2. In the Value Out Binding field, enter createWorkDesignation.date.
10. Open App Preview to check your changes.
11. Save to App Hub.
✅ Expected Result: You should see the third layout section with a title and a date field displaying today’s date.
## Task #7: Add an Inbound API Endpoint to Get Work Locations
Let’s add an Inbound WQL Endpoint to the page that will return work location data.
Workday Query Language (WQL) is a query language used within Workday Extend apps to fetch specific, structured data from Workday. Developers can dynamically populate UI components such as Instance Lists using WQL.
1. On the changeWorkLocation page, select Page Load.
2. Hover over the area below the getAllWorkers inbound endpoint and select Add Inbound Endpoint > WQL Endpoint.
3. In the Enter Name field, enter getLocationValues. This is the name that PMD tags on the page will use to reference the endpoint.
4. Keep the HTTP Method set to Get (default).
5. In the Base URL Type field, enter wql. This references a data provider declared in the AMD component.
6. To the right of the URLfield, select to change it to a scripted value.
7. Copy the WQL query below:
```
let query = 'select location, country from locationsUsedAsBusinessSite';
return `/data?query=` + query.urlEncode();
```
8. In the URLfield, paste the WQL query.
9. In the Auth Type field, enter sso.
10. Select Save to App Hub.
✅ Expected Result: Your Inbound Endpoint should be configured like the one in the image below.
## Task #8: Create an Instance List That Displays Work Locations
In this task, you’ll create an Instance List that will display a list of work locations. The list will be populated from a Workday API endpoint that uses a Workday Query Language (WQL) query.
An Instance List displays a selectable collection of items, such as a list of employees or work locations. An Instance List provides a user-friendly way for users to browse and pick specific values from a set of data.
1. On the changeWorkLocation page, select the Presentation tab.
2. Scroll down to the Date tag, hover over the area below the Date tag, select + Add Tag in Field Set, then search for and select Instance List.
3. In the IDfield, enter proposedLocation and in the Labelfield, enter Work Location.
4. Check the Required box so that it’s set to true.
5. In the Display Key field, enter descriptor.
6. In the ID Key field, enter descriptor.
7. In the Value Out Binding field, enter createWorkDesignation.workLocation.
8. To the right of the Valuesfield, select to change the field to a scripted value, and in the field enter the PMD script below.
```
getLocationValues.data.map(x => x.location)
```
Note: This PMD script uses the map ( ) function to iterate over objects in the data and return values from the location field. getLocationValues is the name of the API endpoint and data is the JSON path to the root of the data structure.
9. Open App Preview, and if necessary, reconnect to the tenant.
10. In App Preview or the App Preview Pop-Up window (shown below), select the Work Location Instance List. It should display a list of cities.
11. Select Save to App Hub.
✅ Expected Result: In the App Preview Pop-Up window, shown below, select the Work Location Instance List to see a list of cities from which the user can pick.
## Task #9: Create a Hardcoded List for Workplace Designations
In this task, you’ll add a new Instance List to indicate if the employee:
1. Works from Home.
2. Works Hybrid - Partially at Home and Partially in the Office.
3. Entirely in the Office
If the employee works entirely from Home, then you need to hide the Proposed Location field. If the employee works hybrid or entirely in the Office, then you will need to display the Proposed Location field.
1. On the changeWorkLocation page, select the Presentation tab.
2. Scroll down to the Field Set with the title Request Details.
3. In the Field Set, hover over the area below the Date tag (effectiveDate) and above the Instance List tag (proposedLocation), select the + Add Tag in Field Set icon, and select Instance List.
4. In the new Instance List tag:
1. Set ID to proposedWorkDesignation.
2. Set Label to Work Designation.
3. Check the Required attribute so that it is set to true.
5. Scroll down the Instance List tag, select Add Instance List, and add the first option to the list:
1. In the ID field, enter HOME.
2. In the Descriptor field, enter Works Fully from Home.
6. Select Add Item to add a second option to the list:
1. In the ID field, enter HYBRID.
2. In the Descriptor field, enter Works from Home and the Office.
7. Select Add Item to add a third option to the list:
1. In the ID field, enter OFFICE.
2. In the Descriptor field, enter Works Fully in the Office.
8. Copy the code block below. This is a [PMD script](/wcp_docs/oli1581402304020.html#G_PEER_1) that controls the location field based on the value that the user selects. If they select HOME, it clears the proposed location (setValue([ ])) and hides the proposedLocation field (visible = false). If the selection is HYBRID or OFFICE, then the proposedLocation field remains visible.
```
if(proposedWorkDesignation.value.first() == 'HOME') {
console.info('In the Fully From Home code branch');
proposedLocation.setValue([]);
proposedLocation.visible = false;
} else {
console.info('In the office or hybrid code branch');
proposedLocation.setValue([]);
proposedLocation.visible = true;
}
```
9. Scroll down to the On Change attribute and paste the code into it.
10. In the Values Out Binding field, enter createWorkDesignation.workType.
11. Return to App Preview Pop-Out window and refresh the page.
12. From the Work Designation list, select Works Entirely From Home.
✅ Expected Result: When Works Entirely From Home is selected, the Work Location field is hidden. When Works in the Office or Works Hybrid are selected, the Proposed Work Location remains visible.
## Task #10: Test the Input Page
Now that you have configured your layout, fields, and API endpoints, it is time to verify the end-to-end functionality of your edit page. In this final task, you will complete the form, trigger the submission, and confirm that the data is correctly persisted to your custom business object.
1. Select the changeWorkLocation page, open App Preview, and select the App Preview pop-up window icon to view the page in a new browser tab.
2. Complete the form:
1. Select a worker from the Employee list.
2. Pick an Effective Date.
3. From the Work Designation list, select HOME, OFFICE, or HYBRID
4. If you selected OFFICEor HYBRID, select a city from the Work Location list. (If you picked HOME, the Work Location list should not be visible.)
3. Select OK to submit the form. You should be routed to the home page, where you’ll see the data you submitted displayed in a grid.
✅ Expected Result: You should be routed to the home page, where you’ll see the data you submitted displayed in a grid.
## Congratulations
In this tutorial, you learned how to create and configure an Edit page in a Workday Extend custom app to collect and submit user data. You gained experience in:
- Creating an app from starter code and deploying it to a tenant.
- Configuring security domains and permissions.
- Setting up Inbound API endpoints to fetch data (worker names and locations) and Outbound API endpoints to submit form data.
- Designing a user interface with layout sections, field sets, date fields, and instance lists.
- Implementing PMD scripting to handle conditional logic, such as showing or hiding fields based on user selection.