User Retry (Magic xpa 3.x)
The User Retry behavior will not automatically rollback the transaction or data view, but will leave them and return the control to the end user, positioning the cursor on the record where the error occurred. User Retry is not applicable for physical tasks. The following table displays the errors that Magic xpa lets the end user recover from.
|
|
|
|
Incorrect Login
|
This is relevant for all task types.
In Runtime and Development modes, the login window opens for the end user to try to login again.
In Background mode, the login window does not open.
|
|
Duplicate Index
Constraint failure
Trigger failure
|
Online and Browser Client
Deferred Transaction – Only the flush phase is rolled back. The data view stays with the current values.
At Record level, Magic xpa stays on the record.
At Task level, Magic xpa stays with the task, and positions the cursor on the first record.
Physical
The transaction is rolled backed.
The data view is recreated
The cursor appears at the beginning of the current record.
At the Task level, Magic xpa stays with the task, and positions the cursor on the first record.
Not applicable for Batch tasks.
|
|
Record has been updated
|
Online
The data view will display the values after the update, and Magic xpa will stay on the current record. If the transaction is on the record, the record will be rolled back. If the transaction is on the task, the task will not be rolled back.
Not applicable for Batch tasks.
|
|
Locked Row
Table open failed
Table Create err
Table delete failed
Table copy failed
Commit transaction failed
Open transaction failed
Internal transaction err
Deadlock
Connect failed
Fatal err
Insert/Update/Delete failure
SQL execution err
Invalid SQL command
Invalid open Query Exp
Invalid table name
Table does not exist
Cannot modify R/O table
Record has been changed by another user
Record lost
|
Not applicable. Magic xpa never uses the User Retry option for these errors.
|
