Issue with Transfer order Line stage processing in OOB BR "Push Status to Asset/Consumable" due to "Transfer order Line SM core" workflow - Known Error

Issue with Transfer order Line stage processing in OOB BR "Push Status to Asset/Consumable" due to "Transfer order Line SM core" workflow Description The BR 'Push Status to Asset/Consumable' does not handle the pushing of the related asset's substatus correctly when the workflow "Transfer order Line SM core" is installed in the instance.

When the TOL stage is in In transit, Asset state is in Pending Transfer, instead of In Transit, Reserved state. This creates issues with other TOL's taking the asset that should be reserved.

Steps to Reproduce

1. Hop to instance with Asset Management and CSM Core installed. 2. Create a new transfer order (alm_transfer_order). 3. In the related list of the TO, create a new Transfer Order Line. Pick an asset some suitable locations to send and receive from. In the 'Request Line' field pick an RITM to relate to. Save. 4. Open the related Asset record in a new tab/window for reference as the workflow progresses. 5. In the TOL record related list change the state of the 'Ready for fulfillment' TOLTASK record to 'Closed Complete'. This generates 2 new tasks in the related list. 6. Close as complete the 'Prepare for shipment' task and the 'Ship' task. 7. TOL stage is now 'In Transit', asset should be 'Reserved' and 'In Transit' but it's still showing as 'In Stock' and 'In Transit'.

Workaround The Push Status to Asset/Consumable business rule can be updated with the below snippet.

var taskGr = new GlideRecord('alm_transfer_order_line_task'); taskGr.addQuery('transfer_order_line', current.sys_id); if (SNC.AssetMgmtUtil.isPluginRegistered('com.snc.service_management.core')) taskGr.addQuery('state', 'IN', '3'); else taskGr.addQuery('state','IN','3,7'); taskGr.orderByDesc('order'); taskGr.setLimit(1); taskGr.query();

https://instance.service-now.com/nav_to.do?uri=sys_script.do?sys_id=f91707ab37e3100044e0bfc8bcbe5d79

This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.