Recalculate task executors
A one-off maintenance for tasks: it fills the service field of executors in old tasks from the executors table, so that the executor filter and the process board find them the same way as new ones.
Where to find it: Modules → System → Maintenances → Recalculate task executors
A worked example
The window consists of one explanation — «The Executor filter of the Actions journal and the Company Workflow board search old tasks by a service field that may differ from the Executors table of the task. The service fills that field from the table. Nothing else in the tasks changes. Safe to run again.» — and one working button, «Execute». «Scheduled» is inactive: the operation is one-off. There are no parameters.
Example: a task was created long ago, and later the person on the «Executors» tab was changed. The card shows the new executor, but the journal filter by their login does not find the task: the old record still holds the previous one in its service field. After «Execute» the window shows the result «Tasks with recalculated executors: M of N.» — N tasks were checked, and in M the service field was rewritten from the table. Run the maintenance again — M will be 0.
Why
The executors of a task live in the table on the «Executors» tab, and for searching their logins are also put together into one service field of the record: the «Executor» filter of the journal and the «Company Workflow» board read it. The task card and the user's task panel take the executors from the table. Now, every time a task is saved, the program builds the service field from the table again, but in tasks saved before that it could drift away from the table. Then a person sees the task in their panel but does not find it by filtering for themselves.
The maintenance builds the service field from the table by the same rule as saving a task does. All tasks are checked, completed ones too: the filter finds them as well.
What the maintenance changes and what it does not
- It writes only the service field of executors. Name, dates, status, executors in the table and booked time stay as they were.
- It sends no notifications to executors and writes no change history. In the record only the time of the last change and the search text are updated.
- A task whose service field already matches the table is not rewritten. The order of logins and upper or lower case are not counted as a difference: the filter does not tell them apart anyway.
- A task without a single executor in the table is not touched: an empty service field would hide it from the filter altogether.
When to run it
Once after updating the database to the version that builds the service field on saving. The schedule is disabled for this maintenance. Running it again is safe: what already matches is not rewritten. If someone saved a task exactly while the maintenance was running, run it once more.
The maintenance works in the current company. On a stand with several companies, run it in each of them. Only a user with the right to edit «Actions» can run it; in a company that takes tasks from another company's shared register, the maintenance refuses: those records belong to the owner company, run it there.
How to tell that it worked
The result of the run says how many tasks were recalculated out of those checked. Open the «Actions» journal and pick in the filter the executor who was changed in the old task: the task is found.
Where to look next
- Actions — the «Executors» tab and the journal filter.
- Company Workflow — the board that searches tasks by executor.
- System — all maintenance operations of the module.