---
title: "Fix Extend BP Subprocess allowedParentProcesses Schema Error"
description: "Fix schema validation errors for parentBusinessProcesses and initiationPageRoute by nesting inside allowedParentProcesses and adding {eventStepId}."
url: https://kiweely.com/guides/workday-extend-bp-subprocess-allowedparentprocesses-eventstepid
---

# Fixing “Object instance has properties which are not allowed by the schema (parentBusinessProcesses, initiationPageRoute)” on Extend Subprocesses

Adding an Extend Model Business Process as a subprocess of a delivered Workday business process fails validation if parentBusinessProcesses and initiationPageRoute are placed at the root of the .bp file or omit the {eventStepId} parameter. Learn the complete .bp, .amd, and .pmd configuration.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   3 min read
-   Published November 6
-   By Kiweely

## Why `parentBusinessProcesses` and `initiationPageRoute` Fail `.bp` Schema Validation

When configuring a Workday Extend Model Business Process (`.bp`) to run as a subprocess inside a Workday-delivered business process (such as `BACKGROUND_CHECK`, `HIRE`, or `CREATE_POSITION`), placing `parentBusinessProcesses` and `initiationPageRoute` at the root of the `.bp` JSON file triggers a schema validation error during deployment:

text

```
Object instance has properties which are not allowed by the schema: ["initiationPageRoute", "parentBusinessProcesses"]
```

In the Workday Extend `.bp` schema, `parentBusinessProcesses`, `name`, `label`, and `initiationPageRoute` are **not** root-level properties. They must be nested inside an object element of the **`allowedParentProcesses`** array (which supports up to 5 initiating actions and 5 unique parent business processes per Extend subprocess).

## Step 1: Nesting Inside `allowedParentProcesses` and Including `{eventStepId}`

Even after moving the properties inside `allowedParentProcesses`, a second validation error occurs if `initiationPageRoute` is written as a static path (for example, `"/createAdHocBackgroundCheckData"`). When a parent Workday business process reaches the subprocess step and places an initiation task in the processing user’s **My Tasks** inbox, Workday appends the subprocess step’s runtime `eventStepId` to the route. Therefore, `initiationPageRoute` **must** end with the `{eventStepId}` path parameter:

json

```
{
  "name": "AdHocBackgroundCheckProcess",
  "label": "Ad Hoc Background Check Process",
  "businessObject": "BackgroundCheckRecord",
  "securingDomain": "BackgroundCheckSecurityDomain",
  "allowedParentProcesses": [
    {
      "name": "InitiateAdHocBackgroundCheck",
      "label": "Initiate Ad Hoc Background Check",
      "parentBusinessProcesses": [
        "BACKGROUND_CHECK"
      ],
      "initiationPageRoute": "/createAdHocBackgroundCheckData/{eventStepId}"
    }
  ],
  "actions": [
    {
      "name": "reviewBackgroundCheck",
      "label": "Review Background Check",
      "type": "APPROVAL",
      "pageRoute": "/reviewBackgroundCheck/{eventStepId}"
    }
  ]
}
```

To verify which Workday-delivered business processes can act as parents for an Extend subprocess, run the **View Business Processes Available to Extend** report in your Workday tenant.

## Step 2: Matching `{eventStepId}` in the `.amd` Routing Pattern

In your Application Metadata (`.amd`) file, the task corresponding to the subprocess initiation page must declare the matching `{eventStepId}` parameter in its `routingPattern`:

json

```
{
  "tasks": [
    {
      "id": "createAdHocBackgroundCheckData",
      "routingPattern": "/createAdHocBackgroundCheckData/{eventStepId}",
      "page": {
        "id": "createAdHocBackgroundCheckData"
      }
    }
  ]
}
```

## Step 3: Wiring the Subprocess Initiation PMD Page

Unlike a standalone Extend Business Process that is initiated via `POST` when creating a record, an Extend subprocess is **already initiated** by the parent Workday business process before the user opens the initiation PMD page from **My Tasks**. At the moment of initiation, the subprocess event’s target is the parent business process event—not your Extend Business Object.

