---
category: [Administration & Integrations, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions, Platform and Product Extensions/Workday Extend, Platform and Product Extensions/Integration]
keyword: [Extend, Model Components, Extend BPs, Extend Business Processes, Model Business Processes, Extend BP]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Reference: Design Considerations for Business Processes
layout: subsection
---

<a id="section_N1003D_N1003A_N10001"></a>
Workday Extend provides you with a lot of flexibility in how you implement business processes when you build a Workday Extend app. However, you should take these considerations into account when you design your app.

## <a id="section_fnp_w5z_s4b"></a>Parallel Requests

Determine if your app needs to allow parallel requests. Example: A worker might be able to submit 2 requests in parallel seeking permission to bring a dog to work. However, that same worker shouldn't be able to submit multiple tuition reimbursement requests at the same time. Consider the implications for your business before you use presentation components to implement parallel requests in your app.

## <a id="section_rcz_z5z_s4b"></a>Business Process Event History

If you want the business process event history to consistently reflect the business object data as of the time of the business process event, your app shouldn't allow changes to business object data. Workday doesn't lock business object data while the business process is in progress, nor after the business process is approved. It's unlikely that a developer would build pages to edit a business object while a business process is in progress. However, if you update business object data after a business process is approved, the event details in the business process event history could display the updated data.

<b>Note:</b> The audit trail for the business object reflects the changes.

## <a id="section_pgj_cvz_s4b"></a>Associate a Business Object with a Business Process

After you associate a business object with a business process, you can't delete that instance of the business object.

## <a id="section_fbv_dvz_s4b"></a>Route a Business Process to Constrained Security Groups

You can route a business process to constrained security groups if you set the `"secureByTarget": true` attribute on a `SINGLE_INSTANCE` field of the target business object definition. Make sure that you understand all business process routing requirements when you design your app.

## <a id="section_nfb_hvz_s4b"></a>Add Custom Pages

You can add a custom page to these steps and views of a business process:

-   Action step.
-   Approval step.
-   Event Details: A custom page that enables you to specify the information that displays on the Details page for the business process event.
-   Initiation: A custom page that enables a worker to initiate the business process.
-   Revise: A custom page that displays in a worker's tasks in <b>My Tasks</b> and enables the worker to revise business object data and resubmit the request.


Only the Action step, the Initiation page, and the Revise page enable you to call outbound endpoints from a custom page. If you need to update business object data after a business process is approved, consider these options:

-   Add an Action step to the business process definition immediately after the Approval step.
-   Use an Asynchronous Orchestration to update the business object after approval.
-   Use a scheduled integration to parse daily approval events and then update business object data.


## <a id="section_pwm_3vz_s4b"></a>Delegate Business Processes

The business processes that you create for your Workday Extend app don't support delegation.

### Related Information

[Tutorial: Model Components: Business Processes](https://wd5.myworkday.com/workday/learning/course/8217842f19801001bb98eac6f24c0000?type=9882927d138b100019b928e75843018d)