ShareVis has been successfully benchmarked and won against systems that cost several times more and is now in use by companies in Electronics/High Tech, Automotive, Manufacturing, Healthcare, Oil & Process, Transportation, Pharmaceuticals and Government.

As part of the sales cycle ShareVis typically offers to configure and demo a workflow and web-form process. In most cases the a company will already have a quote for a custom implementation of the same process and seeing it easily configured in ShareVis really opens their eyes to the power of ShareVis. The process showcased in the demo usually ends up being the first process the company deploys once ShareVis is installed.

The depth and breadth of the following real-world example exemplifies the power and flexibility of ShareVis. Customer references are available upon request.

Objectives

• A corrective action form is filled out and submitted.
• The responsible person is selected automatically based on location, part number, product line, or a combination.
• The responsible person may reject the corrective action, re-assign it to someone else, or accept it.
• If the corrective action is accepted, then the accepting manager assigns it to a person or team who works on the problem.
• Once the person/team has a solution the manager reviews the results and either accepts or rejects it. If the solution is rejected it goes back to the team for re-work, and the process is repeated until an acceptable solution is reached.

Implementation

• External data source is prepared with location data and information about responsible managers per location. Additional data sources are made available for ERP part data lookup.
• The workflow is prepared using ShareVis Designer.
• The Corrective Action form is designed using Microsoft's InfoPath product. Views are prepared for the different activities in the workflow. InfoPath views are mapped to the tasks of the workflow, ensuring that each participant sees only appropriate information for his task.
• End users interact with the form through only a Web browser.
• Custom ShareVis InfoPath controls automatically complete sections of the form as the workflow proceeds.

Workflow Definition

	Once the “Functional Manager” accepts the responsibility, the workflow continues to the “Review Actions” sub-process (also known as a “loop”) that contains the workflow shown in fig. 2. The loop is of type “Repeat_Until,” which means that it will continue looping until the condition is achieved.
Figure 1 (Click to enlarge)
	The loop is defined to continue until the "Review and Verify" step is "Approved" by the Functional Manager. This means that the corrective action will continue until the Functional Manager is satisfied with the work done by the Assignee(s). This step of the workflow is associated with the "Assignee" view of the form.
Figure 2 (Click to enlarge)

Form Definition

	InfoPath design view of the screen that the initiator of the corrective action sees, i.e., this view is associated with the first step of the workflow.
Figure 3 (Click to enlarge)
	The part numbers are lookup via the ERP data source.
Figure 4 (Click to enlarge)
	InfoPath design view of the screen that the "Assignee(s)" see, i.e., this view is associated with the "Assignee" step of the workflow. InfoPath design view showing the ShareVis extensions to InfoPath. The "ShareVis.Assignement" control automatically fills in the name of the "Initial Approver" in the corresponding field on the form at the step in the workflow the Functional Manager accepts the corrective action.
Figure 5 (Click to enlarge)
	InfoPath design view showing the ShareVis extensions to InfoPath. The "ShareVis.Attachment" controls who can upload information and at what step of the workflow.
Figure 6 (Click to enlarge)

Run Time Screens

	Runtime Web-based form, initial view where the originator selects the Responsible Area, Source, and Product. The process participants are in this case automatically selected based on the database lookup.
Figure 7 (Click to enlarge)
	Completed form with attached process trace.
Figure 8 (Click to enlarge)
	All the information collected in the process is of course stored in SharePoint and available for reporting purposes and further processing.
Figure 9 (Click to enlarge)