> For the complete documentation index, see [llms.txt](https://docs.work-relay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.work-relay.com/processes/process-steps/process-step-settings/properties.md).

# Properties

Steps have these properties:

* **Milestone** (view only) — used for some visual and ergonomic purposes. The milestone a step belongs to can be changed by moving a step (see [proper article](/processes/building-a-process/milestones.md)).
* **Name** (required) can be edited if necessary. It is shown everywhere steps are displayed (Progress component, Task Manager, Gantt Chart, Progress Dashboard, etc.). It is not necessary to give unique names to steps, but it is recommended.

![](/files/7765ebca1fe6a0b46e7f1ad3b8a43e214ab964a8)

* **API Name** (optional) can be used in different Actions where the user needs to know or set a step. Otherwise, the user needs to provide Step ID, which is not a good idea to hardcode. It can be specified in merge fields. Mouse over to see the help tooltip with restrictions for API name.

![](/files/a5fb53f0a6f63aad4ca19c24735a8edd52d90aa8)

* **Step type** — specifies a step assignment (whether a step should be proceeded by the system or not) and the type of proceeding. Manual steps can be proceeded to the next one by the default connector. A decision step can proceed to one of the steps connected by "Approve" and "Reject" connections.

![](/files/709496492a8efbffd1660e11079713aed77dfe33)

* **All Assignee must complete** checkbox (for non-system steps) — if this option is set, all assignees should proceed (or approve) a step to allow it to go further. If not checked, only one assignee's proceeding is needed. The same setting works for steps and [responsibilities](/processes/building-a-process/responsibilities-swimlanes.md) assigned to multiple users, as well as for step/responsibility Assign types representing multiple users (Field, Group, Queue, etc.).
  * When you check only "All Assignees must approve", the step will be proceeded with rejection as soon as at least one rejection is received and will be Approved only if all assignees Approved.
  * When you check "All Assignees must approve" and "or reject", the step will be active until all assignees approve or reject. It will be Approved if all assignees approved.

![](/files/e13258c4a8bf74436eed2e80ce53d0d165312c59)

* **Require Comments** checkbox (for non-system steps) — if checked, the user cannot proceed further without text in the comment. For Decision steps, there are two separate checkboxes for Approve and Reject types of proceeding:

![](/files/2f28139a2ca34f1423aae4e6e2d19da97a6b8d1a)

![](/files/e4f736f048a3b42ab7053335d0a784f425e55113)

* **Require Time Entry** — Starting release 8.2, users must report time to proceed, approve, or reject the step. If this option is checked, the system shows a warning when the user tries to proceed, approve, or reject a step without [reporting time](/functional/process-progress-component/progress-component-tabs/time.md) first.

  If the user restarts a step with required time entry (changes step, restarts branch, restarts a workflow), they must add a new time entry to this step even if time was already reported. New activation of a step requires a new time report to complete it.

![](/files/df405502f3edb2d3def4ebd588f2d88bef8fdf4c)

* **Autocomplete Behavior** (for Decision steps only) — specifies what the system should do with the step if it is escalated to the system. This property can be set to "Approve", "Reject", or "Formula". In the latter case, the user can build a formula that returns "Approve" or "Reject" depending on necessary conditions and logic.

![](/files/1588236cd6b4f4f62011f777f71d5a505858c999)

Click the Formula input field (10) to open a Formula Picker popup:

![](/files/fffd0c2c8f7b4f4a010947d3b0f74f1b7c4dc77b)

* **Processing Frequency** — select how often system jobs will try to make necessary actions on started instances of this process. The default value is about 10 minutes. If a process is too heavy or does not require immediate reactions, it is better to set a higher value. Set it to "Never" if you plan to start jobs manually:

![](/files/be30489826a0a92e049c372745a351a01a995e53)

* **Priority** field type — a predefined picklist of available priority values: Low, Normal, High, and Critical.

  Starting release 7.1, **Expression** is available. It allows priority to be set dynamically with a formula expression:

![](/files/49a92f9eb2b70300ac01ebcd63ddf6ddc489531e)

![](/files/b0908b42a6a0de5132beffed581555ab737a39b2)

* **Description** — populate for your assistance, optionally:

![](/files/0c7c0b78c3ae90f16c6d6155bdffef4c910b5b6c)