About this Release

This release represents a major improvement to the ESB and major and minor improvements to the mobile application. 

Mobile Application Release Notes

Mobile Application Changes

ENHANCED Real-time Storage Location Update

ServiceMobility now allows a user's inventory storage location to be updated in real-time rather than requiring that user to clear cache and perform a User Data Refresh. This is done by modifying the user's storage location in the user record.  Performing this action will provide the following functionality:

• Replace the user's storage location in the back-office with the new storage location
• Migrate the inventory in the user's old storage location to the new storage location.  This occurs when the Options.MigrateInventory = true within the Users/ChangeStorageLocation REST API payload.
• Migrate all open inventory counts that are associated with the user's previous storage location with the user's new storage location.  This occurs when the Options.MigrateOpenInventoryCounts = true within the Users/ChangeStorageLocation REST API payload.
• Migrate all open Inventory Loads (Shipments) that were associated with the user's previous storage location to the user's new storage location.  This occurs when the Options.MigrateOpenInventoryLoads = true within the Users/ChangeStorageLocation REST API payload.
• Migrate all Open Stock Levels from the user's previous storage location to the user's new storage location.  This occurs when the Options.MigrateOpenStockLevels = true within the Users/ChangeStorageLocation REST API payload.
• Migrate Stock Levels Data from the user's previous storage location to the user's new storage location.  This occurs when the Options.MigrateStockLevelsData = true within the Users/ChangeStorageLocation REST API payload.

This is done by calling the Users/ChangeStorageLocation API.

NEW  ServiceMobility now provide the ability to exclude labor when a user checks the collect part deposit box within the action panel and has ordered parts associated with the work order.

This functionality is enabled by setting the WorkOrder.laborCoveredByDepositEnabled = true within the Mobile Configuration REST API.

NEW ServiceMobility now provides a feature to verify the Asset Model Number input by the technician against a list of valid model numbers.  This is controlled by the work order rule WorkOrder.Rules.Validations.AssetModelNumExists. When this rule is set to true, the technician must provide a valid asset model number when editing an asset.  In addition, a valid asset model number must be present for a technician to close a work order. 

The list of valid model numbers are input into the system using the Validation REST API.

NEW ServiceMobility has Introduced a tech notes extension to the work order API.  When tech notes are added to the work order utilizing this API, a system notification will be provided to the user. 

Note:  If techNotesPattern is provided within the mobile config, these tech notes will be validated against the pattern provided.

NEW ServiceMobility now provides the ability to utilize a regex to limit what information can be put into the remarks and tech notes fields.  This is setup via the WorkOrder.techNotesPattern within the Mobile Config REST API.

ESB Release Notes

NEW A new API for Tech Notes has been provided as an extension to the Work Order REST API (see above).

NEW ServiceMobility now offers a Validations REST API.  This initial implementation will allow organizations to input valid model numbers to be validated against within the work order process.

NEW ServiceMobility now provides a method to update a user's storage location and optionally migrate the following data via the User/ChangeStorageLocation API:

{
    "Options": {
        "MigrateInventory": false,
        "MigrateOpenCountRequests": false,
        "MigrateOpenInventoryLoads": false,
        "MigrateOpenStockLevels": false,
        "MigrateStockLevelsData": false
    },
    "StorageLocationID": "",
    "UserID": ""
}

Issues Resolved

FIXED Resolved an issue where when deleting an estimate on SFF was causing a new estimate to be generated and sent to the consumer.

FIXED Resolved an issue where the Inventory Load API (Shipments) allowed duplicate parts within a single shipment.

FIXED Resolved an issue where, in some cases, the Work Order purge process isn't clearing old work orders as mandated by the work order purge value settings.