SDK: Building a Module (Advanced)
  • 04 Aug 2022
  • 1 Minute to read
  • Dark
  This documentation version is deprecated, please click here for the latest version.

SDK: Building a Module (Advanced)

  • Dark

Custom modules are created by users to add or extend certain functionalities and to link together different types of custom functionality. While custom modules do not require .dlls, it is common to build custom code in a .dll. Use of custom module may involve grouping exported Decisions Objects, custom Flow behaviors, and/or step implementations together in one Module, integrating custom Flow or step implementations with a third party library, etc.

Creating a Custom Module

  1. Install Decisions 6 locally. Download the Custom Module by selecting Code > Download ZIP; use this as a guide to creating a Module.
  2. The example module is named "CustomModule." Rename files to match the name of the Module that is being created.
  3. Open CustomModule.csproj, CustomModule.sln, Module.Build.xml, and build.proj and rename instances of "CustomModule" to match the module name.
  4. If needed, update the NuGet package reference in the CustomModule.csproj file to the correct version of the SDK.
  5. Add a reference to any external or third-party DLLs.
  6. Implement the module functionality by adding class files or custom code.
  7. Run BuildModule.ps1 to build DLL and create To build the project, MSBuild is required. this builds the DLL file and creates the required module zip file to be deployed in Decisions.
  8. This script will create the zip, stop the Service Host Manager service, copy the zip into 'C:\Program Files\Decisions\Decisions Services Manager\CustomModules', and starts the Service Host Manager service.
  9. Once the Module is deployed, log in to Decisions Studio and navigate My Apps >APP STORE> Modules.
  10. Find the custom module, click DETAILS and click INSTALL.
  11. If any changes are required, make the changes to the code.
  12. Run BuildModule.ps1 to deploy changes and repeat as needed. 


  1. Attach IDE debugger to DecisionsServiceHost process.
  2. Add breakpoints.

Best Practices

When creating a custom module, keep the following best practices in mind:

  • Create a module for service DLLs and a different module for all configurations to assist with breaking cycles apart if using a development team and design team.
  • Always version modules.
  • If issues arise, please refer to C:\Program Files\Decisions\Decisions Services Manager\Logs.

For further information on Modules, visit the Decisions Forum.

Was this article helpful?