# Status Conditions

### 1. Introduction

This release improves the Conditions field implementation for statuses configured under the `Status` section of any process on the Unifize platform. This would simplify configuring status behaviors based on specific user roles (e.g., creator/owner) within any process and enable organizations to implement more context-aware, dynamic status management across their workflows.

### **2. How the update looks on the platform**

To check how this update works in real time on the platform:

1. Navigate to the **Manage view**, then open any **process**.
2. Inside the process, go to **Status** → **Settings** → **Conditions**.
3. At the top, choose one of: **Hide until condition met**, **Enable until condition met**, or **Disable until condition met**.
4. Click **+ Add New Condition**.
   * **Condition:** User (Current user)
   * **Qualifier:** `is creator` *or* `is owner` (Choose either one)
   * **Behavior:** select as needed (e.g., **shown**)
5. (Optional) Use **+ Add condition (AND)** to add another condition.
6. Click **Save Changes**.

### 3. How it looks for the end users

With this update, Conditions can be configured so that end-user behavior is determined when the User (Current user) is the creator or is the owner (Qualifier). Accordingly, the set Behavior state will be applied if the condition is met. If the condition is not met, the configuration will make the setting fall back to the default condition state.

Here’s how the update will work in all three default condition states:

#### 3.1 Hide until condition met

* If the current user meets the Qualifier of being the creator or owner of the process or record for which the condition is configured, the configured Behavior is applied to the configured status (e.g., show status, disable or lock status, or hide status, as configured).
* If the current user does not meet the Qualifier, the configured status remains hidden.

#### 3.2 Disable until condition met

* If the current user meets the Qualifier of being the creator or the owner of the process or the record for which the condition is configured, the configured Behavior is applied to the configured status.
* If the current user does not meet the Qualifier, the configured status is visible but disabled/locked.

#### 3.3 Enable until condition met

* If the current user meets the Qualifier, the configured Behavior is applied to the configured status.
* If the current user does not meet the Qualifier, the configured status remains visible and enabled.

### 4. Previous vs Current behavior

| Area                 | Previous                                                                   | Current                                                                                                                             |
| -------------------- | -------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Condition evaluation | Implementation for `is creator` / `is owner` Qualifiers was not available. | Implementation for `is creator` and `is owner`  Qualifiers is now available and can be configured based on the required behaviours. |
| UI reflection        | Status did not reflect above configured Behavior for end users             | Status reflects above configured Behavior for eligible users.                                                                       |

### 5. Use case of this update

* **Reduce noise for collaborators:** Hide or disable the configured status for participants who are not the creator/owner, so only eligible users see or can act on it, and accidental actions can be avoided.
* **Clear responsibility & handoffs:** Make it explicit who is expected to advance a record by showing/enabling the **configured status** only when the current user is the record's creator or owner.
* **Safe rollout of additional statuses:** When introducing an additional status, show/enable it only for the creator/owner while you validate the workflow, then broaden visibility later if needed.


---

# 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.unifize.com/release-notes/october-2025/status-conditions.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.