Troubleshooting Business Rules and Application Settings

Creation date: 10/7/2026 3:03 PM Updated: 10/7/2026 3:04 PM behavior process rules

Overview

When a user is unable to perform an action, cannot access a specific option, or the application is not behaving as expected, the issue is often related to either the Workflow configuration or a Global Setting.

The Workflow generally controls user-specific and process-specific behavior, such as who can submit or approve documents and what accounts, Distribution Codes, or items they are allowed to use.

Global Settings generally control application-wide behavior and determine how Microix functions based on the organization's requirements.

A good troubleshooting approach is to review the Workflow first, then review the applicable Global Settings if the behavior affects users across the application.

Review the Workflow

The Workflow should normally be the first place to review when an issue affects a specific user, group of users, document type, or approval process.

Workflow configuration determines who can perform certain actions and what they are allowed to access.

Common Workflow settings include:

Requester assignments – Determines which users can create and submit documents through the Workflow.
Approver assignments – Determines which users are responsible for approving documents at each approval level.
Approval routing – Controls how documents move through the approval process.
Account restrictions – Determines which GL accounts, departments, funds, programs, locations, or other accounting segments users can access.
Distribution Code restrictions – Determines which Distribution Codes are available within the Workflow.
Item restrictions – Determines which configured items are available to users.
Budget rules – Certain budget controls can be enabled or disabled by Workflow.
Submission restrictions – Some Workflow settings can prevent a requester from submitting a document when specific conditions are not met.

If an issue affects only certain users or one Workflow, review the Workflow configuration before changing any Global Settings.

Example

If one requester cannot select a specific account, but another requester can, review the user's Workflow and account restrictions first. By default, all users within the same workflow are restricted to the same accounts unless different restriction IDs are configured.

Review Global Settings

Global Settings control application behavior that generally applies across the organization rather than to a specific Workflow.

These settings allow each organization to configure Microix based on its operational requirements and internal policies.

Examples of Global Settings include:

Receiving requirements.
Vendor requirements.
Document variance tolerances.
Two-way or three-way matching requirements.
Whether attachments can be added after a document is transferred to MIP.
Document approval and processing behavior.
Authentication and MFA-related options.
Application-wide defaults and feature behavior.

If the same behavior affects all or most users regardless of Workflow, review the applicable Global Setting.

Recommended Troubleshooting Steps

When a business rule appears to be preventing an action:

Identify the user, document type, Workflow, and current approval level.
Review the applicable Workflow configuration.
Check requester and approver assignments.
Review any account, Distribution Code, item, or other restrictions.
Determine whether the issue affects only that Workflow or occurs throughout the application.
If the behavior is application-wide, review the applicable Global Setting.
After making a change, retest using the same user and Workflow to confirm the expected behavior.

Quick Reference

Workflow = Who can do what within a specific business process.

Use the Workflow when troubleshooting user assignments, approval routing, account restrictions, Distribution Codes, items, and other process-specific rules.

Global Settings = How the application behaves for the organization as a whole.

Use Global Settings when troubleshooting application-wide behavior, default rules, feature settings, and organizational policies.