Dive deeper into the Workflow Foundation demo and extend it.

Once you have a good understanding of the Tree Definitions, the data types, the Forms XML and the simple edit workflow your are familiar with the major artifacts that make up a WF based CMS Console application.

If you wish to dive deeper into the samples and technology we suggest the following steps:

• Edit a product and specify a price like 10.17 (something not divisible by 0.05), save and notice the balloon that pops up on the "Price" field. Locate the code responsible for validation alert in the workflow code.
• Familiarize yourself with the XML schemas located in the web projects ~/Composite/schemas subfolder – here you will find schemas for both Forms XML and Tree Definition XML.
• On a workflow, try to disable one or more events, run the changed workflow and notice how the UI buttons for those events no longer show up.
• To make a simple but visible change to a workflow, try adding a ShowFieldMessageActivity (from the WF Toolbox) to a step, set the title and message, recompile and execute the workflow.
• Set a break point in workflow code and run the website in debug mode and have it break.
• Examine the AddNewProductWorkflow – this flow is running as a wizard which will skip step 2, based on input given in step 1. Figure out what makes the wizard skip step 2 on back / forward.
• Figure out how the Add Product workflow transitions into the edit product workflow when it’s done.
• Create a new workflow which enables users to delete a Product Category and hook the workflow to the Tree Definition.
• Create a new workflow which enables users to edit a Product Category (title and description) and hook the workflow to the Tree Definition.
• Create a new wizard based workflow which enables users to add a new Product Category. When completed the edit workflow should start and the tree be refreshed so it contains the new element.