Application Control Report Parameter Integrity Checker
Compare actual report parameter names with caller-supplied required and supported sets using normalized names, reporting omissions and unsupported extras.
Description
Report parameter completeness depends on which parameter names are supported, required and actually supplied.
Report parameter completeness depends on which parameter names are supported, required and actually supplied.1
This tool compares normalized name sets without checking parameter values or the generated report's accuracy.
When to use Application Control Report Parameter Integrity Checker
Use this tool to compare normalized name sets without checking parameter values or the generated report's accuracy.
How to use Application Control Report Parameter Integrity Checker and how it works
- Establish the observations, units, reference context and assumptions described below.
- Enter actualParameters, requiredParameters, supportedParameters and run the tool.
- Read complete, missingRequired, missingRequiredCount, unexpectedParameters using the meanings and sign conventions below.
- Correct any rejected inputs and rerun; independently review the result under the stated scope.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| actualParameters | Supplied parameter names; trimmed, lowercased and deduplicated. | array of string | Required; branch conditions below |
| requiredParameters | Caller-required parameter names on the same normalization convention. | array of string | Required; branch conditions below |
| supportedParameters | Nonempty supported-name inventory on the same normalization convention. | array of string | Required; branch conditions below |
Supply lists of supported, required and actual parameter names. Require every name be nonblank and the supported set nonempty. Trim and lowercase names, deduplicate each list, then sort missing required names and actual names absent from supported. Return complete only when both lists are empty. Required names are not separately required to be members of supported; an inconsistent inventory can therefore prevent completion. Values and report contents are not inspected.
missingRequired=sort(requiredSet-actualSet); unexpected=sort(actualSet-supportedSet); complete=(both sets empty) Use the stated ordering, units and branch conditions.
| Output field | Meaning | Value type |
|---|---|---|
| complete | Boolean completion result under the explicit rule above; underlying evidence is not verified. | boolean |
| missingRequired | Sorted normalized required parameter names absent from actual names. | array of string |
| missingRequiredCount | Number of distinct normalized missing required names. | number |
| unexpectedParameters | Sorted normalized actual names outside the supported inventory. | array |
{
"input": {
"actualParameters": [
"as_of_date",
"entity"
],
"requiredParameters": [
"as_of_date",
"entity",
"currency"
],
"supportedParameters": [
"as_of_date",
"currency",
"entity",
"segment"
]
},
"output": {
"complete": false,
"missingRequired": [
"currency"
],
"missingRequiredCount": 1,
"unexpectedParameters": []
}
}Limitations and assumptions
The result summarizes supplied audit observations under the stated arithmetic or checklist rule. It does not inspect underlying documents, select sufficient audit evidence, make a professional assurance judgment or establish regulatory compliance. Empty or all-true input can describe only the recorded assertions.
Supply explicit values and dense aligned arrays. Unexpected fields, wrong types and nonfinite scalar values are rejected; fixed-token, alignment and other branch conditions are explained above. A successful false flag, empty match list or unknown-evidence list differs from an input error. Extremely large inputs or nonrepresentable results may fail.
Alternative or Complementary methods
Use CAATS Full Population Testing Benefit Lookup for a related operation: Testing a full population still depends on data completeness, query controls, reconciliation and review.
Use Client Provided Schedule Reliability Foot-Tie Sampler for a related operation: Footing tests arithmetic within a schedule and tying tests its relation to a ledger total.
References
Similar or alternative tools
- CAATS Full Population Testing Benefit Lookup
Testing a full population still depends on data completeness, query controls, reconciliation and review.
- Client Provided Schedule Reliability Foot-Tie Sampler
Footing tests arithmetic within a schedule and tying tests its relation to a ledger total.