The /atg/commerce/order/abandoned/AbandonedOrderService
is a schedulable service that has two important functions:
Storing the criteria that orders must meet to be identified as abandoned and lost.
Querying the order repository on a specific schedule for orders to identify as abandoned or lost.
The following table describes each AbandonedOrderService
property you may want to configure:
Property | Description | Default value |
---|---|---|
| The |
|
| The |
|
| The number of days that an order must be idle for it to be considered abandoned. | 7 |
| The number of days that an order must be idle for it to be considered lost. If | 30 |
| The minimum amount that an order must cost for it to be considered abandoned or lost (for example, “10.00”). Set this property to zero or leave it unset if you do not want to use order price as a criterion. Warning: If you do use | 0 |
| The Set this property to |
|
| The |
|
| The |
|
| The name of the scheduled job to run. |
|
| A description of the scheduled job. | Identify abandoned and lost orders |
| The schedule by which to run | every day at 3:00 AM |
| The |
|
| The client lock manager that should ensure that only one instance of this service is running at a given time. |
|
| The name of the global write lock that identifies this service. |
|
| The maximum time in milliseconds to wait for a lock. To wait indefinitely, set this property to zero. |
|
| The |
|
| The maximum number of items to include in a single transaction. |
|
| The number of batches of orders to fetch in a single transaction. |
|
| The number of batches or orders to process at once (1 batch per thread). |
|
| The maximum length of time to allow for the processing of a single batch. |
|