> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/frequently-asked-questions/possible-to-modify-field-constraints-for-application-name-of-mu.md).

# Possible to Modify Field Constraints for "Application Name" of Murano Application Deployment?

## Problem

* A Heat template has been used to create a Murano application.
* Upon deployment of the application, an **Application Name** field is presented.
* It's desired to modify the field constraints, such as requiring all lower-case (as doable for other parameters in the Heat template).

## Environment

* Platform9 Managed OpenStack - All Versions
* Murano

## Answer

**No**, it is not possible to modify the constraints for the **Application Name** field, nor can it be validated by Heat as the application name is not included as part of the template parameters in the API payload. For example:

1. Request URL:

https\://\_\_CLOUD\_FQDN\_\_/murano/v1/environments/\_\_ENV\_ID\_\_/services 2. Request Method:

POST 3. Status Code:

200 OK

**Payload**:

{% tabs %}
{% tab title="None" %}

```none
{?: {classVersion: "0.0.0", package: "io.murano.apps.generated.Apachehttpserver",…}, name: "apache",…}  ?: {classVersion: "0.0.0", package: "io.murano.apps.generated.Apachehttpserver",…}  name: "[application-name]"  templateParameters: {flavor: "[flavor]", image: "[image-id]", key_name: "[ssh-key]",…}
```

{% endtab %}
{% endtabs %}


---

# 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://platform9.com/kb/pmo/frequently-asked-questions/possible-to-modify-field-constraints-for-application-name-of-mu.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.