Difference between revisions of "Workflow Requests List View"
From SmartWiki
m (→Notes) |
|||
| Line 13: | Line 13: | ||
==Notes== | ==Notes== | ||
* Custom Fields on a Level 1 [[Template]] cannot be added. Only "Global" Level 1 Custom Fields. | * Custom Fields on a Level 1 [[Template]] cannot be added. Only "Global" Level 1 Custom Fields. | ||
| − | * Level 1 Custom Fields can only be added from one [[UTA]]. If the Application Configuration page from a different UTA is saved it will over-ride the selections in the first UTA (even if nothing is selected in the second UTA. | + | * Level 1 Custom Fields can only be added from one [[UTA]]. If the Application Configuration page from a different UTA is saved it will over-ride the selections in the first UTA (even if nothing is selected in the second UTA). |
[[Category:Workflows]] | [[Category:Workflows]] | ||
Revision as of 09:14, 1 November 2011
The List View on the Workflow Requests page is almost entirely system defined. This is because it must accommodate all Workflow Types.
The exception is that it can be configured to include one or more UTA Level 1 Custom Fields.
Procedure
At the bottom of the Application Configuration page of the UTA you will find a Select Many Combo Box that allows you to choose which fields should be included in the List View.
- The fields will be displayed on the far left of the list view, before the standard system-defined Workflow Request List View columns.
Notes
- Custom Fields on a Level 1 Template cannot be added. Only "Global" Level 1 Custom Fields.
- Level 1 Custom Fields can only be added from one UTA. If the Application Configuration page from a different UTA is saved it will over-ride the selections in the first UTA (even if nothing is selected in the second UTA).
