...
Here we create a parent document type that defines the behavior of all Request Firewall Change documents. This particular parent document type defines everything short of routing paths. The idea is to allow for the possibility of other business processes called Request Firewall Change but might have different routing paths, validation rules, work groups, etc., but might use the same form, have the same super user work group, the same exception workgroup, etc. a hierarchy of child document types that inherit attributes of their parents.
Let's use the convention <process owner>.<process name>.eDoc.ParentDocType for naming Parent Document Types. Let's also use the same convention for naming the XML file.
| 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"> <documentTypes xmlns="ns:workflow/DocumentType" xsi:schemaLocation="ns:workflow/DocumentType resource:DocumentType"> <documentType> <name>cd.IET.AppDev.FirewallPolicyGroup.Workgoup.RequestFirewallChange<name>RequestFirewallChange.eDoc.ParentDocType</name> <description>eDocLite Request<description>Request Firewall Change eDocLite Parent Document Type</description> <label>eDocLite Request<label>Request Firewall Change eDocLite Parent Document Type</label> <blanketApprovePolicy>NONE</blanketApprovePolicy> <docHandler>${workflow.url}/EDocLite</docHandler> <active>true</active> <routingVersion>2</routingVersion> </documentType> </documentTypes> </data> |
...