Defining a Custom Workflow Selection

Procedure

  1. Make an entry of the workflow in the CONFIGURATIONDEFINITION table. Set the member ID of the organization for which customization is to be done. 
    INSERT INTO CONFIGURATIONDEFINITION(ID, "TYPE", OWNERID, GLOBAL, "NAME", SELECTOR, DESCRIPTION, DEFINITIONTYPE, DEFINITION, ACTIVE, MODMEMBERID, MODDATE, MODVERSION) VALUES ('<maxID+1>', 'PROCESSNAME', '1', 'Y', 'wfin26dqcatsourcev1.xml', 'WORKFLOW', 'Process for data source upload and import with DQ', 'File', 'standard/workflow/wfin26dqcatsourcev1.xml', 'Y', '1', TO_DATE('15-03-2006 04:01:00 pm','DD-MM-YYYY HH:MI:SS AM'), '1');
  2. If the DOCTYPE and DOCSUBTYPE are different (not provided out-of-box), make an entry in the DOMAINENTRY table with domaintype as DOCTYPE and DOCSUBTYPE. 
    INSERT INTO DOMAINENTRY(DOMAINTYPE, "VALUE", DESCRIPTION) VALUES ('DOCSUBTYPE', '<CustomValue>', '<CustomDescription>');
INSERT INTO DOMAINENTRY(DOMAINTYPE, "VALUE", DESCRIPTION) VALUES ('DOCTYPE', '<CustomValue>', '<CustomDecscription>');
  3. Log in to the application.
  4. Click the Business Processes link in the menu and select the Process Definition Selection rule. If the out-of-box condition is not as per the requirement, add a new condition provided in the templates.
  5. Create a rule through the rule creation menu using the DOCTYPE, DOCSUBTYPE, and custom workflow name parameters.

Result

Note: Rules are executed in order of definition. So, a default rule could override an explicit one, if it is placed first.

For example, if a default rule with DOCTYPE=Record Edit and DOCSUBTYPE=any is specified before an explicit rule with doctype=Record Edit and DOCSUBTYPE=Record, the default rule gets executed.