> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/admin/8.7/updateprocessdata-workflow-application.md).

# UPDATEPROCESSDATA Workflow Application

## Overview

The **UPDATEPROCESSDATA** workflow application allows you to update process data associated with a request. It provides a simple solution for inter-process communications.

## Using default and other parameters

### Request

The required parameter is `REQUEST_ID:` IN parameter, numeric value. This parameter must contain a valid request ID.

### Activity

The optional parameters are the process data to update (the parameter name in the processing data name). You must define those parameters on the corresponding action parameters.

To create a workflow action using UPDATEPROCESSDATA, use the following parameters:

* `REQUEST_ID` send value of:
  * Data: `REQUEST_ID _UPDATE`
* `AMOUNT` send value of:
  * Data: `AMOUNT_UPDATE`

{% hint style="info" %}
You may have to add an exception management to handle possible errors (e.g. invalid request ID).
{% endhint %}

#### 📌 Example

If you want to update `AMOUNT` with the value of the `AMOUNT_UPDATE` process data, the request ID to update is stored in a `REQUEST_ID_UPDATE` process data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.workflowgen.com/admin/8.7/updateprocessdata-workflow-application.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.