Which elements of the cycles table are recalculated when the cycle changes?
When changes occur in the cycle, the row in the cycle table related to the cycle is recalculated.
Also, the header in the cycle table is a very important point! The cycle table is based on a simple table, and the logic for recalculating the header is the same for both!
What is the place of recalculation of the cycles table when changing in a cycle?
A row in the cycle table is recalculated after recalculating the tables inside the cycle and performing actions in these tables — that is, at the very end.
This is important — if you attach an action inside the cycle that takes data from the cycle row in the cycle table. Such an approach is incorrect.
If the action takes data from a row in the cycle table, then it should be attached there, or at the very least, ensure that it takes immutable data.
If I recalculate a row in the cycles table, will the cycle recalculation occur?
No. It is the row in the cycles table that will be recalculated.
How do I recalculate a cycle from the cycles table without going inside the cycle?
In the dropdown menu, select "recalculate cycle" — this option is available only to the Creator role.
Why would the cycle table put "no tracking of actuality"?
For example, there is an Orders table — this is a cycles table. There are several managers who work with different orders.
The first manager changed something in the order he had open — the tables in the order were recalculated, and then the row in the Orders table was recalculated. This led to a change in the relevance code of the Orders table.
The second manager at the same time changed something in the order he had open. And after his order was calculated and the row in Orders was calculated, Totum will check the relevance code. But it has already been changed by the actions of the first manager. At this point, Totum will automatically send the change of the second manager for a new recalculation.
If the cycle calculations are quite long — 1-2 seconds, and there are many users working with cycles in one cycles table, there will be delays.
To avoid this in heavily loaded cycles tables, without tracking changes is set.