Your initiation PMD page (`createAdHocBackgroundCheckData.pmd`) must perform four actions using `queryParams.eventStepId`:

### 1\. Fetch the Subprocess Event Step and Event IDs (Inbound `endPoints`)

Query the `workday-bp` service to resolve `queryParams.eventStepId` into the subprocess event ID (`searchEventStep.event.id`):

json

```
"endPoints": [
  {
    "name": "searchEventStep",
    "baseUrlType": "workday-bp",
    "url": "<% 'eventSteps/' + queryParams.eventStepId %>",
    "authType": "sso"
  },
  {
    "name": "searchEvent",
    "baseUrlType": "workday-bp",
    "url": "<% 'events/' + searchEventStep.event.id %>",
    "authType": "sso"
  }
]
```

### 2\. Create the Business Object, `PATCH` the Subprocess Target, and Submit the Step (`outboundEndPoints`)

When the user clicks **OK** on the initiation PMD page, sequence three outbound endpoints in `outboundData`:

1.  **`createBoInstance` (`POST`)**: Creates the `BackgroundCheckRecord` instance.
2.  **`patchSubprocessEvent` (`PATCH`)**: Calls the generated Extend BP event endpoint (`adHocBackgroundCheckProcessEvents/{id}`) to update `businessProcessTarget.id` to `createBoInstance.id`.
3.  **`submitInitEventStep` (`POST`)**: Calls `eventSteps/{eventStepId}/submit` on `workday-bp` to complete the initiation task—guarded by an `exclude` condition so the step only submits if `patchSubprocessEvent.businessProcessTarget` succeeded.

json

```
"outboundData": {
  "outboundEndPoints": [
    {
      "name": "createBoInstance",
      "baseUrlType": "app",
      "url": "backgroundCheckRecords",
      "httpMethod": "POST",
      "authType": "sso",
      "values": [
        {
          "outboundPath": "vendorReference",
          "value": "<% vendorReferenceInput.value %>"
        }
      ]
    },
    {
      "name": "patchSubprocessEvent",
      "baseUrlType": "app",
      "url": "<% 'adHocBackgroundCheckProcessEvents/' + searchEvent.id %>",
      "httpMethod": "PATCH",
      "authType": "sso",
      "values": [
        {
          "outboundPath": "businessProcessTarget.id",
          "value": "<% createBoInstance.id %>"
        }
      ]
    },
    {
      "name": "submitInitEventStep",
      "baseUrlType": "workday-bp",
      "url": "<% 'eventSteps/' + queryParams.eventStepId + '/submit' %>",
      "httpMethod": "POST",
      "authType": "sso",
      "exclude": "<% !patchSubprocessEvent.businessProcessTarget %>",
      "values": [
        {
          "outboundPath": "comment",
          "value": "Completed Extend subprocess initiation step."
        }
      ]
    }
  ]
}
```

Always keep the `"exclude": "<% !patchSubprocessEvent.businessProcessTarget %>"` guard on `submitInitEventStep`. If the `PATCH` call fails and `submitInitEventStep` executes anyway, the task disappears from **My Tasks** while the subprocess remains attached to the parent BP target instead of your Extend Business Object.

## How to Verify in the Tenant

1.  Deploy the app to your Workday Extend development tenant and confirm that `.bp` schema validation succeeds with `allowedParentProcesses` and `/.../{eventStepId}`.
2.  Open **App Manager**, configure the Business Process Security Policy and Business Process Definition for the Extend subprocess, and add the subprocess step (`InitiateAdHocBackgroundCheck (Workday Extend: <App Name>)`) to the parent Workday business process definition.
3.  Trigger the parent business process in the tenant, open the initiation task in **My Tasks**, submit the PMD page, and verify on the subprocess event’s **Process History** tab that the target updated to the newly created Extend Business Object instance and routed to the next approval step.

## Sources checked

