WORKFLOW SOFTWARE EVALUATION SCORECARD — YENRA
Guide: https://yenra.com/bpm-software/
Use the same process, synthetic data, roles, and cases for every candidate.
Agree mandatory gates before reviewing scores. Verify actual versions,
configuration, licenses, integrations, and operating responsibilities.

Process / trigger / output / owner / maintainer:
Expected volume and roles / service hours / data requirements:
Candidate / version / environment / configuration / test date:

MANDATORY GATE (repeat)
Requirement / pass criterion / observed evidence / pass or unresolved:
A failed mandatory gate cannot be offset by optional-feature scores.

CASES — record expected and actual result, evidence, effort, and gaps
1. Normal approval creates exactly one external test order.
2. Missing input returns clearly for correction and records resubmission.
3. Unavailable approver can be reassigned by an authorized person.
4. Timeout after external order creation recovers without a duplicate.
5. Restricted self-approval is denied under the intended permission rule.
6. Waiting/failed/parallel work follows the explicit process-version policy.

OPTIONAL CAPABILITY EVIDENCE SCALE (illustrative, not a product ranking)
0 absent or unverified; 1 described; 2 observed; 3 reproduced by our team.
Capability / score / observed evidence / configuration or custom work:
Maintainer / upgrade implications / extra license or service:

OPERATE AND EXIT
Monitoring, stuck-work diagnosis, support, backup/restore evidence:
Definition, record, attachment, and audit exports opened and inspected:
Missing export data or external dependencies:
Cost units, assumptions, recurring work, growth scenario, exclusions:
Required implementation work / owner / estimate / unresolved dependency:

DECISION
Mandatory gates passed / gaps remaining / planned pilot / decision owner:
References: OMG BPMN and current platform documentation linked in the guide.