SDK: Building a Module (Advanced)
  • 10 Aug 2022
  • 3 Minutes to read
  • Dark
    Light

SDK: Building a Module (Advanced)

  • Dark
    Light

Version 7.x .NET Architecture Change

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.

If a custom module needs to be updated, refer to the Updating Custom Modules article.


Creating a Custom Module

  1. Install Decisions 7 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.
    Module.Build.xml ElementUse RelevanceDescription
    CoreServicesDllsMost commonly usedThis folder contains a DLL or multiple DLLs that define a project's Flow steps, Rule parts, customizations, behaviors, initializer code for setup, and more. If these files have any Web Services registered in this folder, the user will get corresponding ServiceClient DLLs in the ServiceClientDlls folder. These are created by the CreateModule.exe tool.
    ReferenceDllsRequired if third-party dlls are usedUsed to store third-party dependencies for a module.
    CliDllsMost commonly usedSee note on CoreServicesDlls. This folder does not usually contain any custom assemblies, only those generated during module build.
    WebPagesNot typically usedHTML or ASPX pages go in the web host's root directory. This folder must contain zip files that are unpacked on module installation. The unpacked files become peers to the Login.aspx page. This folder may contain folders, and those folders will be maintained.
    MvcDllsNot typically usedFolder for compiled Dlls of MVC views and controllers
    MvcViewsNot typically usedThese are additional MVC Views that are hosted in the Decisions.Web. The host is the primary user interface. MvcViews can be used to add additional view controls for pages and forms. These files go to the installation's Web Host/HUI virtual directory. HUI is the virtual directory that serves the HTML portal to users.
    AgentDLLsNot typically usedExtra DLL files for adding the capability to the Decisions Cloud to Site Agent. If not using the agent and extensions to the product do not need to be run through the agent, this folder can be safely ignored.
    SQLScript / MySQLScript / OracleScript / AzureScript
    Not typically usedThese are database scripts that will run when the module is deployed. These are often used to add tables or stored procedures that this module relies on.
    ObjectsToImportCommonly usedFlows, Pages, Reports, Rules, and Folders that have been built by the Decisions designers and exported from Decisions using the Import/Export function. These should be .decObj files.

  6. Implement the module functionality by adding class files or custom code.
  7. Run BuildModule.ps1 to build DLL and create Module.zip. 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 Decisions Server service, copy the zip into 'C:\Program Files\Decisions\Decisions Server\CustomModules', and starts the Decisions Server 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. 

Debug 

  1. Attach IDE debugger to Decisions.Web.Core.exe process.
  2. Add breakpoints.

Best Practices

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

  • Always version modules.
  • If issues arise, please refer to C:\Program Files\Decisions\Decisions Server \Logs.

For further information on Modules, visit the Decisions Forum.

Was this article helpful?