How to access 'Pending submissions' segment

1. Users can navigate to 'All Apps' report. Drill down into a particular application's report.

   

2. You can further access the 'Pending submissions' report/segment, via a dedicated CTA/option next to 'Download report' CTA.

   

📔

Updated: Failed API/AIC Submissions No Longer Appear Here

Workflow submissions initiated via API or AIC that fail are now classified under Failed — not Pending Submissions — and will appear across all applicable reports. This change improves visibility and reporting accuracy for API/AIC-initiated workflows.

Note: Failed submissions initiated through forms (not API/AIC) will continue to appear under Pending Submissions as before.

Which requests fall under 'Pending submissions'

1. A user might render the request form, and due to the following 2 options/user journeys, might skip submitting the request:
   1. Saves the request form in draft
   2. Tries to submit the form but fails to submit it successfully due to validation checks.
2. In such a scenario, an item ID/unique identifier is generated for the request, and categorises under 'Pending submissions'.
3. For each request/item, 'Last action' details are captured, which help identify what was the last action on the un-submitted request the user/requester took:

   1. Tried to submit request but failed

   2. Saved changes in draft

      

Pending submissions' overall impact on count

1. In Progress
   1. Pending submissions do not get categorised as 'In Progress' status.
   2. Hence, pending submissions' requests would not reflect under the 'In Progress' segment.
2. Total
   1. Pending submissions' requests logically have not been successfully raised/submitted by the requester.
   2. Hence in order to maintain the overall parity between count across statuses, 'Pending submissions' requests are not categorised under 'Total' segment.