Add-Ins are buttons you add to DocMgt that do something when a user clicks them. An Add-In can run a list of workflow actions, open a web page, start an E-form, or download a Document, and it can ask the user for information first. Because an Add-In can use almost any workflow action, it is the usual way to give users a one-click tool for a job that would otherwise take several steps or need an administrator. The topics in this folder each build one complete Add-In from start to finish. Use them as they are, or as a starting point for your own.


Types of Add-In

The Type setting decides what the Add-In does when it is clicked.

  • Actions Only runs the Add-In's actions and nothing else. Most of the examples in this folder use this type: fixing data, restarting workflow, stamping or signing Documents, sending email.
  • Full Screen Web Site opens a web address in place of DocMgt. The address is built after the Add-In's actions run, so it can include Record fields, IDs, and values the actions set.
  • Embedded Web Page shows a web page inside DocMgt. The page loads without a Record, so it suits tools that do not depend on one, such as a company directory or a dashboard.
  • Pop-Up Window opens a web address in a separate window, built after the actions run, like Full Screen Web Site.
  • Start E-form opens an E-form for the user to fill in, such as a request or approval form started from a Record.
  • Download Document gives the user a file to save. This type appears only when your system has it turned on.


Where an Add-In can appear

The Where to Show settings decide where the button is placed, and which Records and Documents its actions work on.

  • Toolbar Add-Ins are available from anywhere in DocMgt. Use them for tools that do not belong to a single Record, such as starting a new request or opening another application. They can also be placed in the Admin or Reporting panel so only those users see them.
  • Record Add-Ins appear on the Record screen and work on the open Record and, if you choose, the Document open in the viewer or the checked Documents. This is where most everyday tools belong: marking an invoice paid, signing a Document, emailing a letter.
  • Search Add-Ins appear on the search results screen and run their actions once for each checked Record, or for every Record found if none are checked. Use them for bulk work, such as updating a field on many Records at once or repairing data after a bad import.
  • REST / MCP Add-Ins can be run by other programs and by AI assistants rather than by a person clicking a button.


The same Add-In can appear in more than one place. Use Record Types and When to Show to decide which Record Types and which users see it.


What Add-Ins are good for

Almost any job made of workflow actions can be put behind a button. Some common kinds:

  • Data tools fill in, correct, or clear fields, copy a Record, or restore values from the Record's history.
  • Workflow tools start, restart, cancel, or reassign a Record's workflow, so users do not have to wait for an administrator.
  • Document tools stamp, annotate, sign, merge, convert, combine, or delete Documents.
  • Communication tools email a merged letter, send a text message, or share a Document with someone outside DocMgt.
  • Reporting and export tools build a file from search results and send it on.
  • Integration tools send data to another system, open it at the right place, or pull information back.
  • AI tools run AI actions on demand, such as reading an invoice again after a better scan is added.


Asking the user for input

An Add-In can collect what it needs before its actions run.

  • Confirmation Prompt asks the user to confirm before anything happens. Add one to any Add-In that changes data or workflow.
  • Data Entry Options ask the user for values, such as a new status or an email address, which the actions can then use.
  • Request Signature asks the user to sign, and saves the signature to a Record field the actions can use.
  • Start E-form gathers more detailed information on a form.


Before you build one

  • Test on a test Record first. Most Add-Ins change data, workflow, or Documents. Run a new Add-In on a test Record and check the result before you make it available to anyone else.
  • Limit who can see it. Use Record Types so the button appears only where it makes sense, and When to Show so only the right users have it.
  • Refresh after running. When an Add-In changes what is on the screen, set it to refresh the Record/Viewer screen after running so the user sees the change.
  • Know where the actions run. Record Actions run once for each Record. Pre-Process Actions and Post-Process Actions run once, before and after the Record Actions.
  • Replace the sample names. Field names, Categories, and Record Types in the examples are samples. Use the names in your own system.