Microsoft word document routing

The process can run as either a desktop application or a Microsoft Windows service. When the application runs as a Windows service, it can be started automatically after a computer restart. It can also be configured to run under the security context of a specific user account. This enhancement lets customers host the Document Routing Agent on secured domain resources such as network print servers. An application is a program that a user interacts with on the desktop.

A service is a process that runs in the background and doesn't have an active window. The Document Routing Agent now supports both execution modes. It's important that you understand why you might select one mode instead of the other and the steps that are involved in running the process as a service.

Here are some of the main benefits of running the Document Routing Agent as a background service:. Although there are many benefits of running the Document Routing Agent as a Windows service, there are also limitations. Ok, creates an e-mail with an attachment. What the routing would do, is the originator of the document would create a list of people in a specific order. Then when the e-mail went out it would go to the first person in the list. When they were done, they could route it to the next recipient automatically.

In reply to ShelleySizer's post on June 14, In them, the content type can be part of the criteria that determines the final location where a document is stored.

You can route documents to a library or folder in a Records Center site or any other kind of SharePoint site. The Drop Off library, which is automatically created when you activate the Content Organizer feature, serves as the default location. The document routing process is made up of several elements:. Target libraries and folders Content stewards or records managers manually create libraries and folders where documents should be routed, and designate these libraries as target libraries.

Site content types Every document must have a content type, and users can add appropriate site content types manually to target libraries. Or, you can configure the Content Organizer so that all uploaded documents are temporarily routed to the Drop Off library. Note: The Drop Off library is intended as a "catch-all" for those items not matching any rule.

It is designed as a temporary location, and not as a permanent collaboration site. Document rules list This is a collection of all the routing rules. Content stewards or records managers visit this list to create, manage, and view routing rules. The following diagram shows how documents and email messages are routed based on meeting specific criteria, and how documents that are missing information are returned to the Drop Off library.

For each record type that you add to the Record Routing list, you specify a record title and description. You also specify the location in the site where the record is stored. To make sure that all relevant records are routed to the appropriate location, you can specify alternate names for the record type. Note: You must have at least Site Owner permissions to create rules to route documents. On the Content Organizer Rules page, in Click to add a new item , select add. In the Rule Status and Priority section, to apply the rule to incoming content, select Active.

Then, select a priority to determine how content is routed should it match more than one Content Organizer rule. We would like to automate the process for an internal employee to apply to a current job opening. We want them to fill out the application form and the submit it somehow. We then want it to automatically route to their manager for approval.

Then after the manager approves it, we want it routed to the HR Department for approval. Then finally to the Recruiting Manager. Is that sort of thing possible and does anyone have any tutorials or info I can check out to figure out how to make it happen?

I see you do not have a reply yet. I create additional fields that I don't display that capture stages that need to be met before the mail is sent to someone. Hopefully that is helpful to understand how you can capture the steps to control the process of who to send the email to at each stage. Of course, you would need to store the names and email available for each manager. If you are storing this when you craft the position then you would have it already. Unfortunately I cannot provide specific details for the particular program you are using.

My only hope is that my example helps you brainstorm and possibly apply a similar approach with the tools available. Or springboard to bigger and better ideas!