You are viewing limited content. For full access, please sign in.

Question

Question

Override wait condition on Timer Catch Event

asked on March 4, 2021

Hi,

 

Is there a way for an Admin to override the wait condition on a timer catch event on a Forms process that was submitted?  I have a one-off situation where a user selected an incorrect future date that is used as a wait condition on a timer catch event.  I'd like to manually move her process forward without waiting for the date she selected to occur.  

 

Thanks!

0 0

Replies

replied on March 4, 2021

What version are you on? We recently released a "Skip" feature where you can move on to the next step. 

1 0
replied on March 4, 2021

cool!

0 0
replied on March 4, 2021

Jared,  I'm on version 10.4.  Is there a way to skip in this version?

0 0
replied on March 4, 2021

It was added in 10.4.2. 

0 0
replied on March 4, 2021

There might be others - but the two ways I know of:

  • Modify the configuration of the timer catch event to release the item sooner, then restart the Forms Routing Service (triggers timer to re-evaluate), then reverse your modification.  This has a risk of impacting other forms that get to the timer catch event during the time it is modified.
  • Modify the value that was submitted on the form in the database.  To do this, look at the process (like from the Monitor page) and determine which submission_id in the process added that date field (if you have multiple tasks and activities, you may have to look through them all to determine at which point the value was populated).  Then check the cf_bp_data table in the database for items with that submission_id.  You might be able to tell which field is is simply by the value, but if not, you would need to check some other tables to determine wihch attribute_id belongs to which field.  Once you determine which item it is, edit that value to what you need it to be (be EXTREMELY careful here to ensure you're only editing that one value, write a careful SELECT statement that returns that one value before modifying it to be an UPDATE statement, and make sure you backups are recent).  Once you have edited that value restart the Forms Routing Service (triggers timer to re-evaluate).  This has the benefit of only impacting the one form and no others in progress, but big risks of screwing up your database if you are not careful - PROCEED AT YOUR OWN RISK.
    • I heard that version 11 will have some ability to edit field values after submission, so that would elminate needing to edit this directly in the database - so that's something to look forward to.
0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.