Form Submitted Trigger: Does Not Include Cancellation

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

I wanted to share for others in case they’re searching for the answer to this (as it’s not explicit in the documentation).

The Form Submitted trigger does not fire if the form expires from the set duration. We were hoping to fire a workflow with two paths of logic depending if we got a response or not - so we’ll have to pursue another direction.

Here’s an idea if you support triggers for such actions: Form Expiration Trigger | SailPoint Ideas Portal

2

Thanks for this insight. I agree that expanding the triggers for each End State for the form would benefit us.

I would consider 2 options as a solution:

  1. Individual triggers for each end state.
  2. Single Trigger that has an attribute for the end state which can be checked. End States could be [FORM_SUBMITTED, FORM_CANCELLED, FORM_EXPIRED, FORM_ERROR]
1 Like
3

Agreed - option two would be a solid pathway as well.