This action retrieves the photo(s) associated with an applicant's National ID (NID) or child ID. It is used in workflows where verifying identity or displaying applicant photos is required.
{
"args": {
"fetchValueAttribute": [
"applicantNID",
"applicantChildId"
],
"fetchValueTypeAttribute": "applicantDocumentType.id"
},
"actionType": "FETCH_ID_PHOTO"
}
- Breaking Action: ✅ Yes, this should typically be a breaking action because downstream steps may rely on the photo being successfully fetched.
- Non-Breaking Action: ❌ No, it should not be non-breaking if photo verification is critical.
-
Trigger
- This action is triggered during workflow transitions where an applicant's photo needs to be retrieved, for example, for verification or document generation.
-
Execution
- The system fetches the photo from the applicant’s submitted documents based on the provided attributes.
fetchValueAttribute specifies which identifiers to use (e.g., applicantNID, applicantChildId).fetchValueTypeAttribute defines the type of document to fetch (e.g., the ID type).
-
Dependencies
- The applicant’s NID or child ID must exist in the system.
- The action may fail if the photo is missing or the document type is invalid.
-
Integration
- The fetched photo can be used in certificates, reports, or officer review forms.
- Example variable to use in templates:
${applicantPhoto} (or system-specific variable)
- Configure this as a breaking action to ensure workflow cannot continue without the photo if it is required.
- Optional: Combine with a notification action to alert officers when the photo is retrieved.
- Can handle multiple identifiers (e.g., NID and child ID) for more complex workflows.