Background actions
 | If you do not use a Planon Accelerator environment, the Background actions TSI must be added to the navigation panel. For example, you can add it to Supporting data or System Settings. |
Background actions are actions that take longer than 30 minutes to run on the Web Client. The maximum session time on the Web Client is 30 minutes. Consequently, if you are running actions that take longer than 30 minutes, there may be session timeout errors.
| | To reduce storing data in the PLN_SESSIONDATA table and improve performance, (stateless) in-memory session IDs are used for background actions |
Examples of time-consuming actions:
• Deep copying
• Generating clustered orders
• Compiling property-based maintenance plans
• Compiling contract-based maintenance plans
• Replenishing stock, by creating automatic replenishment suggestions
• Running a Talk/SDI definition
• Running a configuration transfer
• Processing Planon AppSuite data synchronization (also see the Planon AppSuite - Configuration Guide)
These actions are run in the background on the application server while you and your colleagues continue working.
| | • For a background action like generating clustered maintenance orders, the clustering takes place in batches, according to the clustering criteria that apply. This reduces the number of session time out errors and makes it easier to verify in the logging which actions were successful. • In order to prevent the 'history' from piling up, you can delete the older background actions. The Delete action is disabled if the selected background action is running. |
Logging
A log is created for every background action running on the server, to keep track of its progress. The log can be seen in the TSI per background action and it allows you to view what a particular background action has done.
Background action statuses
Background actions can have the following statuses -
Not started, Queued, In progress, Completed and Completed with errors. There can be 5 simultaneous background actions (jobs) in progress. Planon comes with predefined defaults (which are applicable for most common use cases) for the number of background actions that are run simultaneously.
Not started, Queued, In progress, Completed and Completed with errors. There can be 5 simultaneous background actions (jobs) in progress. Planon comes with predefined defaults (which are applicable for most common use cases) for the number of background actions that are run simultaneously.
| | The priority of the background actions is first in first out. Actions with the oldest insert date-time will be picked up with the highest priority. |
Background action progress
The Background action progress bar displays the progress of a background action currently running in the background. The progress is shown in percentage from 0 to 100% and is set to Done when it is completed.
For a description of the fields, see the following table:
Field | Description |
|---|---|
Property set | Displays the active property set for this background action. |
Status | Indicates the background action's status, which is either: • 0, Queued • 1, In progress • 2, Completed • 3, Completed with errors |
Start date-time | Displays the date and time the background action was started. |
Completion date-time | Displays the date and time the background action was completed. |
Duration | Displays the duration of the scheduled task in milliseconds. |
Has errors | Indicates whether errors were encountered. If the status is 3, Completed with errors, this field will be set to Yes. |