Personalización avanzada > Business Logic Customization > Customizing Workflow Administration > Customizing Workflow Task Pages > Rendering Custom Workflow Activity Variables
  
Rendering Custom Workflow Activity Variables
There exists a tag file (workItemInfo.tag) that must be included within each task page JSP, before the actual rendering of the components. This tag describes and gets the model of GUI Components for the given task page. For any custom workflow activity variables, you need to specify either a comma-delimited list of the activity variable names (which have been defined in the Workflow Definer) and/or specify the reserved keyword of "all_activity_variables". Height and/or width for each listed custom variable may also be specified using CSS style syntax. ". (Note: height and width can only be applied to java.lang.String activity variables, and width (only) can be applied for java.net.URL, java.util.Date, and wt.workflow.engine.WfDueDate custom activity variable types). A default height (1 character) and width (50 characters) are used, when none is specified. For example, a list of variable names can be specified as follows:
"variable_name1{height:1;width:2},variable_name2{height:1},variabl
e_name3{width:2},variable_name4".
Specifying "all_activity_variables" displays all visible activity variables except for those named "special_instructions", "instructions", or "primaryBusinessObject". The customizer is required to explicitly list these three activity variable names (if defined in the Workflow definer as such), in addition to the "all_activity_variables".
For the Windchill R9.0 out-of-the-box templates, the default renders all_activity_variables. In addition, the Change Management template includes the specification of the special_instructions activity variables.
Describe Examples:
<tags:workItemInfo
custom_variables="variable_name1,variable_name2{height:1}"/>
<tags:workItemInfo custom_variables="all_activity_variables"/>
<tags:workItemInfo
custom_variables="all_activity_variables,special_instructions{widt
h:50;height:5}"/
If you specify to render a particular custom activity variable (other than special_instructions, instructions, or primaryBusinessObject) with the all_activity_variables, the specified custom activity variable gets rendered twice.
Once the customizer has described and retrieved the property model (via the workItemInfo.tag), they need to specify where on the page to render the particular workflow activity variable's GUI component. This is done by including the taskPanelValue tag, along with the new property model and the list of variables to display at the desired location of the JSP. (Note: the list of variable names must match the names listed for tags:workItemInfo. That is, if "all_activity_variables" was specified, then this same name must be used to render the GUI Components for "all_activity_variables.)
Render Examples:
<tags:taskPanelValue propertyModel="${propertyModel}"
attrs="variable_name"/>
<tags:taskPanelValue propertyModel="${propertyModel}"
attrs="special_instructions"/
<tags:taskPanelValue propertyModel="${propertyModel}"
attrs="all_activity_variables"/>