Cancel Transactions
A ProcessEvents message with a NotifyWorkReconciledEvent can be used to cancel one or more transaction of bulk material in MineMarket.
When a transaction is cancelled in MineMarket, a reason code must be assigned. If the Cancelled Transaction Reason Code text list does not already include the B2MML Delete Transaction value, the value is added to MineMarket. This value is assigned to any transactions that are cancelled using the B2MML adaptor. Transactions cancelled via the B2MML adaptors do not display in the MineMarket user interface.
Note: Words in coloured text refer to node names in the XML file. Words in bold refer to field names or data in MineMarket, or required text strings. Words in italics refer to field values in MineMarket.
Subscriber Name
The subscriber name must be NotifyWorkReconciledEvent.
Class Name
The class name is BulkTrak.Integration.PublishSubscribe.B2MML_Classes.NotifyWorkReconciledEvent.
XML Example
Note: The following example has been simplified from the original. The example shows only the cancellation of a transaction.
<?xml version="1.0" encoding="UTF-8"?>
<p:NotifyWorkReconciledEvent xmlns:p="http://www.mesa.org/xml/B2MML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<p:ApplicationArea>
<p:Sender>
<p:LogicalID>PFPCS</p:LogicalID>
<p:ComponentID>TGM1</p:ComponentID>
</p:Sender>
<p:CreationDateTime>2022-12-05T18:26:41Z</p:CreationDateTime>
</p:ApplicationArea>
<p:DataArea>
<p:Notify />
<p:WorkReconciledEvent>
<p:DeletedJobResponseRecord recordTimestamp="2022-12-05T18:26:41Z">
<p:JobResponse>
<p:ID>TransactionAlias1</p:ID>
</p:JobResponse>
</p:DeletedJobResponseRecord>
</p:WorkReconciledEvent>
</p:DataArea>
</p:NotifyWorkReconciledEvent>XML Nodes
|
Node and Path |
Notes |
|---|---|
|
ApplicationArea » CreationDateTime |
If DeletedJobResponseRecord does not include a timestamp, this time is saved in each transaction's extended data in the Date7 field. If DeletedJobResponseRecord does include a timestamp, this time is ignored in processing. Note: If used, the time must be later than existing data in MineMarket. If the time is earlier than the Date7 field in the extended data of the transaction, no data is saved. |
|
DataArea » WorkReconciledEvent » DeletedJobResponseRecord |
The start node for the set of transactions. Can include a timestamp for the set of transactions. If included, this timestamp is saved in each transaction's extended data in the Date7 field. Note: The time must be later than existing data in MineMarket. If the time is earlier than the Date7 field in the extended data of the transaction, all data in this DeletedJobResponseRecord node is ignored. |
|
DeletedJobResponseRecord » JobResponse |
The start node for an individual transaction. |
|
JobResponse » ID |
The Alias1 of the transaction. Note: If a transaction with this Alias1 exists, it is cancelled. If the transaction does not exist, processing of the XML file fails and no data is saved. |
Notes and Troubleshooting
Nodes not described in the table above do not correspond to MineMarket data and are ignored in processing.
Multiple instances of nodes (with their sub-nodes) can exist within the one file:
- Multiple JobResponse nodes – For cancelling multiple transactions within a set of transactions.
When the B2MML adaptor processes the XML file, if one transaction causes an error, no transactions are saved.
