Ensure that all of the order workflows contain the `cancelOrder`ruleset. For example:
1{2"name":"OrderCancel",3"description":"Order is Cancelled from admin console",4"type":"ORDER",5"subtype":"CC",6"eventType":"NORMAL",7"rules":[8{9"name":"{{accountId}}.core.SetState",10"props":{11"status":"CANCELLED"12}13},14{15"name":"{{accountId}}.order.SendEventForAllFulfilments",16"props":{17"eventName":"CancelFulfilment"18}19}20],21"triggers":[22{23"status":"CREATED"24},25{26"status":"RECEIVED"27},28{29"status":"BOOKED"30}31],32"userActions":[33{34"context":[35{36"label":"CANCEL ORDER",37"type":"PRIMARY",38"modules":[39"adminconsole"40],41"confirm":true42}43],44"attributes":[]45}46]47},
As you can see in the rulesettrigger section, Only `CREATED`, `RECEIVED`, or `BOOKED` status will enable the `orderCancel` feature. Therefore, the first record on the list must have the right status to see the checkbox:
An example of List that does not show the checkboxes
Here is an example where the first entry in the list is not in `CREATED`, `RECEIVED`, or `BOOKED` status:
Filtering the order list result
The user can filter the list by using the status:
Test bulk cancel
Select 2 entries and click the CANCEL ORDER button; a confirmation will be displayed. By clicking CONFIRM, both orders will move to `CANCELLED`.