Skip to main content

Action Source Definitions

Action sources are used to define and manage the origin of main actions within the system. These definitions enable meaningful grouping and restriction of actions based on their associated business processes.

Action source definitions provide an essential structure for traceability, reporting, and administrative control.

Role of Action Sources in the System​

  • Grouping: Actions are categorized by their sources to create an organized structure.
  • Sub-Action Type Restriction: Only specific action types can be selected based on the defined action source.
  • Module Restriction: An action source can be restricted to certain modules only.
  • Parent-Child Relationship: Action sources can be linked hierarchically to form a nested structure.

This structure increases control and usability in expanding systems.

Action Source Definition Process​

Action sources are defined using specific parameters such as Code, Name, Description, Parent Source, Action Types, and Modules.

Action Source Definition Screen​

This screen allows users to define a new action source or update an existing one. It can be accessed via the Action Sources list.

Core Fields​

  • Code:
    A unique identifier for each action source.

  • Name:
    A short and meaningful title for the action source.

  • Description:
    (Optional) Explains the purpose or scope of the action source.

  • Parent Source:
    This source can be linked to another action source as its parent.

    • Note: A source cannot select itself or its own child as a parent.

  • Allowed Action Types:
    Defines which action types are permitted in sub-actions.

    • If left blank, all action types will be available.

  • Allowed Modules:
    Limits the use of this source to specific modules.

    • If left blank, it will be available in all modules.

Authorization and Access Control​

Only authorized users can create, update, or delete action source definitions.

Permission Roles​

  • Create: Allows adding a new action source definition.
  • Update: Allows modifying existing definitions.
  • Delete: Allows removing unused definitions from the system.
  • Report: Allows generating reports based on action sources.

Warnings and Error Messages​

  • Duplicate Code: Two different action sources cannot share the same code.
  • Invalid Parent Source: A source cannot assign itself or one of its children as its parent.
  • Restricted Visibility: If action types or modules are selected, the source will only be visible where applicable.
  • Permission Error: The operation cannot proceed if the user lacks sufficient rights.

User Tips and Best Practices​

1. Define Hierarchical Action Sources​

Use parent-child relationships to reflect business processes accurately.

Best Practices:

  • Create parent sources for general categories (e.g., Quality Management).
  • Link detailed sources under parents (e.g., Internal Audit, Corrective Action).

2. Apply Action Type and Module Restrictions Strategically​

Use restrictions only where necessary to avoid unnecessary complexity.

Best Practices:

  • Leave these fields blank if the source should be available system-wide.
  • Use module selection only when the source is specific to certain modules.

Frequently Asked Questions​

Can I define two sources with the same code?​

No. Codes must be unique across the system.

Can I select my own record as the parent source?​

No. A source cannot be its own parent or a child of itself.

What happens if I don’t select any action type or module?​

The action source will be usable in all modules and with all action types.