The GraphicalUserInterface (GUI) of a Workflow is build with Views and Templates. They define the structure of the html markup and the widgets. This section is about the concept and the usage of Views and Templates in Workflows.
Based on the controller-attribute of the workflow node the corresponding View is getting loaded. According to the three different Controllers Workflow, List and Form we offer three different Views. Like in common ASP.NET MVC we follow the same idea to seperate layout, structure and content. The RootMasterView describes the structure of the html-markup and seperates the GUI in different sections. The SiteMasterView describes the content of some consistent sections, like the Navigationbar and the Historybar . The variable sections are defined by one of the three Views. The View is loading, depending on the definition of the form, the corresponding Templates to build up the GUI.
Templates are stored in the same directory like views, they are also C#-Html Files (.cshtml) but they differ in usage. Views are always linked with the workflow controller and templates are linked with forms and lists. For a better understanding of the usage of templates we seperated it into two parts, Structure and Widget templates.
The templates Filter, Form, Tab, Group and Singlerow define the structure of the GUI. Except the Group and Singlerow Template, all other Structure templates are used only once either by its parent template or View. The call graph of the templates are equal to the structure of the forms, the Form Template uses the Tab Template, the Tab Template uses one or more Group Templates, the Group Template uses one or more widget templates and it can use additionally one or more Singlerow Templates, which also uses one ore more widget templates.
A Script Control is a partial view which is getting loaded by and . It renders the ASP.NET MVC ScriptBundles (see MVC Bundling and Minification).