QuickFlow2.0 release, including Aspx UI form framework!

There are two problems with SharePoint native workflows:

1) The expression of process logic is cumbersome whether it is a sequential model or a state machine model.

2) form Problems

• Infopath workflow forms are not easy to use. If you are designing complex forms, you may encounter various problems. The biggest drawback is that the task table is scattered, the customer generally asks to display the approval form and submission form together, but developers need to spend a lot of effort to implement it.
• Although it supports aspx forms, it only provides basic excuses and does not have a complete mechanism.

The first point has been well solved in QuickFlow1.0. Using the Flowchart model, the design process is no longer a bit painful.

QuickFlow1.0 only supports infopath forms. In the latest version 2.0, aspx forms are supported.

QuickFlow2.0 provides a new aspx form mechanism-ListForm
ListForm provides the following controls to create a workflow form:
1) button control
StartWorkflowButton: starts a workflow.
CommitTaskButton: Submit a workflow task.
TaskReassignButton: reassign a task
ActionsButton: automatically displays the corresponding approval button according to the Action in the WF designer. If you agree, call back.
2) Form Controls
FormField: List Field
TaskField: Task Field
These two controls solve the problem that SharePoint workflows have plagued developers for a long time-how to use the same page for the submission page and approval page?
3) task tracking control:
TaskTraceList: displays the processing status of all tasks in the current workflow (Old Version)

WorkflowHistory: displays the processing status of all tasks in the current workflow (new version, multi-language supported)

4) Link Control

TaskTraceLink: Link to the task history list

WorkflowChartLink: Link to the visual tracking page

Let's take a quick look at the SharePoint workflow designed by QuickFlow + ListForm:

1) Click the create button in the list to start the task.

2) Submit page

3) submitted

4) Go to the task monitoring page for approval

5) if you are a common user, go to

A user task is the webpart of the user task that comes with the system.

6) Approval page

7) Check the forwarding function.

8) the submitted change page after return

9) completed approval records

Such a one-step return process, using QuickFlow as long20In minutes.

Let's take a look at the development interface:

1) WF designer

2) Form

With support for aspx forms, QuickFlow can finally be used for WSS. Even if you do not have MOSS, installing a WSS can quickly meet your business process needs.

Download the sample project:

Bytes

This article details how to run the example project: http://www.cnblogs.com/jianyi0115/archive/2009/09/19/1569940.html

Quick flow's next plan article:

1) Use of QuickFlow ListForm (including FormField extension, TaskField extension, and data verification)

2) how to implement workflow forms without using ListForm, but completely default aspx

3) How can I use infopath forms for submission and ListForm for approval?

4) How to Implement the Goto function of QuickFlow (the administrator can forcibly redirect the process to any step)

5) How to Implement visual status monitoring of QuickFlow (the next version of QuickFlow will include this function and display the flowchart at design time as a page)

If a friend is particularly interested in a certain part, I will mention it above.

6) No code designer for QuickFlow (the general user can design the process) (supported in the next version)

Related Articles:

SharePoint workflow solution QuickFlow series (1) -- quick flow entry

SharePoint workflow solution QuickFlow series (2)-Task

] SharePoint workflow solution QuickFlow series (3)-Task ReAssign

SharePoint workflow solution QuickFlow series (4)-Step Rounter (Step Routing)

SharePoint workflow solution QuickFlow series (5)-tag (MultiTask and GroupTask)

SharePoint workflow solution QuickFlow series (6)-event bus (EventBus)

Quick flow2.0 Aspx form example running Method