Skip to main content
All CollectionsAssignments
Using Assignment Definitions
Using Assignment Definitions

This article will explain how to setup and use Assignment Definitions for your Organization.

Logan Bowlby avatar
Written by Logan Bowlby
Updated over 4 months ago

Explore Asset Management with Mobaro: Assignment Definitions are a feature of our Asset Management add-on package. To learn more or to integrate this functionality into your organization, contact our team at support@mobaro.com.

Overview

Assignment Definitions allow you to go beyond the standard, built-in Assignment flows within Mobaro by introducing custom states, priorities, and categories that can be visible exclusively to specific User Groups or to the entire Organization.

Users must be Super Users or have the following Role to manage Assignment Definitions:

  • Organization: Administrate


What are Assignment Definitions?

Currently, a default Assignment within Mobaro is limited to the following settings:

  • Priorities: Low or High

  • Categories: Includes all existing Assignment Categories

  • States: Created, Started, and Finished

With the new Assignment Definitions feature, you are able to expand upon and customize these settings uniquely for each definition, ensuring they are relevant only to the User Groups specified.


Using Custom Properties

When creating an Assignment Definition, you will be able to create custom:

  • States

  • Categories

  • Priorities

  • Creation and Delegation configurations

It is important to understand how property interacts with each other and the system as a whole.


Custom States

When creating custom states, you will be able to create three different types of states:

  1. Initial State:

    • Definition: The Initial state is a unique starting point for an Assignment Definition.

    • Requirement: Only one state can be designated as the Initial state in any given workflow or process.

    • Behavior: When the process or workflow is initiated, it automatically begins at this Initial state.

  2. Step (Intermediate States):

    • Definition: Steps are optional states that exist between the Initial and Final states in a process.

    • Flexibility: Including steps allows for the addition of complexity and granularity in the workflow, accommodating various activities, decisions, or interactions that occur after the start but before the process concludes.

    • Purpose: Steps can be used to manage and track progress through the process, offering checkpoints or milestones that guide the workflow toward its conclusion.

  3. Final State:

    • Definition: The Final state marks the conclusion of the Assignment Definition. It represents the endpoint(s) that can be reached once all necessary conditions or steps have been fulfilled.

    • Variability: It is possible and sometimes necessary to have more than one Final state.

    • Examples: Common examples of multiple Final states include scenarios like "Completed" or "Rejected."

Examples of some custom states workflows

Simple Work Order

Parts Request

Winter Work

Open

Request Submitted

Preparation

Awaiting Approval

Supplier Coordination

Execution

In Progress

Receiving/ Inspection

Safety Check

In Review

Inventory Update

Completion

Finalized

Part Delegation

Rejected


Custom Categories

In the system, there are two types of assignment categories that can be defined:

  1. Organization-defined Assignment Categories: These are set by the organization and are standard across the system. These are the categories utilized for default Assignments.

  2. Custom-created Assignment Categories: These categories are created for specific Assignment Definitions. They allow for flexibility in categorizing custom Assignment Definitions.

Unrelatedness of Similar Categories

Even if an Organization-defined category and a custom-created category share the same name, the system treats them as completely distinct entities. This means:

  • Separate Identification: Each category, regardless of its name, is recognized and treated separately based on its type (organization-defined or custom-created).

  • No Overlap or Merging: There is no automatic linking, merging, or relation between these categories, even if they have identical names.

  • Impact on Data Handling: This approach ensures that data sorting, filtering, and reporting are based on the specific type of category used, without confusion or overlap.

Note: Assignment categories defined by the organization and custom-created categories are treated as distinct, even if they share the same name. For example, an organization-defined 'Mechanical' category and a custom 'Mechanical' category will be recognized as separate entities by the system.

Assignment Category Options

  1. Use Organization-defined Categories:

    • Employ only the standard categories set by the organization.

  2. Use Custom-created Categories:

    • Opt for categories that you create on a per-Definition basis.

  3. Use Both:

    • Combine standard and custom categories for a broader approach.


Custom Priorities

Unlike the default Assignment's binary approach to priorities (Low vs. High), Assignment Definitions allow you to define your own, custom priorities on a per-definition basis.

When creating these custom priorities, keep in mind the following:

  • Critical for operation: if a custom priority is marked as Critical for operation, then the affected Location or Asset will be marked as Not ready for operation until the Assignment is finalized or moved to a non-Critical for operation priority level

    • This is a similar process to the default Assignment's High priority status.

  • Default: it is mandatory to mark one priority as the "Default" priority the Assignment will be placed in when initialized.


Creation and Delegation configurations

Assignment Definitions provide comprehensive control over the creation and delegation of each Assignment.

  • Who Can Create: Restrict Assignment creation to specific User Groups for each definition.

  • Who Can Be Assigned: Limit Assignment recipients based on designated User Groups.

  • Assignee Type Limitation: Specify if Assignments can be delegated to only Users, only User Groups, or both.

  • Assignment Flexibility: Define whether Assignments can be assigned to multiple or single Users and/or User Groups.

These configurations offer precise control over your Assignments, ensuring they are managed according to your specific needs.


How to configure Assignment Definitions

To create an Assignment Definition, follow these steps:

  1. Navigate to Configuration.

  2. Under the Assignments tab, click the Create button in the Assignment Definitions section.

  3. Under the Configuration tab, adjust any creation and delegation limits

  4. Under the States tab, click the Add State button

    1. You must create exactly one Initial state and at least one Final state.

  5. Under the Categories tab, select from the following:

    1. Choose to enable or disable the use of Organization-created Assignment Categories.

    2. Specify whether Users can select one or multiple Assignment Categories.

    3. Optionally add custom Assignment Categories by clicking the 'Add Category' button .

  6. Under the Priorities tab, optionally create custom priorities by clicking the Add Priority button .

    1. When creating custom priorities, you must dictate exactly one Default priority.

    2. Optionally designate one or more priorities as Critical for operation.

Did this answer your question?