Add Workflow Node to a KFS Document

Adding a workflow node means modifying .xml.

1. Verify the current workflow nodes. Go to Administration tab, Configuration column, Workflow section, Select Routing & Identity Management Document Type Hierarchy link. 
2. Show the KualiDocument Tab.
3. Search for the Document Type you plan to modify and note the workflow stops listed under the document.
4. Find the source code.

Modified (uconn) workflow .xml source can be found in uconn/db/upgrades/workflow.  Original workflow .xml source can be found in work/workflow.

                                001_kfs

                                002_kfs_core_parent_docs

                                003_kfs_core_module_docs

                                010_accounts_receivable

                                020_budget_construction

                                030_capital_asset

                                040_contracts_and_grants

                                050_effort_certification

                                060_labor_distribution

                                070_purchasing_accounts_payable

                                080_kuali_coeus

                                100_endowment

                                110_kc_integration

                                120_travel_and_entertainment

• To find the latest source, start searching in the uconn source. Begin from the last source .xml file moving up. If the document type you are modifying is not found in the uconn source, then use the original source.
• Verify all the workflow stops you noted above appear in the .xml file.
• Modify the source as needed by creating a new .xml file at the bottom of the uconn source for your modification.

5. Ingest the .xml file. Go to Administration tab, Configuration column, Workflow section, XML Ingester link.  Find your modified file, then press upload .xml data.

6. Verify the modified workflow nodes. Repeat steps 1 thru 3.

7. Modify the workflow attributes within the Document Data Dictionary .xml file. If uconn source exists, use that source, otherwise create a uconn override.

8. Find the role associated with the node and add entries (for testing). Press Submit button.  You will need to get the information needed for production before deploying the source code to prod.

Ex. Sub-Fund Reviewer = role 48

Ex. Accounting Reviewer = role 28

9. After modification (for testing) you need to clear cache to allow new configuration to take place. Go to Administration tab, Configuration column, Technical section, Cache Admin link. Check all the boxes on the left hand side and press flush button.