When a community is configured to route approvals by Account Code, requisitions are directed to specific approval chains based on rules defined in the Rulesets tab. These rules determine which account codes trigger which approval workflows.
Management and Permissions
Only users with the Community Administrator or Approval Administrator role can manage these rules.
Note: To add an entirely new Rule (as opposed to a ruleset within a rule), you must contact your Unimarket Customer Success Manager.
Important Implementation Notes
Full Replacement: When you import this CSV, all existing rules for that specific ruleset are deleted and replaced by the content of the file. Always export a backup before importing.
Order of Operations: Rules are processed from top to bottom in the file. Ensure your most specific rules (VALUE/RANGE) are at the top, and your most general rules (ANY/Wildcards) are at the bottom.
Case Sensitivity: Matching for Single Value and Range is not case-sensitive.
Character Limits: Each part value has a maximum length of 25 characters.
Add An Individual Rulesets
Rulesets are processed from top to bottom. It is recommended to have a "Catch All" rule at the end of the list to handle any codes not explicitly defined.
- To add a ruleset, go to Administration > Approvals > Rulesets tab and select the rule name.
- Select Add Rule and the Add Rule pop-window will appear
- Complete all fields marked with a red asterisk. On the Format field is complete, the Part and Type field will populate to select the desired Type and configure.
| Match Type | Function | Usage Example |
|---|---|---|
| Any | Use this as a wildcard. It will match any value in that specific part of the account code. The Value, Lower, and Upper columns for that part should remain blank. | Routing all departmental codes to a single Finance chain. |
| Single Value | Use this for a specific match (e.g., Department 101). You must provide the exact string in the Value column. | Routing only account code "650" to the Finance chain. |
| Range | Use this to capture a series of codes (e.g., Accounts 1000 through 2000). You must provide both the Lower and Upper bounds. | Routing codes "723-750" to the Facilities chain. |
Sample Scenario #1: If the community desires to add any rulesets to their Finance approval chain. That is assigned to their Departmental Approvals (account code) rule. The user would action the following:
Sample Scenario #2: If the community desires to add rulesets 650 (single value) to their Finance approval chain. That is assigned to their Departmental Approvals (account code) rule. The user would action the following:
Sample Scenario #3: If the community desires to add rulesets 723-750 (range) to their Facilities approval chain. That is assigned to their Departmental Approvals (account code) rule. The user would action the following:
- Once completed, select Add. To add additional rulesets, select Add More.
Ordering Rules
Because rules are processed sequentially, positioning is critical. Use the up arrow to move specific rules above general ones or the "Catch All" rule.
Bulk Management (Import/Export)
Administrators can update rulesets in bulk using CSV files.
Export: Select the rule name > More Actions > Export Rules. Access the file via the "here" hyperlink in the Job Submitted pop-up.
Update the file using the CSV Column Requirements and Dictionary (below)
Import: Select More Actions > Import Rules and upload your updated CSV, by selecting Browse. Once completed, select OK.
CSV Column Requirements
The file structure depends on the number of "parts" in your account code.
Mandatory Columns:
Chain,Format, andPartType(e.g.,Part1Type).Values: If a part is set to
VALUE,PartValuemust be filled. If set toRANGE, bothLowerandUpperbounds must be filled.
Warning on Imports: Importing a ruleset file will delete and replace all existing account code rules within that rule with the contents of the new file.
CSV Column Dictionary
Here is the technical specification for the CSV file used to bulk import or export Account Code Approval Rules.
| Column Header | Mandatory | Options | Description |
|---|---|---|---|
| Chain | Yes | Existing Chain Name | The name of the approval chain to route to if the account code matches this pattern. |
| Format | Yes | Existing Format Code | The specific Account Code Format code this rule applies to. |
| Part1Type | Yes | ANY, VALUE, RANGE | Defines the matching logic for the first segment of the code. |
| Part1Value | No* | Text (up to 25 chars) | Required if Part1Type is VALUE. Matches a specific code. |
| Part1Lower | No* | Text (up to 25 chars) | Required if Part1Type is RANGE. The start of the matching range. |
| Part1Upper | No* | Text (up to 25 chars) | Required if Part1Type is RANGE. The end of the matching range. |
| Part2Type | Yes | ANY, VALUE, RANGE | Logic for the second segment of the code. |
| Part2Value/Lower/Upper | No | Text (up to 25 chars) | (Same logic as Part 1, applied to the second segment). |
| Part3Type | Yes | ANY, VALUE, RANGE | Logic for the third segment of the code. |
| Part3Value/Lower/Upper | No | Text (up to 25 chars) | (Same logic as Part 1, applied to the third segment). |
What's Next/Related
- You can also watch a short video on this process: