...
Here we create a Rule Attribute that is associated with the isUrgent field in the form. Let's use <process name>.eDoc.<rule attribute name>.RuleAttribute to name our rule attributes and <process name>.eDoc.RuleAttributes to name the associated XML file defining our collection Lcollection of rule attributes.
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<data xmlns="ns:workflow" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="ns:workflow resource:WorkflowData">
<ruleAttributes xmlns="ns:workflow/RuleAttribute" xsi:schemaLocation="ns:workflow/RuleAttribute resource:RuleAttribute">
<ruleAttribute>
<name>RequestFirewallChange.eDoc.isUrgent.RuleAttribute</name>
<className>edu.iu.uis.eden.routetemplate.xmlrouting.StandardGenericXMLRuleAttribute</className>
<label>Request Firewall Change Is Urgent Rule Attribute</label>
<description>Request Firewall Change Is Urgent Rule Attribute</description>
<type>RuleXmlAttribute</type>
<routingConfig>
<fieldDef name="isUrgent" title="URGENT" workflowType="ALL">
<display>
<type>select</type>
<values title="NO">NO</values>
<values title="YES">YES</values>
</display>
<validation required="true" />
<fieldEvaluation>
<xpathexpression>//isUrgent = wf:ruledata('isUrgent')</xpathexpression>
</fieldEvaluation>
</fieldDef>
<xmlDocumentContent>
<isUrgent>%isUrgent%</isUrgent>
</xmlDocumentContent>
</routingConfig>
</ruleAttribute>
</ruleAttributes>
</data>
|
| Info | ||||
|---|---|---|---|---|
Naming conventions:
|
Create Rule Templates
Here we create several Rule Templates that are applied to each route node. Let's use <process name>.eDoc.<rule template name>.RuleTemplate to name our rule templates and <process name>.eDoc.RuleTemplates to name the associated XML file defining our collection of rule templates.
...