Element data storage specifics
Each process has its own set of elements. In this case, the hierarchy is similar to information blocks, where process - is information block type and elements - are information block elements. Only instead of iblock properties, user fields from kernel are used.
Large portion of code, responsible for storage of elements and user property values is concentrated in the folder modules/main/lib/userfield/internal
Find more details in this article about general processes of dynamic creation of tables and columns.
Classes in rpa, responsible for process tables, elements and harnessing code are descendants to kernel classes.
System fields
All element tables in rpa have a set of system fields:
See more details in \Bitrix\Rpa\Model\PrototypeItem.
User sorting of elements in kanban
Each user can set an arbitrary order of elements in each stage using kanban.
This sorting will be working only within this stage and only for this user.
Without this sorting, elements with oldest date of stage change are displayed at the top of column (see \Bitrix\Rpa\Model\Stage::getUserSortedItems())
Table b_rpa_item_sort.
Class \Bitrix\Rpa\Model\ItemSortTable.
Full text index
Dynamic table for storing full text index is created for each process aside from element table.
Index is filled automatically via events (\Bitrix\Rpa\Model\DataManager::onAfterAdd, \Bitrix\Rpa\Model\DataManager::onAfterUpdate)
Class \Bitrix\Rpa\Model\PrototypeItemIndex.
Tables themselves are created here \Bitrix\Rpa\Model\TypeTable::onAfterAdd.
Revision history
All actions, executed by elements are logged in detail in a separate page.
This table is filled with data not via events, but via \Bitrix\Rpa\Command::saveToHistory().