simulator-actors

To create actor records, first resolve the root form structure using getForm, map your data to item_<id> field keys, and call createActor with the formId and data. You can manage records using CRUD operations like updateActor and deleteActor.

Multiform actors use data keys named __form__<formId>:<itemId> to structure nested data. To locate the root form for leaf forms, you must trace the form hierarchy to ensure data is correctly keyed and mapped across the multiform actor structure.

You can search and filter actors within a workspace using the searchActors and filterActors functions. You must ensure the workspace context, specifically the accId, is known and verified before making any tool calls to discover or filter records.

Yes, actor descriptions support BBCode formatting and allow embedded references to other actors or apps. This enables rich text descriptions for records, providing detailed context and linking related data within the Simulator.Company environment.

To ensure data is keyed by field ids using the item_<digits> format, you must first resolve the form structure by calling getForm. This maps each field to its item_<id> key before passing the data to createActor or updateActor.

Yes, actor records integrate with simulator-forms, simulator-graph, and simulator-finance modules. This integration supports end-to-end workflows, allowing actor data to flow seamlessly across form structures, graph relationships, and financial operations.