> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/configure-forced-values-and-parameters.md).

# Configure forced values and parameters

Forced values let you fill work order fields automatically when an email creates a work order.

You can use fixed text or dynamic parameters from the email.

### What you can set

You can use forced values for common work order fields such as:

* status and work type
* priority and SLA
* work descriptions and references
* relation details and invoice details
* object fields and free fields

### Dynamic parameters

Parameters insert values from the email into the work order.

Common examples are:

* `{subject}`
* `{sender_address}`
* `{email_display_name}`
* `{mail_content}`
* `{time_mail_process}`
* `{date_mail_process_dmy}`
* `{date_mail_process_ymd}`
* `{obj_code}`

### Add forced values

{% stepper %}
{% step %}

### Open a configuration

Open the mail configuration you want to edit.
{% endstep %}

{% step %}

### Open Forced values

Go to the **Forced values** section or tab.
{% endstep %}

{% step %}

### Add a field

Choose the field you want to populate.
{% endstep %}

{% step %}

### Enter the value

Add fixed text, a parameter, or a combination of both.
{% endstep %}

{% step %}

### Save and test

Save the configuration and test the result with a sample email.
{% endstep %}
{% endstepper %}

### Good examples

* set the work description to `{subject}`
* store the sender address in a remark field
* combine static text and dynamic values in one reference

### Frequently asked questions

<details>

<summary>Can I use multiple parameters in one value?</summary>

Yes.

You can combine parameters with static text.

</details>

<details>

<summary>What if a parameter is empty?</summary>

That part is inserted as an empty value.

</details>

<details>

<summary>Do forced values work with custom fields?</summary>

Yes, if those fields are available in the configuration.

</details>

### Related topics

* [**Create and manage mail configurations**](/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/create-and-manage-mail-configurations.md)
* [**Parse email content with regex and advanced options**](/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/parse-email-content-with-regex-and-advanced-options.md)
* [**Understand matching rules and sender types**](/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/understand-matching-rules-and-sender-types.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/configure-forced-values-and-parameters.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.