> This page is for Itential Platform Cloud.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Task input query syntax deprecated

> Notice that some of the task input query syntax for accessing a property, introduced in the Platform Cloud May 2026 release, is deprecated in the Platform Cloud November 2026 release and will be removed in an upcoming release.

Starting in November 2026, task input queries and the [query task](/itential-cloud/studio/tasks/reference/query) share one syntax. As a result, the November 2026 release deprecates some of the syntax for accessing a property in a task input query. An upcoming release removes the deprecated syntax. Until then, task input queries that use it continue to run as before.

## What's changing

The shared syntax adds support for data filtering and manipulation to task input queries via filters, helper functions, and other added syntax. Most existing task input queries work the same way as before. The November 2026 release deprecates only what the shared syntax reads differently.

The following syntax for accessing a property is deprecated:

| Deprecated syntax                                                                                                                                                                                                | Previous behavior                    | Replacement              |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | ------------------------ |
| `["device_name"]` Quoted bracket notation, single or double quotes                                                                                                                                               | Accesses the property `device_name`. | `.device_name`           |
| `[*]` for property access                                                                                                                                                                                        | Accesses a property named `*`.       | `.*`                     |
| `[a=b]` An unquoted bracket-notation key that contains a special character reserved by the query library for query syntax (`:`, `\|`, `?`, `~`, `=`, `!=`, `<`, `>`, `<=`, `&`, `(`, `)`, `[`, `]`, `{`, or `}`) | Accesses the property `a=b`.         | `:getLiteral(a=b)`       |
| A dot-notation key that contains a special character reserved by the query library for query syntax (`:`, `\|`, `?`, `(`, `[`, or `{`), such as `region?id`                                                      | Accesses the property `region?id`.   | `:getLiteral(region?id)` |

The `:getLiteral()` helper function is new in the November 2026 release. It reads its argument as plain text, which makes it the replacement for any key that contains a special character. For more information, see [Query a key that contains special characters](/itential-cloud/studio/tasks/reference/query#query-a-key-that-contains-special-characters).

The following example shows a task input query that uses deprecated syntax and its replacement.

Deprecated:

```js
response.body["device_name"]
response.body["device.name"]
```

Replacement:

```js
response.body.device_name
response.body.:getLiteral(device.name)
```

The rest of the existing syntax isn't deprecated. The `[*]` wildcard is supported, and only `[*]` used to access a property named `*` is deprecated. Dot notation still works for a key that doesn't contain a special character, such as `region_id`. Array indexes, such as `devices[0]`, also work as before.

In the shared syntax, `["device_name"]` accesses a property named `"device_name"`, including the quotation marks, and `[*]` is a wildcard that returns every value in an object or every element in an array. Starting in the November 2026 release, the **Update** action in Studio converts deprecated syntax to the syntax in the Replacement column, so the query returns the same value in the shared syntax. For more information, see [What should I do?](#what-should-i-do). After Platform removes the deprecated syntax, task input queries that you haven't updated return a different value or fail.

## Timeline

| Release                              | Change                                                                                                                                                                                                                      |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Platform Cloud November 2026 release | The deprecated syntax still works. Studio displays a warning on each affected input field and a workflow validation warning when you save or import the workflow. Any task input query you add uses the shared syntax only. |
| Upcoming release                     | Platform removes support for the deprecated syntax.                                                                                                                                                                         |

## What should I do?

Update each affected task input query before Platform removes the syntax. Studio displays a warning next to each input field that has a query with deprecated syntax, and an **Update** action next to the warning. The action does the following:

* Converts only the deprecated syntax in the query and leaves the rest of the query unchanged.
* Preserves the value that a matching query returns.
* Clears the warning for that input field.

> **Warning**
>
> A task input query that failed before the November 2026 release can succeed after the update. For example, when `devices` is an array, `devices[*]` previously took the task's error transition because the array has no property named `*`. The updated query `devices.*` returns an empty array instead because this is the new array pluck syntax, so the task takes its success transition. Review any task whose input query previously failed due to attempting to access a property from an array.

The update applies to one input field at a time. The change isn't saved until you save the workflow. If you leave the workflow without saving, Studio discards the update and displays the warning again.

> **Warning**
>
> You can't revert an update to the previous syntax. Back up your workflows before you update task input queries.

## Related resources

* For more information about `:getLiteral()`, see [Query a key that contains special characters](/itential-cloud/studio/tasks/reference/query#query-a-key-that-contains-special-characters).
* For more information about task input queries, see [Task input query](/itential-cloud/studio/workflows/tasks/configure-manage-tasks#task-input-query).