Transactions and Tasks Abandonment

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    System Manager / DevOps  |   18.05 This feature was updated in 18.05.

When a user submits a form, Manager creates a transaction, associated with this form. As a result of transaction processing and user inputs, it can become completed or abandoned. Manager considers abandoned transactions as completed transactions, so they can be purged. Abandoned transactions can also be configured to deliver data depending on a threshold value, which determines how incomplete form data was before the transaction became abandoned. Manager stores abandoned transactions along with all other transactions that are part of the transaction life cycle.

Transactions can be abandoned automatically or manually.

Automatic Abandonment

Automatic abandonment can happen under varying conditions depending on your Manager configuration. Manager applies the following rules to govern when draft submissions are automatically abandoned. The rules use a set of data retention parameters that you may need to configure for your particular requirements.

Transaction Abandonment

Data retention policy, which determines how long a saved transaction is maintained in Manager before it is automatically abandoned. Forms with abandonment delivery can have a more aggressive abandonment policy than the standard 1 day (24 hours) policy.

Form Status Standard Abandoned Delivery
Open / Started Abandon after 1 day Not applicable
Background Saved

Abandon after 1 day 1

Abandon as per the form level No User Activity in Form Max Time setting. Transaction will then be delivered if the transaction score threshold has been exceeded.

Transactions which are rendered but never actually captured any data or transactions which are never saved by a user, even though they are background saved by Maestro Editor or using the Form.backgroundSave() Maestro API.

User Saved Abandon after data retention setting for Saved Transactions (days)2 Abandon after the data retention setting for Saved Transactions (days)2
Submitted Do not abandon automatically 3 Abandon as per the form level Submitted Transactions Max Time setting. Transaction will then be delivered if the transaction score threshold has been exceeded.
Expired Abandon 7 Days after expiry Abandon 7 Days after expiry

 

Note

1 - You can't change this 1 day abandonment policy time interval.

2 - Saved Transactions (days) can be set at the global, organization and form levels.

3 - Transactions in this state are mainly legacy. Normally, with a FTX flow, transactions will be completes before the transaction submits. When a transaction is left in the submitted state, it will be waiting for attachments or payments and the expectation is that help desk staff or administrators will be reviewing these transactions and either helping the users complete the form or manually abandoning them.

Task Abandonment

Tasks with configured expiration time are abandoned after this time has elapsed. If no expiration time is set, then the save abandonment time is used.

Form Status Standard Abandoned Delivery
Assigned / Open / Started Abandon after data retention setting for Saved Transactions (days) 1 Not applicable
Background Saved Abandon after data retention setting for Saved Transactions (days) 1 Abandon as per the form level No User Activity in Form Max Time configuration. Transaction will then be delivered if the transaction score threshold has been exceeded.
User Saved Abandon after data retention setting for Saved Transactions (days) 1 Abandon after data retention setting for Saved Transactions (days) 1
Submitted Do not abandon automatically 2 Abandon as per the form level Submitted Transactions Max Time setting. Transaction will then be delivered if the transaction score threshold has been exceeded.
Expired Expiry time overrides the above for Assigned, Open, and Started statuses and the tasks will abandon as per the expiry setting. Expiry time overrides the above for Assigned, Open, and Started and the tasks will abandon as per the expiry setting.

Note

1 - Saved Transactions (days) can be set at the global, organization and form levels.

2 - Transactions in this state are mainly legacy. Normally, with a FTX flow, transactions will be completes before the transaction submits. When a transaction is left in the submitted state, it will be waiting for attachments or payments and the expectation is that help desk staff or administrators will be reviewing these transactions and either helping the users complete the form or manually abandoning them.

Transaction and Task Purging

Form Status Date Record
Open / Started

Not applicable

Transactions which were abandoned from this state will be purged in a fixed 2 days
Abandoned / Completed It'll be purged as per the Finished Transaction PII Data (days) It'll be purged after delivery (if required) as per the Finished Transactions (days)

Note

For Collaboration Jobs transaction data purging is a per standard policy but transaction record purging is different and the record will be purged when the collaboration job is purged. Collaboration Job purging is controlled by the ‘Finished Collaboration Jobs (days) ’ data retention setting.

Manual Abandonment

There are situations when manual abandonment is required. It can come from:

  • A user via Workspaces
  • A system administrator via the Manager dashboard
  • A Fluent API call using the new TxnUpdater(txn).setFormStatus(Txn.FORM_ABANDONED).update() method. For more information, see Fluent API documentation for your specific Manager version.

Next, learn how to view submissions history.