# Microflow Version Settings

In ONEWEB, **Microflows are versioned automatically** whenever a new **snapshot** or **patch** is created.\
As a result, multiple versions of the same Microflow may exist at the same time.

The **Microflow Version Settings** feature in Page Designer allows users to control **which version of a Microflow is invoked from a page**, ensuring stability and flexibility across application updates.

***

### Why Microflow Version Management Is Important

Microflow versioning helps:

* Maintain **backward compatibility**
* Prevent breaking UI pages when Microflows change
* Support gradual rollout of new logic
* Allow testing against specific Microflow versions
* Control behavior across **SIT / UAT / PROD** environments

Without version control, changes in Microflows could unintentionally affect existing pages.

***

### Access Microflow Version Settings

Microflow version selection is configured from the **Microflow Settings screen inside Page Designer**, where users can choose how Microflows are resolved when called from a page.

***

### Version Selection Options

ONEWEB provides **two ways** to manage Microflow versions:

***

### Option 1: Use Latest Version (Global Setting)

Users can configure Microflows to **always use the latest available version** automatically.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FF9pnklljiosBblcwSrCi%2Fimage.png?alt=media&#x26;token=a8437198-4b20-4fe7-ae91-e4bfd96f5b2d" alt=""><figcaption></figcaption></figure>

#### When to Use This Option

* Rapid development and frequent iteration
* Non‑critical applications
* Early development or testing phases

#### Consideration

* Changes in Microflow logic immediately affect all pages calling it

***

### Option 2: Set Microflow Version Per Page Call

Users can explicitly select a **specific Microflow version** for each Microflow invocation from a page.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2Fi5uBapGFB2Lf3GhLw5mm%2Fimage.png?alt=media&#x26;token=8a89b293-dc89-4008-b058-088cd1bf3f76" alt=""><figcaption></figcaption></figure>

#### When to Use This Option

* Production‑critical pages
* Backward compatibility requirements
* Controlled rollout of new Microflow logic
* Hotfix or patch isolation
* Regulatory or audit‑sensitive applications

***

### How Version Selection Works at Runtime

* If **Latest** is selected:
  * The page always calls the newest Microflow version
* If a **Specific Version** is selected:
  * The page always calls that exact version
  * Even if newer Microflow versions are published later

This ensures predictable behavior in production environments.

***

### Design Perspective

As part of **enterprise best practices**:

* Use **Latest** in Development and early testing
* Pin **specific versions** in UAT and Production
* Document Microflow versions used by critical pages
* Test new Microflow versions before switching pages to “Latest”
* Combine Microflow Version Settings with **Environment Variables** for controlled deployments

Microflow Version Settings provide **strong governance and stability** for evolving applications.


---

# Agent Instructions: 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:

```
GET https://docs.onewebstack.com/oneweb-platform-th/building-apps/ui-page-designer/ux-ui-components/pages/page-features/microflow-version-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.