> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/tools/document-services.md). # Plugins **Category:** Tools **Version:** 1.0 **Last updated:** July 13, 2026 **Author:** Any2Info *** ### Description The **Plugins** tool allows administrators and users with **Advanced configuration** permissions to manage custom plugins within the Any2Info platform. A plugin is a custom .NET assembly (DLL) containing customer-specific business logic that extends the standard functionality of the platform. Plugins allow organizations to integrate external systems, implement custom validation, and execute additional business logic without modifying the core application. Plugins are developed externally using an IDE such as **Visual Studio** or **Visual Studio Code**, after which the compiled plugin assemblies and any required supporting files can be uploaded through the platform. Once uploaded, plugins can be enabled on supported platform components such as forms and dashboards. *** ### Supported Plugin Types The platform currently supports the following plugin interfaces: | Plugin Interface | Purpose | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | **IDashboardPlugin** | Loads custom data for dashboards. This can be used to retrieve data from external systems or perform custom calculations before dashboard rendering. | | **IDocumentServicePlugin** | Provides custom document downloading logic. For example, retrieving documents from an external document management system instead of the default storage. | | **ISaveFormPlugin** | Executes custom logic during form saving. Supports both **Before Save** and **After Save** events. | #### ISaveFormPlugin The **ISaveFormPlugin** contains two execution methods. **Before Save** Executed before a form is saved. Typical uses include: * Validating entered data * Automatically populating fields * Modifying values before storage * Preventing invalid data from being saved The plugin may cancel the save operation. When this happens, the user receives a save error message and the form is not stored. **After Save** Executed after the form has been successfully saved. Typical uses include: * Calling external APIs * Synchronizing data with third-party systems * Sending notifications * Starting additional business processes *** ### Managing Plugins Plugins can be managed through: **Platform → Tools → Plugins** The screen consists of two sections: #### Plugin files Contains the uploaded plugin assemblies (.DLL files). For each plugin the following information is shown: * Name * Description * Enabled state Use the **Add** button to upload one or more plugin assemblies. #### Supporting files Contains any additional files required by uploaded plugins. Examples include: * Configuration files * Additional libraries * Resource files Use the **Add** button to upload supporting files required by your plugins. *** ### Plugin Workflow The typical workflow for using plugins is: 1. Develop the plugin using a supported IDE. 2. Compile the project into one or more DLL files. 3. Upload the plugin assembly through **Platform → Tools → Plugins**. 4. Upload any required supporting files. 5. Configure the appropriate form or dashboard to use the uploaded plugin. *** ### Usage Plugins are typically used when standard platform functionality needs to be extended. Common scenarios include: * Loading dashboard data from proprietary systems * Downloading documents from external storage providers * Performing advanced form validation * Executing custom business logic after saving forms * Integrating with ERP, CRM or other line-of-business applications *** ### Tips & Best Practices * Develop plugins using the matching Any2Info plugin interfaces versions. * Keep plugin logic focused on a single responsibility whenever possible. * Upload all required supporting libraries together with the plugin assembly. * Thoroughly test plugins before deploying them to production. * Only activate plugins on the forms or dashboards that require them. * Handle exceptions within plugin code to prevent unexpected runtime failures. *** ### Limitations * Plugins must be developed externally; they cannot be created within the Any2Info platform. * Only supported plugin interfaces can be loaded by the platform. * Plugins require activation on the appropriate forms or dashboards before they become active. * Incorrect or incompatible plugin assemblies may fail to load or execute. *** ### Additional Information For information about developing custom plugins, supported interfaces, and implementation guidelines, please contact **Any2Info Support**. *** ### Metadata | Property | Value | | --------------------------- | --------------------------------------------------------- | | Tool type | Platform Tool | | Location | Platform → Tools → Plugins | | Supported plugin interfaces | IDashboardPlugin, IDocumentServicePlugin, ISaveFormPlugin | | Supported file types | DLL and supporting files | | Version | 1.0 | *** ### Changelog | Version | Date | Change | | ------- | ------------- | ------------------------------------ | | 1.0 | July 13, 2026 | Initial documentation version added. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://academy.any2info.com/any2info-academy/no-code-platform/tools/document-services.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.