---
title: "Fix blank launch parameter simple type error — Kiweely"
description: "Why leaving an optional Text, Number, Boolean, or Date launch parameter blank in O4I throws 'not a simple type launch parameter' and how to guard it with lp."
url: https://kiweely.com/guides/workday-orchestrate-null-launch-parameter-not-simple-type
---

# Fixing ‘not a simple type launch parameter (Text, Number, Boolean, Date)’ on blank O4I launch parameters

Calling lp.stringParam, lp.simpleData, lp.numberParam, or lp.dateParam on an optional launch parameter that was left blank at launch throws ‘Parameter is not a simple type launch parameter (Text, Number, Boolean, Date)’. Check lp.existsAndHasValue(‘ParamName’) first before reading the parameter.

-   **Checked** against Workday on November 6
-   Applies to **Workday Orchestrate**
-   4 min read
-   Published November 6
-   By Kiweely

## Why leaving a launch parameter blank throws `"not a simple type launch parameter"`

When you launch a **Workday Integration System** (O4I) orchestration in a tenant and leave an optional launch parameter empty (for example, an optional `NominationSubmittedDate` parameter of type **Text** or **Date**), the integration fails immediately—often on the very first **Create Values** step—with:

text

```
Parameter 'NominationSubmittedDate' is not a simple type launch parameter (Text, Number, Boolean, Date)
```

When you relaunch the exact same integration and populate `NominationSubmittedDate` with `2026-09-21`, the orchestration completes without error.

### Root cause in the integration launch event XML

When an Integration System is launched in Workday and the user leaves an optional simple launch parameter blank on the **Schedule an Integration** page, Workday either omits the value node from the launch event payload or passes an empty/untyped parameter node.

In Orchestrate’s `lp` global function qualifier (**Reference: Lp Global Functions**), functions that read simple launch parameters—including `lp.simpleData(label)`, `lp.stringParam(label)`, `lp.numberParam(label)`, `lp.booleanParam(label)`, `lp.date(label)`, and `lp.dateParam(label)`—verify that the runtime parameter exists in the launch payload and carries a populated simple type (`Text`, `Number`, `Boolean`, or `Date`). If you call `lp.simpleData("NominationSubmittedDate")` or `lp.stringParam("NominationSubmittedDate")` directly when the parameter was left blank, the runtime throws `Parameter '<label>' is not a simple type launch parameter (Text, Number, Boolean, Date)` before any downstream `.isEmpty()` check on the returned string can execute.

Even if you wrote an expression like `lp.simpleData("NominationSubmittedDate").isEmpty()` inside a **Create Values** condition to default a blank parameter to today’s date, `lp.simpleData("NominationSubmittedDate")` itself throws the exception before `.isEmpty()` is ever reached.

## How to guard optional launch parameters with `lp.existsAndHasValue`

Workday’s **Reference: Lp Global Functions** provides two existence-checking functions specifically for guarding optional launch parameters before you read their values:

| Function | Arguments | Return Type & Behavior |
| --- | --- | --- |
| `lp.existsAndHasValue(label: String)` | `label` (or `provider, label`) | Returns `true` (`Boolean`) only if the runtime parameter with the specified label is defined **and has a non-empty value**. |
| `lp.exists(label: String)` | `label` (or `provider, label`) | Returns `true` (`Boolean`) if the runtime parameter with the specified label is defined and is not `null`. |

For optional numeric parameters, Workday also provides a built-in default function:

| Function | Arguments | Return Type & Behavior |
| --- | --- | --- |
| `lp.numberParamWithDefault(label: String, defaultValue: String)` | `label`, `defaultValue` (or `provider, label, defaultValue`) | Returns the runtime parameter as a `Number` (`Double`) if it exists and is numeric; returns `defaultValue` if the parameter does not exist. |

