create-workflow

To generate a Directum RX workflow, you provide the CompanyCode, ModuleName, existing TaskName, and a block list. The process outputs updated Task.mtd blocks, C# block handlers, and a matching RouteScheme.xml graph for end-to-end execution.

Wiring HandledEvents in Directum RX block handlers requires updating Task.mtd metadata to map events correctly while keeping BlockIds as an empty array. The C# handler method signatures must match the expected Assignment, Notice, Script, and Task block types.

Yes, you can add workflow blocks to an existing Directum RX task. You must supply the existing TaskName along with block names, types, and descriptions to generate the correct Task.mtd updates, ModuleBlockHandlers.cs scaffolding, and RouteScheme.xml.

Directum RX C# block handlers must use the {Company}.{Module}.Server.{ModuleName}Blocks namespace. This ensures the strongly-typed handler signatures for Assignment, Notice, Script, and Task blocks are correctly recognized within the module's server-side architecture.

RouteScheme.xml validation fails when the activity graph does not match the defined blocks or lacks correct GUID fields. The scheme requires a valid Start to Blocks to End flow that aligns exactly with the Task.mtd block definitions and their specific identifiers.

Creating a route scheme for multiple block types involves defining a minimal activity graph in RouteScheme.xml connecting Start, Blocks, and End. You must simultaneously update Task.mtd with the correct block definitions and generate C# handlers for each Assignment, Notice, Script, or Task block.