Stalled Transactions?

1 view
Skip to first unread message

Victor Congionti

unread,
Jan 3, 2014, 3:13:07 PM1/3/14
to openesig...@googlegroups.com
Not sure why were are getting these in our trans search but it appears some of our transactions are still in progress and are stalled. This shouldn't be the case as the transaction should technically be complete after the signer signs the contract located at a specific link. See attachment for details. 
trams-search.png

Open eSignForms

unread,
Jan 3, 2014, 4:57:42 PM1/3/14
to openesig...@googlegroups.com
If you start the transaction, but then don't complete it, it will remain in progress.  For transactions that are started by external users, you may find you want to have a custom logic action added to the package to cancel the transaction if it's not completed within a given timeframe (1 day, 1 week, etc.).  That will keep it from staying in progress and appearing as stalled.  See: http://code.google.com/p/openesignforms/wiki/ProgrammingGuide#Change_tran/party_status_action

If the transaction is active and no party is active, or if the party is active, but has no email address assigned (and it's not associated with a logged in user or assigned to a To Do party's group), it will be listed as "stalled".  If the party is still working on it, it's just a temporary thing and not really stalled, but if they close their browser, there's generally no way for them to return unless they have bookmarked the URL themselves.

Victor Congionti

unread,
Jan 7, 2014, 11:50:11 PM1/7/14
to openesig...@googlegroups.com
I'm in a bit of a crisis here. After following the directions I believe I messed something up. I have several transactions that should not be deleted marked for deletion even though I cancelled the custom logic. See attachments. 
custom.png
cancels.png

Open eSignForms

unread,
Jan 8, 2014, 12:23:12 AM1/8/14
to openesig...@googlegroups.com
That should not be a problem and just reflects the set cancel timestamp.  But since the transaction was completed, it will never be auto-canceled.  Basically, the cancel timestamp will take no action if the transaction is previously canceled or completed. 

Victor Congionti

unread,
Jan 8, 2014, 11:29:38 AM1/8/14
to openesig...@googlegroups.com
I followed the instructions for "Change tran/party status action" and I'm not sure if its having the desired effect. Instead of cancelling the transactions that have not been completed it appears to be cancelling the completed transactions as shown in the previous screen shot. Since I'm not sure if it was working properly I removed the custom logic and would like to get some clarification that I'm doing it correctly.

I think I'm not selecting the appropriate option for "When event(s) occur." Currently I have Transaction completed selected but I think it should be another status since when the transaction is completed it shouldn't be cancelled. Please advise!

Open eSignForms

unread,
Jan 8, 2014, 12:30:45 PM1/8/14
to openesig...@googlegroups.com
Yes, you are right on your assessment of putting it on the wrong event.  When an event occurs, the actions you specify will run.  Once the transaction is completed, you might send out emails, or HTTPS POST data to another system, but it's definitely odd to set an auto-cancel timestamp.

It never hurts to look at a transaction's activity log to see what happened and in what order.

If you look at your transaction listing, you will see what the status of each transaction is.  If it were canceled, the status would say this exactly.  Your transactions show the status of completed.  Even though you set an auto-cancel date in the future, because the transaction is completed, nothing will happen.

A transaction can only be auto-canceled if the date has been reached AND the transaction is still in progress.

For you, you want to set the auto-cancel when the transaction is started, not completed.
  Doesn't that make sense?  When the transaction starts, you want to set an auto-cancel timestamp so that if they don't complete it by that date, it will cancel itself.  Often you may even delete the transaction earlier than the standard retention for this scenario.  For multi-party transactions, you would more typically set the cancel timestamp on transaction start, and then cancel the auto-cancel when the first party completes the first document or completes them all.

Open eSignForms

unread,
Jan 9, 2014, 1:43:14 PM1/9/14
to openesig...@googlegroups.com
We will change the system so that when a transaction is canceled or completed, any prior auto-cancel date will be cleared to avoid the confusion of having a cancel date set when it's already canceled or completed.

was...@harvestglobal.com

unread,
Jan 26, 2018, 11:34:02 AM1/26/18
to Open eSignForms Developers
I tried changing the "When event occur" to other options like Transaction Completed , i get java.io.FileNotFoundException with status code 404 occurs .

was...@harvestglobal.com

unread,
Jan 26, 2018, 11:34:11 AM1/26/18
to Open eSignForms Developers
I have set When event(s) occur to Transaction started and url spec to my server via post method but when i checked View http send action there is nothing in it . i does'nt show up stalled or anything.
how can i configure Http send action to send data to my server through http send action. Just for reference i've Java in my backend code

Open eSignForms

unread,
Jan 26, 2018, 4:36:38 PM1/26/18
to Open eSignForms Developers
Perhaps you have posted your question using the wrong thread and you should start a new one...  It's unclear how this is related to the thread topic, nor do we understand the issue.

Where are you setting the event specification?  Who/where do you see a the exception?  I suggest starting a new thread to track your issue.

Open eSignForms

unread,
Jan 26, 2018, 4:39:35 PM1/26/18
to Open eSignForms Developers
Again, you have a different topic, but you are asking on another thread.  That doesn't help anybody else.  Can you start a fresh thread?

There's far too little information for us to help.  Can you share screen shots or the like of your HTTP Send Action setup?  What about the activity log and HTTP Send logs in the transaction details?  Is there nothing to help you understand what is going wrong?

You certainly can tie an HTTP Send Action to the 'Transaction started' event and it will send out data, but of course, at transaction start, I would not expect there to be much to send over as users have not yet interacted with the transaction's documents/data.
Reply all
Reply to author
Forward
0 new messages