-   [Add Parent Business Process to Extend Subprocess](https://developer.workday.com/documentation/GUID-bf7ef8cb-6300-46e2-a4a2-122dba844794-enHYPHENus)
-   [Concept: Extend Subprocess Step Routing](https://developer.workday.com/documentation/GUID-4c03fde0-f66f-4596-b424-accc9dd346db-enHYPHENus)
-   [Steps: Initiate an Extend Subprocess from a PMD Page](https://developer.workday.com/documentation/GUID-0f36e7cb-08f4-4a92-9efd-945981a29dfe-enHYPHENus)
-   [Update the Target of the Extend Subprocess Event](https://developer.workday.com/documentation/GUID-f9dd0f7d-138c-4ddc-9cc1-494d285e1d92-enHYPHENus)
-   [Submit the Current Event Step](https://developer.workday.com/documentation/GUID-814690d1-9775-46e3-bf82-3ed76a7069d3-enHYPHENus)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Conditional Page Routing on Load, multiStepLayout vs. tabBar Navigation, and flowVariables Payload Limits in Workday Extend PMD Workday Extend PMD does not expose a redirect API in onLoad, cannot switch tabBar tabs from a button, and serializes flowVariables on the server across page transitions. Learn how to use conditional pods, multiStepLayout or editWizard, and Business Object persistence.](https://kiweely.com/guides/workday-extend-pmd-conditional-page-routing-tabbar-flowvariables-limits)
-   [### Working Around the 10-Relationship Limit on a Workday Extend Model Business Object (MCBO) Using a Helper Object Workday Extend enforces a platform ceiling of 10 SINGLE\_INSTANCE and MULTI\_INSTANCE relationship fields per Model Business Object (MCBO) and 25 delivered target relationships per app. Learn how to reserve the 10th slot for a 1:1 helper extension object and query across both objects in WQL.](https://kiweely.com/guides/workday-extend-mcbo-10-single-instance-relationship-limit-helper-bo)
-   [### How to Blank Out Text Fields and Nullify Reference Values on Workday Extend Business Objects via Inbound EIB Using {empty} Leaving a spreadsheet cell blank or entering “” or null in an Inbound EIB does not clear existing field values on a Workday Extend Business Object. Learn how to use the {empty} tag, avoid the leading/trailing whitespace trap in Excel, and remove specific multi-instance values.](https://kiweely.com/guides/workday-extend-eib-clear-text-nullify-fields-empty-tag)

### More guides on Extend apps and pages

[All 97 guides](https://kiweely.com/guides#extend)

-   [Cascading dropdowns and instance lists in Workday Extend](https://kiweely.com/guides/workday-extend-cascading-instance-lists)
-   [How to move Workday Extend apps to a new developer tenant before the old one expires or is deleted](https://kiweely.com/guides/workday-extend-move-apps-new-developer-tenant)
-   [Why a Workday Graph API query suddenly fails with “Cannot query field”](https://kiweely.com/guides/workday-graphql-cannot-query-field)
-   [How to build a worker search prompt in a Workday Extend page](https://kiweely.com/guides/workday-extend-worker-search)
-   [Which Workday Extend widget to use for what](https://kiweely.com/guides/workday-extend-widget-guide)
-   [Workday Extend Professional is now Extend AI: Core vs AI vs legacy limits, storage and AI features](https://kiweely.com/guides/workday-extend-legacy-vs-extend-professional)
-   [Model business processes in Workday Extend: how a transaction gets created and approved](https://kiweely.com/guides/workday-extend-model-business-process)
-   [Version control for Workday Extend apps: GitHub, Local Disk Sync and automated deploys](https://kiweely.com/guides/workday-extend-version-control-github)

### From the blog on Extend apps and pages

[All posts](https://kiweely.com/blog)

-   [Five Workday Extend app blueprints you can build in a free personal tenant](https://kiweely.com/blog/five-workday-extend-apps-to-build-in-open-developer-program)
-   [From Business Brief to Tested Workday Extend App: Why Zero Validation Errors Is Not Proof](https://kiweely.com/blog/why-workday-extend-validation-is-not-testing)
-   [Workday Extend Graph API and AppHub Promotion: Moving Apps From Development to Sandbox](https://kiweely.com/blog/workday-extend-graph-api-and-apphub-promotion)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