Notice that **Reference: Lp Global Functions** has `lp.numberParamWithDefault`, but does **not** have a `stringParamWithDefault` or `simpleDataWithDefault` function. Therefore, for optional **Text**, **Date**, and **Boolean** launch parameters, you must guard the read with `lp.existsAndHasValue` inside a conditional expression.

## Step-by-step: Defaulting a blank launch parameter in `Create Values`

Rather than calling `lp.simpleData(...)` or `lp.stringParam(...)` scattered across multiple steps in your orchestration, normalize all optional launch parameters once in an initial **Create Values** step (for example, `InitializeLaunchParams`) right after the **Integration System Trigger** step.

Suppose your integration has an optional Text launch parameter `NominationSubmittedDate` that should default to today’s date (`YYYY-MM-DD`) when left blank at launch:

1.  Add a **Create Values** step named `InitializeLaunchParams`.
2.  Create a key named `submittedDate` of type `String`.
3.  In **Expression Builder**, toggle **Add Condition** on the `submittedDate` value to configure a conditional expression (**Concept: Adding Conditions in Expression Builder**):
    -   **Condition:**
        
        javascript
        
        ```
        lp.existsAndHasValue("NominationSubmittedDate")
        ```
        
    -   **If conditions are true:**
        
        javascript
        
        ```
        lp.stringParam("NominationSubmittedDate")
        ```
        
    -   **If conditions are false:**
        
        javascript
        
        ```
        date.today().toString()
        ```
        

Because Orchestrate only evaluates the **If conditions are true** expression when `lp.existsAndHasValue("NominationSubmittedDate")` returns `true`, `lp.stringParam("NominationSubmittedDate")` is never called when the launch parameter is blank. When the user leaves the prompt empty at launch, `data.InitializeLaunchParams.submittedDate` cleanly evaluates to today’s ISO date string.

### Applying the same guard to provider-scoped launch parameters

If your Integration System groups launch parameters under a specific service provider, use the two-argument overload of `lp.existsAndHasValue(provider: String, label: String)`:

-   **Condition:**
    
    javascript
    
    ```
    lp.existsAndHasValue("Custom_Service_Provider", "NominationSubmittedDate")
    ```
    
-   **If conditions are true:**
    
    javascript
    
    ```
    lp.stringParam("Custom_Service_Provider", "NominationSubmittedDate")
    ```
    
-   **If conditions are false:**
    
    javascript
    
    ```
    ""
    ```
    

### Guarding optional `Date` and `Instance Set Reference` launch parameters

Use the exact same `lp.existsAndHasValue` guard when reading optional **Date** launch parameters (`lp.dateParam("EffectiveDate")` when true; `date.today()` when false) or optional single-instance **Instance Set Reference** parameters (`lp.referenceData("Location_Prompt", "WID")` when true; `""` when false).

## How to verify blank and populated launch parameters in the tenant

1.  Save and deploy the updated orchestration to your tenant.
2.  Run **Launch / Schedule Integration** on the Integration System and leave the optional launch parameter (`NominationSubmittedDate`) completely blank. Confirm that the **Integration Event** completes without throwing `Parameter 'NominationSubmittedDate' is not a simple type launch parameter (Text, Number, Boolean, Date)` and that downstream steps receive the fallback default value from `data.InitializeLaunchParams.submittedDate`.
3.  Launch the integration a second time with an explicit value entered in the prompt (such as `2026-09-21`) and verify in **Orchestration Builder Logs** (or via **Debug Step** on `InitializeLaunchParams`) that `lp.existsAndHasValue` evaluates to `true` and passes your entered value through unchanged.

## Sources checked

