Scheduled Jobs feature defines how system tasks are executed automatically without direct user interaction.

It represents a framework for running background processes that must be executed regularly, reliably, and in a controlled way, such as report generation, payroll exports, integrations, and automated workforce operations.

Instead of being triggered manually by users, these processes are configured once and then executed by the system based on defined schedules or explicit execution rules.

KEY COMPONENTS

Job
Defines an automated system task executed by the application.

Job Type
Defines the functional purpose and processing logic of a job.

Trigger
Defines when and how frequently a job is executed.

Job Run
Represents a single execution instance of a job, including its outcome.

Job Log
Stores informational, warning, and error messages generated during a job run.

Job File
Represents a file output generated during a job run..

PERMISSIONS

The following permissions control access to Scheduled Jobs:

JobsSetup

JobRunsView

CONFIGURATION

Scheduled Jobs are configured under the Administration module.

Navigate to Jobs to define:

• Which system processes are automated
• How they are parameterized
• Whether notifications are sent on success or failure

Navigate to Triggers to define when and how often jobs are executed.

Navigate to Job Runs to monitor execution results and access generated outputs (dev in progress)

ROSTER VIEW

Scheduled Jobs do not appear as standalone elements in the roster.

However, jobs that perform planning or state validation update roster data automatically. The roster always reflects the result of the latest successful job execution.

REPORTS

Scheduled Jobs automate report execution.

They ensure that reports are:

• Generated regularly without manual effort
• Produced with consistent parameters
• Delivered as files or email attachments

This allows reports to be reused directly in management workflows and external systems.

PAYROLL & INTEGRATION RESULTS

Scheduled Jobs act as a delivery mechanism for payroll and integration data.

They ensure that:

• Payroll export files are generated on time
• Integration outputs follow a stable structure
• Data is ready for consumption by external systems without manual preparation

MOBILE APPLICATION

Scheduled Jobs themselves are not configured in the mobile application.

Their outputs become visible in the mobile application only when the related reports or properties are enabled through standard mobile configuration parameters.

The Roles and Permissions feature defines how access and responsibility are managed in AristoTelos.
It controls who can perform which actions, on which entities, within which organizational scope, and during which time period.

This feature underpins all operational workflows, ensuring secure, consistent, and auditable behavior across planning, attendance, requests, reporting, and payroll processes.

Key Components

Permission Group
A subset of permissions within a role that applies only to specific employees based on subordinate or excluded role rules.

Assignment Scope
The organizational level at which a role applies. Scope determines where permissions are effective.

Validity
A time interval defining when a role assignment is active and which data periods the permissions apply to.

User Role
A concrete assignment of a role to a user, including scope and validity.

Role Delegation
A temporary transfer of selected permissions from one employee to another for a defined period.

Subordinate Roles
A rule limiting permissions to employees who have specific roles.

Excluded Roles
A rule preventing permissions from applying to employees with specified roles, overriding subordinate role logic.

Delegable Permission
A permission explicitly allowed to be transferred through role delegation.

Configuration

Roles and permissions are configured centrally to reflect organizational structure and rules.

Configuration allows organizations to:

• define roles aligned with real responsibilities
• assign roles globally or to specific organizational units
• restrict where and to whom permissions apply
• enable or disable permission delegation
• manage future and temporary role assignments

Once configured, permissions are enforced automatically across all workflows.

Roster View

Roles and permissions directly control roster behavior.

They determine:

• which employees are visible
• whether shifts can be viewed, edited, or published
• who can create, process, or approve requests
• access to historical and future rosters

The roster dynamically adapts to role, scope, and validity, preventing unauthorized actions by design.

Permissions

(How control is enforced)

Permissions are evaluated dynamically based on:

• assigned roles
• organizational hierarchy
• validity intervals
• delegation rules

The system enforces:

• strict separation of self vs others actions
• hierarchy-aware access control
• controlled handling of future and historical data
• predictable and safe delegation behavior

This ensures consistent and auditable permission enforcement across the system.

Entitlements feature defines how employee time-off and activity entitlements are structured, allocated, and consumed within the system.

It determines which entitlement categories exist, how they behave, which employees receive them, and how usage is recorded over time.

KEY COMPONENTS

• Entitlement Type
  Defines the rules, units, eligibility, and activities that can consume an entitlement.
• Entitlement
  Represents an employee-specific allocation of a defined Entitlement Type.
• Entitlement State
  Tracks entitlement usage and the remaining balance over time.

PERMISSIONS

There are several available permissions for configuring entitlements:

1. EmployeeEntitlement_Write
2. EntitlementType_Write
3. EmployeeEntitlementRosterValue
4. EmployeeEntitlementRosterBalance
5. EmployeeEntitlementRosterUsage

CONFIGURATION

The main configuration of entitlements is performed under the Administration module.

Navigate to Entitlement Types to define how the entitlement behaves and who is eligible.

Navigate to Entitlements to define the assignment of an entitlement type to an individual employee.

Navigate to States to manually add or correct usage entitlement usage records for an employee if needed.

Navigate to Depleted or Depleted Past Entitlements to define which entitlement types must be consumed before others.

ROSTER VIEW

For the most effective roster work, there are several options you should enable:
1. View - Requests, Pattern

2. Employee information - Attendance State, Individual Time off / Activity Entitlement, Balances, Usage

REPORTS

To support common reporting needs, the following calculation types can be configured:

• Entitlement
• EntitlementBalance
• EntitlementDeduction
• EntitlementBalanceState

MOBILE APPLICATION

Navigate to Configuration to adjust MobileAppTimeOffProperties and list all entitlement types that should be visible in the mobile application (see the example in the Schema tab).

The Balance Period feature defines how employee working time is managed and evaluated over time within the system.

It defines how actual worked time is compared against the working time fund, how working time balances are created, and how these balances are carried forward and settled within a balance period.

KEY COMPONENTS

• Balance Period
  Defines the time frame in which actual worked time is evaluated against the working time fund.
• Balance
  Represents the difference between actual worked time and the working time fund within a balance period.
• Balance Type
  Defines whether a balance is positive (surplus) or negative (deficit).
• Cumulative Balance
  Represents the continuously accumulated result of balances across periods that is carried forward until settled.
• Tracked Overtime
  Represents worked hours explicitly marked as overtime and excluded from standard worked time totals.
• Balance Period Type
  Defines whether the balance period is fixed (predefined dates) or rolling (moving time window).

PERMISSIONS

• WorkSheetView
• OwnWorkSheetView

BALANCE PERIOD CONFIGURATION

1. Basic configuration

Performed in Administration under Balance Period.
2. Balance Property configuration

Used to configure a fixed balance period.
The default value must be set to 0, and the duration of the balance period must be defined.

3. Balance period assignment

The created balance period must be assigned to organizational units, working time models, or individual employees.

When assigned at multiple levels, the balance period assigned closest to the employee takes precedence.

ROSTER VIEW

Balance period values are displayed on the roster through:

1. Minimum required propreties:
   • Transferred balance from previous period
   • Refunded balance

• Setup of Property Type: None, Data Type: PropertyDataType.DurationHours or PropertyDataType.DurationSeconds

2. RosterComputations Configuration parameter

• Calculation type: ReportProperty
• Links roster properties with corresponding report metrics

REPORTS

Balance period display requires a report with the following statistics:

• CumulativeBalance_TransferredBalanceFromPreviousPeriod
• CumulativeBalance_RefundedBalance