Overview

The Events submodule is comprised of a series of highly customizable, complex processing tasks that can be bound to and triggered by Action controls.

These include actions that can be used to generate documents, map to Excel files, design and send emails, and execute custom code.

Print Processes

A Print Process is a collection of individual print tasks (e.g. multiple documents) that will cumulatively be utilized in order to produce a single print output. The Print Process Designer allows for design of template-based document generation, which can then be triggered through buttons via the user interface. The system allows for the creation of separate print processes for a given application and you can assign any number of these print processes to a button.

Each print process will consist of a series of documents (or a single document). Each document must be a Word-based template (*.DOCX) file. The execution of the print process will occur when a corresponding button that is defined to trigger the process has been clicked.

The process itself consists of replacing static content stubs in your template documents with dynamically mapped values (outlined further in the Document Stubs help section). Subsequently, all defined documents within the print process will be appended together and processed through a PDF conversion engine to provide the final result, which can then be flushed to the user for immediate download or appended to an email process (further details in the Email Designer section of the help pages.)

Excel Export Processes

An Excel Export consists of a single Excel file that will be utilized as a template in order to produce a single Excel output. The Excel Export Designer allows for design of template-based spreadsheet generation, which can then be triggered through buttons via the user interface. The system allows for the creation of separate Excel exports for a given application and you can assign any number of these Excel exports to a button.

Each Excel export will consist of a single Excel file (*.xlsx) which will be used as a template. The execution of the Excel export will occur when a corresponding button that is defined to trigger the process has been clicked.

The process itself consists of replacing named ranges in the source file with dynamically mapped values from the application. The mapping process is further outlined in Export Ranges help section. The final result can then be flushed to the user for immediate download or appended to an email process (further details in the Email Designer section of the help pages.)

Email Processes

The Email Process Designer allows for the creation of email processing tasks that can be associated with button controls. For example, the system can send notification emails when a user creates a new record, edits an existing record, or generates a PDF from the application.

Custom Actions

The Custom Action Designer allows you to define custom actions with custom action hooks. In a dedicated server environment, this allows the end user to upload a compatible .NET assembly with custom code that will be executed during the regular execution of calculations.

This permits for a myriad of possibilities, such as pushing or pulling data to/from external systems, recursive calculations, custom complex validation mechanisms, and numerous other possibilities.

These hooks can then be associated with buttons and will execute at some point in the calculation process, based on the interfaces that the methods implement.