> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/xcover-elements/client-integration/element-signals/update-signal.md).

# Update signal

XCE allows Partners to load the widget in a state other than the default with custom attributes or trigger events programmatically using the `update` signal.

This type of features work on an as needed basis for each element, which is explained below.

## Using `update` signal

The `update` signal allows you to programmatically trigger our element events.

This is useful for specific customer actions or contexts during their journey that kept them away from any direct element interaction and still being able to trigger the desired event.

#### isError

To programmatically set the element to an error state call `signalLayer.push()` with `update` as the value for the `signal` property and add the input value in the `isError` property as in the following example:

<pre class="language-javascript"><code class="lang-javascript">window.signalLayer.push({
  signal: "update",
  element: "xce-protection-offer",
  isError: true,
<strong>});
</strong></code></pre>

{% hint style="info" %}
This is similar to `dispatchEvent()` difference being we are using XCE Signals instead.
{% endhint %}


---

# 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://partner-docs.covergenius.com/xcover-elements/client-integration/element-signals/update-signal.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.