Open Nintex Workflow for Project Server 2010 workflow designer. Click Sites Actions > Project Server Workflow > Create Project Server Workflow.
In the Workflow Designer Ribbon, click on Workflow Settings. Enter the title "Basic Branching Workflow" and a description "The proposal will be automatically rejected if it exceeds $1,000,000". Click Save.
Note: The task list called Project Server Workflow Tasks is the default task list used for Project server workflows that is accessible from the Workflow Approvals link in the PWA home page.
The initial steps within this workflow will be to set the project stage and initial status of the project to wait for an input when the workflow is started.
In the Workflow Actions Toolbox, click the Project Server category for the workflow actions that are specific to Project Server.
Note: This tutorial is focused on the Project Server actions; the full set of Nintex Workflow 2010 actions are available to be used to integrate with SharePoint and other Line of Business systems.
Click and drag the Set project stage and Set status information actions from the toolbox onto separate the design canvas.
Double click on the Set project stage action to open the configuration dialog. In the Stage drop-down menu, select Initial Proposal Details. Click Save.
Double click on the Set status information action to open the configuration dialog. In the Stage drop-down menu, select Initial Proposal Details. In the State drop-down, select Waiting for approval. Click Save.
Add a Compare project property action from the toolbox to the design canvas below the Set Status information action.
Double click on the Compare project property to open the configuration dialog. The Compare project property action will return a True/False based on the comparison. Create a workflow variable to store the result of the comparison.
Configure the outcome of the project based on the result of the comparison. In this example, the project will move to the next stage if it is equal or less than $1,000,000; else an automatic rejection will occur.
Add the Set a condition action to the design canvas (below the Compare project property action). Double click on the action to configure it.
Add a Set project stage, Set status information and End Workflow actions to the "Yes" branch of the Set a condition action on the design canvas.
In the Set project stage action, configure the action as follows:
In the Set status information action, configure the action as follows:
Add the Set project stage and Set status information to the No branch of the Set a condition action on the design canvas.
In the Set project stage action, configure the action as follows:
In the Set status information action, configure the action as follows:
Add a Set project stage and Set status information outside the Set a Condition branches.
In the Set project stage action, configure the action as follows:
In the Set status information action, configure the action as follows:
Your workflow should now look something like this:
The Basic Branching Workflow is now complete. The workflow will run when a new project is created based on an Enterprise Project Type that has been associated to this workflow.
Follow the next tutorial to learn how to > Associate a Nintex Workflow with an Enterprise Project Type
a lot of the workflows seem to revolve around entering information and approve/reject rather than ones with multiple levels of depth. I would find it helpful to see an example where the user makes an initial Product group selection, steps down into Product detail selection and input and then a series of approvals routing occurs from there. I'm trying to build a workflow for internal sales / relationship managers for a family of products to replace all the spreadsheets and phone calls (with errors). I'm also trying to break down the amount of information displayed on each screen to 5-8 fields.