Skip to main content

Action Priority Definitions

Action priority is a structure that enables categorizing actions based on their level of importance. This allows actions to be grouped more meaningfully in reports.

Action priority provides the ability to prioritize actions based on the criticality of business processes, especially in environments where many actions are being tracked.

Role of Action Priority in Business Processes​

Action priorities are definitions selectable in sub-actions that determine priority levels in alignment with the organization’s strategic goals.

  • Classification: Actions are categorized by priority levels such as "High Priority", "Medium Priority", etc.
  • Color Coding: Priorities can be visually distinguished by assigned colors.
  • Icon Representation: Each priority can be represented by a specific icon.
  • Reporting: Priority-based reports can be generated.

Action priorities offer valuable filtering mechanisms for decision-making at the management level.

Action Priority Definition Process​

Action priorities are defined in the system using the following parameters: Code, Name, Description, Color, and Icon.

Action Priority Definition Screen​

This screen is used to define a new action priority or to update an existing one. It can be accessed via the Action Priority Management module.

Core Fields​

  • Code:
    Must be unique for each action priority.

  • Name:
    Describes the priority. Example: "High Priority"

  • Description:
    (Optional) Explains the scope or intent of the priority.

  • Color Definition:
    Color can be specified in RGB format. Recommended for visual consistency.

  • Icon (Image File):
    An icon can be uploaded to visually represent the priority.

Authorization and Access Control​

Only authorized users should be able to create or edit action priorities.

Permission Roles​

  • Create: Allows defining a new action priority.
  • Edit: Allows updating existing priorities.
  • Delete: Allows removing unused priorities from the system.
  • Report: Grants access to reports based on priorities.

Warnings and Error Messages​

  • Unique Code Constraint: Multiple priorities cannot be defined with the same code.
  • Invalid Color Format: The color must be a valid RGB string.
  • Status-Based Listing: Only "Active" action priorities are listed on data entry screens.
  • Missing Fields Warning: Users must be notified if required fields are left empty.

User Tips and Best Practices​

1. Clearly Define Priority Categories​

Create custom levels based on your organization (e.g., Critical, High, Medium, Low).

Best Practices:

  • Use short and descriptive codes (e.g., CRIT, HIGH).
  • Maintain consistent descriptions.
  • Match colors with logical groupings (e.g., red = critical).

2. Choose Icons Meaningfully​

Visual cues enhance user experience.

Best Practices:

  • Prefer simple and universal icons.
  • Avoid using very similar icons for different priorities.

Frequently Asked Questions​

Can I define multiple priorities with the same code?​

No. The code must be unique across the system.

What happens if I don’t define a color?​

No default color is applied. The visual presentation may be incomplete.

Is the icon required?​

No, defining an icon is optional. However, it is recommended for visual consistency.