Creating AD Hoc Workflow

Ad hoc workflow processes allow the user to create and amend process definitions very quickly and easily to meet new circumstances as they arise. Within this type of workflow, it is possible to have as many different process definitions as there are users of the workflow. The main goal of ad hoc-based workflow is flexibility in areas where throughput and security are not the most important concern, and allowing the user s own experience to define the processes.

Within this type of process, the user is attempting to solve a specific domain-based problem or task that he needs to do by applying his own domain expertise to the problem. This can come in many different forms; based on both the person and organization, this may change. Ad hoc workflow is one of the most important types of workflow that an organization has in its workflow arsenal.

Many times, these processes automate knowledge- intensive workflow that contains key bits of business and processing knowledge that often are lost, or, worse yet, that require additional work each time they are performed. Typically, these types of workflow have a low overall business value and low repetition rate. Often, they are known for not having a predefined structure, and for the next step in the process usually being determined by each user in the process. Each business process automated within this context is constructed individually whenever there is a need to perform a series of actions. Typical examples of this type of workflow applications are routing or for your information types of InfoPath form application that include meeting- and task-based agendas .