Delivering Messages to FileBound

A default connector profile can be created to deliver messages to FileBound. Administrators can specify default values for delivery to the FileBound DMS. It can be configured to deliver to one project and its parameters, or it can be set up with a placeholder variable; for example, “%ProjectName%” which the default profile can use to deliver messages to any project specified by the workflow.

Note: This method is a viable delivery solution for organizations that do not use AccuRoute Desktop, AccuRoute Queue Desktop or WebApps.

In this example, Administrators create the profile, select a single project, and specify file fields, separator, and divider parameters by using the Server Administrator. There can only be one default profile which can be updated as needed.

Note: The project, file, separator, and divider parameters are typically defined in FileBoundand then used by the connector to route the messages to the appropriate location in FileBound. Administrators can create new files, separators, and dividers in the Server Administrator if they have not been defined in FileBound. This also applies to using AccuRoute Desktop, AccuRoute Queue Desktop and WebApps to deliver messages to FileBound.

See the FileBound on the Server Properties dialog box example below.

See About FileBound Connector > Setting up the default profile for more information.

AccuRoute Desktop (ARD) can be used to deliver messages to FileBound as a recipient type. In this example, ARD users select a recipient type, format, add the project to profile, specify file fields, separator, and divider parameters by using AccuRoute Desktop.

Additional parameters like subject, comments, and attachments can be defined in AccuRoute Desktop and delivered to FileBound.

See the AccuRoute Desktop dialog box example below.

See About FileBound Connector > Adding FileBound as an AccuRoute Desktop recipient for more information.

WebApps can be used to deliver messages to FileBound as a destination in a distribution. In this example, users create a distribution with FileBound as a destination, select a format, project, specify file fields, separator, and divider parameters.

See About WebApps DMS Document Profiling and About Create Distribution for more information.

AccuRoute Queue Desktop can be used to deliver messages (jobs) to FileBound. In this example, Queue users select the appropriate job, specify additional parameters, apply, and release to FileBound.

Note: Projects, files, separators, and dividers, if any, are preconfigured by Administrators. Queue users will need to specify general file fields and line items specified in the Edit Data dialog box.

See the AccuRoute Queue Desktop example below.

See Sending a job using AccuRoute Queue Desktop for more information.

The AccuRoute FileBound User Interface (UI) for selecting projects, file fields, and other parameters is the same for the delivery methods listed above except for AccuRoute Queue.

See the UI wizard example below.

In this example, a loan application project is selected.

Note: Users can create new files or add to existing files when selecting projects. If the Add to existing file option is selected, users will need to specify the appropriate search parameters, find, and select the appropriate file.

The user enters the appropriate file fields for the project.

The user selects or specifies the delivery details which may include document name, separator, divider, and notes if necessary.

Note: The Separator and Divider drop-down list boxes may contain predefined values from FileBound. They can also be used to specify a user’s Separator and Divider values by typing them in the appropriate list box.