-   [Reference: Lp Global Functions](https://developer.workday.com/documentation/GUID-00349403-f028-4e53-9a12-b095a8b3cf14)
-   [Concept: Adding Conditions in Expression Builder](https://developer.workday.com/documentation/GUID-5852a5b2-389d-4d44-b66f-78cab4544d65)
-   [Reference: Create Values](https://developer.workday.com/documentation/GUID-c310de5e-1e37-4ca6-bca3-52033d7ccb18)
-   [Reference: Date Global Functions](https://developer.workday.com/documentation/GUID-bdc8ad72-6dad-423d-978e-2838fc44d47d)
-   [Creating Integrations Using Workday Orchestrate: Orchestration Data Access](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-orchestrate/orchestration-data-access.html)

## Related guides

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

-   [### Resolving ‘\[StepException\] requirement failed: Input lists must be of the same size’ in createReferenceList The two-list overload InstanceRef.createReferenceList(idTypes: StringList, values: StringList) pairs idTypes\[i\] with values\[i\] and requires equal list lengths. Use the single-String overload InstanceRef.createReferenceList(idTypes: String, values: StringList) when all IDs share one type.](https://kiweely.com/guides/workday-orchestrate-createreferencelist-input-lists-same-size)
-   [### Logging in Workday Orchestrate: Log, Log to File, Add Integration Message and verbose logging The Log step writes to the app logs on the Developer Site, kept 30 days. Add Integration Message writes to the integration event in the tenant. Log to File builds a named CSV log you attach with Store Document. Verbose logging is a time-limited REST switch for troubleshooting.](https://kiweely.com/guides/workday-orchestrate-logging)
-   [### Branch on Conditions outputs must match: fixing Enable outputs, and when to use Continue on Conditions instead With Enable outputs on, every IF and ELSE branch must hand on the same output names and data types, because later steps read one output from the branch step. End each branch with a Create Values step setting the same keys, or use Continue on Conditions when a path should stop.](https://kiweely.com/guides/workday-orchestrate-branch-outputs-must-match)
-   [### How do I debug a Workday Orchestrate orchestration that shows success but some steps failed? A run can look successful because an unsuccessful HTTP response is not a failure unless a retry policy defines a success range, and an error handler set to Conditional Outputs lets the run carry on. Read the run’s per-process stepsFailed, not the status.](https://kiweely.com/guides/orchestrate-errors)

### More guides on Orchestrate

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

-   [Storing and Migrating External Client CredStore OAuth Credentials and Masked Integration Attributes in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-migrate-external-client-credstore-secrets)
-   [JSONPath Logical Filter Expressions and Wildcard XPaths in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-jsonpath-logical-filters-xpath-wildcards)
-   [Preventing Duplicate Records on Orchestration Rerun and Concurrent Webhook Triggers in Workday](https://kiweely.com/guides/workday-orchestrate-idempotency-concurrent-webhooks-duplicates)
-   [Reading the HTTP Response Content-Type Header in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-http-response-content-type-header)
-   [Transforming dynamic-key JSON to CSV and grouping flat CSV rows into nested JSON in Orchestrate](https://kiweely.com/guides/workday-orchestrate-dynamic-json-keys-to-csv-grouped-json)
-   [Custom CSV formatting in Workday Orchestrate: Windows CRLF line endings, title rows, and skipping preamble lines](https://kiweely.com/guides/workday-orchestrate-csv-crlf-title-row-skip-header-lines)
-   [Fixing ‘Fast forwarding to correct position’ and 45-minute timeouts in Orchestrate batchLoop](https://kiweely.com/guides/workday-orchestrate-batchloop-paginatedget-fast-forwarding-timeout)
-   [Overcoming ‘Message length should be lesser than 1MB in size’ and ‘Orchestration is too large to be saved’](https://kiweely.com/guides/workday-orchestrate-1mb-message-limit-too-large-to-save)

### From the blog on Orchestrate

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

-   [Why Workday Studio Remains Essential in an Orchestrate World](https://kiweely.com/blog/why-workday-studio-still-matters-with-orchestrate)
-   [Debugging Workday Extend apps and orchestrations in kiweely](https://kiweely.com/blog/debugging-workday-extend-apps-orchestrations-kiweely)
-   [Kiweely Roots vs Workday EIB, Studio, and Orchestrate](https://kiweely.com/blog/kiweely-roots-vs-workday-eib-studio-orchestrate)

## 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.
