Transaction number

The number of the upload transaction. The system assigns the next available number when a transaction is created.

	See Also

Mobile computer

The name of the remote computer from which the upload transaction was downloaded.

	See Also

Transaction date

The date and time that the user performed the action on the remote computer which created the upload transaction

	See Also

Class name

The name of the class of object involved in the transaction. For example, if the transaction is for a new work request, the class name is “Work Request”.

	See Also

Transaction type

The type of upload transaction: • Creation: A new instance of an object was created (for example, a new work request) • Modification: An object was edited (for example, a work request’s description was changed) • Deletion: An object was deleted • Method: A method was run on an object (for example, a work order task was closed)

	See Also

Method to execute

If the transaction type is method, this is the name of the method that will be run on the object in the master application. Note: This may be a method specific to processing synchronization transactions.

	See Also

Instance description

The title or description of the object being updated by the transaction. For example, the title of the work request that was edited.

	See Also

Instance object ID

The ID number of the object being updated by the transaction. For example, the number of the work request that was edited on the remote computer. Note: The upload transaction displays the ID number of the object on the remote computer, which may be different from the ID number the object has in the master database.

	See Also

Transaction status

The current status of the transaction. Possible statuses include: • New: transaction has been created but not yet uploaded • Waiting to be processed: uploaded to the master database, but not yet processed • Processed: processed successfully in the master database • Correction required: an error occurred when the system tried to process the transaction. You can attempt to correct the transaction and process it again.

	See Also

Success level

For processed transactions, displays whether the transaction passed or failed. If you accept an upload transaction that has an error, the transaction is marked as processed and flagged as failed. You might use this response, for example, for a transaction that failed because it was trying to cancel a task that had already been closed. Accepting failed transactions can lead to other failures, if following transactions depend on the failed transaction. This option should be used with caution.

	See Also

Comments

Text that identifies any adjustments that were made in order to process the transaction. If the data had to be adjusted in order for the transaction to be processed, the adjustments made would be identified here.

	See Also

XML

The XML code that describes the transaction. The system uses this code to re-create the transaction in the master database. Normally, this information is also read-only, but if a transaction has been flagged as “correction required” it becomes editable. This allows a knowledgeable person to correct the XML and then re-submit the transaction for processing.

	See Also

Distributor XML

If the transaction is for an object in a customized class that was created with a Distributor license key, additional XML code will be created on this tab. The system uses this code to re-create the transaction in the master database. Normally, this information is also read-only, but if a transaction has been flagged as “correction required” it becomes editable. This allows a knowledgeable person to correct the XML and then re-submit the transaction for processing.

	See Also

Customer XML

If the transaction is for an object in a customized class, additional XML code will be created on this tab. The system uses this code to re-create the transaction in the master database. Normally, this information is also read-only, but if a transaction has been flagged as “correction required” it becomes editable. This allows a knowledgeable person to correct the XML and then re-submit the transaction for processing.

	See Also