The Partwise Submit Trigger is a Webhook Trigger that activates in real time whenever a candidate saves and submits a section (part) of an application form. Unlike the full application submission trigger, this one ensures that client systems receive incremental data updates as candidates progress through the form, enabling step-by-step tracking and engagement.
For Manual Push via Application Manager:
Bulk Data Push Through Webhook/ERP – Allows users to push partwise submission data in bulk manually.
Allow Data Flow to ERP – Allows users to single-push partwise submission data manually.
When a candidate fills out a part of the application form and clicks Save & Next/Submit Part, the Partwise Submit Trigger gets triggered instantly .
The Partwise Submit webhook is fired immediately in the following scenarios:
Applicant Progress Submission: When a user submits a part of the application form via mobile or desktop.
Resubmitted Parts: When resubmission for any specific section is enabled in the Application Manager, and the candidate edits and re-submits that part.
View as Applicant: When a backend user fills and submits a specific part using the “View as Applicant” option.
Backend Preview Submit: When a backend user uploads and submits a specific section through the single-upload preview option.
A. Fallback Mechanism (Runs Every 30 Minutes):
If any partwise submission data is missed due to Meritto system delays, the fallback mechanism identifies the pending records and pushes them automatically.
B. Third-Party Failure Retry (Runs Once a Day):
Records that fail due to third-party API errors are logged and retried by the system once every day at 2:00 AM, ensuring that no partwise submission is permanently skipped.
All events are real-time first.
Fallback mechanisms ensure reliability against system delays or third-party failures.
Users can manually push partwise submission data for one or more applications from the Application Manager.
Step by Step Guide:
Select the webhook name in the Select Webhook Name dropdown.
In the Select Trigger Point dropdown, choose Partwise Submit from the configured triggers.
In the Select Application Stage dropdown, pick the stage against which the partwise data should be pushed. This ensures only matching records are sent.
Incremental Data Sync with CRM/Marketing Tools
Capture partially completed form sections in external CRMs to engage with applicants who have started but not yet completed the full application.
Progress Tracking in ERP/BI Tools
Feed partwise submission updates to ERP or analytics systems for monitoring completion trends, bottlenecks, and applicant behavior.
Conditional Workflows
Trigger specific workflows (e.g., counselor follow-up, automated reminders) when certain critical sections (like academic or personal details) are submitted.
Limitations
In the case of Partwise forms, the resubmission logic initiated from the Application Manager is not handled under the Partwise Submit Trigger. This is because the Application Manager resubmission flow is not designed for partwise forms .
However, if a resubmission is specifically enabled through the Partwise Configuration, any edits and re-submissions made by the applicant will be captured and the Partwise Submit Trigger will be activated accordingly.
The Partwise Submit Webhook Trigger ensures that every section of an application form is tracked and shared with client systems in real time. This incremental approach not only improves visibility into applicant behavior but also ensures downstream systems can act on partial data without waiting for full application submission.