ASP.NET Forms Technology
There are three different page sources when selecting to use the ASP.NET Forms Technology. They are:
- Use Default Pages
- Network Share (File System)
- Generate new ASP.NET pages
Use Default Pages
The Use Default Pages option makes use of K2 blackpearl out of the box pages that have been installed by the installer. These pages should preferably not be customized. The Default Pages contains installed assembly and associated *.aspx and *.ascx pages in the SharePoint file system.
There are primarily two types of default forms:
| ASP.NET Default Pages | |
|---|---|
| Default Basic Pages: | The Default Basic Page only allows for the setup, start and actioning of a workflow within SharePoint with the added feature of providing the user with the functionality to add additional comments |
| Default Advanced Pages: | The Default Advanced Page only allows for the setup, start and actioning of a workflow within SharePoint with the added feature of providing the user with the functionality to add additional comments, add DataFields and XML Fields. |
Network Share (File System)
The Network Share (File System) option allows users to create their own custom *.aspx pages and Associated DLL's and to upload these pages to the SharePoint site. These pages will then be used during the workflow.
 |
It is essential to provide a *.aspx page as well as a compiled dll for this feature to function correctly. |
Generate new ASP.NET pages
Page Generation is another source that is allowed in the wizards for the setup, start and actioning of the workflow. The entire page generation is based on a templating principle where a template is chosen during wizard run and the pages are generated according to the template. These templates are customizable and users can add, edit and delete them from the file system which is located at: C:\Program Files\K2 blackpearl\Bin\Layouts\workflowintegration
When generating pages Data Fields, XML Fields and SmartObjects can be surfaced on the page. The code is then automatically scripted into the *.ascx and .cs code behind.
 |
The pages used in this option must be in *.ascx format and not in *.aspx format. |
This option makes use of *.ascx controls, as the *.aspx host page is generated at deploy time and hosts the *.ascx control for ease of use from a development side. The generated *.aspx page is essentially the SharePoint interface and the control holds all the implementation and features for the processing of the workflow.
The figure below represents the directory structure for the generated forms. The forms project is represented as a website structure and the website directory may even be added to the project and the file contents amended.
