> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/patterns/forms/form-creation-mode.md).

# Form - Creation mode

## Layout - Overview <a href="#id-604785" id="id-604785"></a>

### Page Title

<figure><img src="/files/v2UpdLwZv105kyCSqT8V" alt=""><figcaption><p>Exemple of a Page Title</p></figcaption></figure>

* **Visibility:** The page title is always visible on a creation form.
* **Content:**  "Add *\[object name]*" or "Create **\[object name]**"&#x20;
* **Navigation:** Include a backlink for easy return to the previous page, unless this is the first page in the hierarchy.
  * **Backlink Content:** "Back to *\[landing page title]*", where *\[landing page title]* is the exact title of the return page.
* **Additional Information:** [Learn more about Page Titles and Backlinks](/design/components/navigation/page-title.md).

### Save Bar

<figure><img src="/files/8vVEX4ePzcCZKHn072Cj" alt=""><figcaption><p>Save Bar in a creation mode form</p></figcaption></figure>

* **Visibility:** The Save Bar is always visible in creation mode.
* **Functionality:** Both '*Save*' and '*Cancel*' buttons are enabled when the Save Bar is visible.

## Form submission

### Success

*When users have successfully saved the form*

* **Single Object Creation:**
  * **Process:** After creating a single object, users are redirected to the previous page, accompanied by a success notification.
  * **Notification Content:** "\[Object name] added" or "\[Object name] created".
* **Multiple Object Creation:**
  * **Process:** After saving the form, users have the option to create another object.
  * **Notification:** Display a success alert with options for additional actions.

<figure><img src="/files/3nt5wyiwPX1CLUEkAKxC" alt="" width="375"><figcaption><p>Exemple of a success alert when creating multiple objects in a row</p></figcaption></figure>

### Cancel <a href="#id-54dd8b" id="id-54dd8b"></a>

*When users clicks Cancel or the backlink without saving form*

* **Form pristine (unmodified)** : no modal + back to previous page (in the hierarchy)
* **Form dirty:** *`Prompt-before-leave`* + back to previous page (in the hierarchy)

<figure><img src="/files/OT1Ia8DToYNC6LjMDtlv" alt="" width="375"><figcaption><p>exemple of a Prompt Before Leave</p></figcaption></figure>

### Prevent changes while submission

* **Processing Time:** The form becomes read-only during backend processing to prevent changes.

## Take aways

{% hint style="success" %} <mark style="color:green;">**Do**</mark>

* Respect Layout guidelines
* Refer to Stepper Form guidelines for long and/or complex forms
* Refer to [Error Management](/design/patterns/forms/error-management.md) page to guide users through the whole form experience
  {% endhint %}

{% hint style="danger" %} <mark style="color:red;">**Don't**</mark>

* Avoid custom behaviors: keep form creation consistent across all products.
  {% 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 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://design.mirakl.com/design/patterns/forms/form-creation-mode.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.