/create-cover-action -- Добавление действий на обложку модуля RX

To add an action to a Directum RX module cover, you insert CoverEntityListAction or CoverFunctionAction entries into the RX Module.mtd file and ensure proper UI localization via ModuleSystem.resx. This process wires the action to the client interface.

You open an entity list by configuring a CoverEntityListAction in the module cover definition. This requires extracting the correct EntityTypeId from the target entity's .mtd file and mapping it to the action in your RX Module.mtd configuration.

Cover actions lack localization when ModuleSystem.resx keys are missing or mismatched. You must create matching localization keys for your CoverEntityListAction and CoverFunctionAction entries, then run MCP validation tools to verify the fix.

You group and order actions by assigning valid GroupId and TabId GUIDs in the RX Module.mtd. To preserve the exact sequence of cover actions, use the PreviousItemGuid property to link items and then validate the structure.

Yes, you trigger client-side reports or SPAs by adding a CoverFunctionAction to the module cover. This action type calls module client functions without parameters, allowing users to launch reports directly from the Directum RX UI.

Yes, valid GUIDs are strictly required for NameGuid, GroupId, and TabId when configuring Directum RX module covers. Using invalid or mismatched identifiers breaks action grouping and tab placement, so always validate them with MCP tools.