Submissions | IMI Life Science

Submissions

Purpose: View, filter, and manage all form submissions across the platform in a unified inbox.

What You Can Do Here

  • Browse submissions: See all submissions in a sortable, filterable list. Unread submissions are highlighted.
  • Filter: Narrow results by form type, form name, date range, workflow status, read/unread state, or search by email and name.
  • View details: Click a submission to see the full payload, submitter information, and workflow execution timeline.
  • Mark as read/unread: Track which submissions you have reviewed.
  • Archive: Move processed submissions out of the active inbox without deleting them.
  • Add notes: Attach internal comments to a submission for your team.
  • Add tags: Organise submissions with custom tags.
  • Replay workflow: Re-execute the workflow for a submission — useful after fixing a workflow bug or when an external service was temporarily down.

Workflow Status

  • Completed: All workflow steps ran successfully.
  • Partially Failed: Some actions failed (e.g. Salesforce timeout) but the submission was saved.
  • Failed: The workflow could not execute (e.g. invalid definition).
  • Pending: The workflow has not yet run.

Tips

  • Submissions are never deleted — only archived. You can always find them using filters.
  • The workflow timeline shows each step with duration, success/failure, and error messages.
  • Use the “Replay Workflow” button after fixing issues to re-process failed submissions.

Submission Navigation and Recovery

  • Navigate: Forms returns to the directory. Edit form opens the editor for the selected form. Filters, pagination, and the opened submission are stored in the URL.
  • Filter: Use form, type, workflow status, email, read/archive state, and campaign attribution. Filter changes restart at page one. Previous results remain visible but actions are disabled while a new page loads.
  • Open details: View opens a linkable detail dialog. A failed detail request offers Retry.
  • Save notes: Notes can be edited or cleared completely. Failed saves preserve the entered text. Closing a detail with unsaved notes asks before discarding them.
  • Retry incomplete work: Retry workflow keeps completed checkpoints. Review failed external actions before queuing a retry.

Checkpoint Recovery and Attachments

  • Workflow state: Details refresh while Queued or Running. Review the final result and saved steps.
  • Retry workflow: Queue incomplete work after checking failed actions. Completed steps are retained and are not repeated. Completed or already active workflows cannot be replayed.
  • Unconfirmed outcomes: Interrupted external actions require provider and service-log review. Retry is blocked until the outcome is resolved.
  • Attachments: Download a submitted file from its detail using your authorized session. Attachment bytes are not public media URLs.

Configuration Quarantine and Private Lists

  • Configuration failures: Invalid saved definitions or journals become Failed and leave active discovery. Inspect the stored version and execution evidence before remediation.
  • Retained evidence: Completed checkpoints are kept. Malformed journals are not overwritten. Fixing the current published form does not rewrite an older submission version.
  • Temporary failures: Broker or database outages remain recoverable. A normal filtered exit is Completed rather than Failed.
  • Private files: Lists and details contain attachment metadata, not private base64 contents. Use the authorized attachment download action for file bytes.