(February 11, 2014)

New features
  • iOS Client - For those fields that have search ability (e.g Assignee, Location, Model), an active search query can now be cancelled, allowing the user to interact with the app again.
  • iOS Client - Camera scanner button is larger, making it easier to tap.
  • iOS Client - Turned off auto-correct on search input boxes.
  • API - Validation support added to /TaskData (POST) endpoint.
  • iOS Client - Added ResourceRules.plist file.
  • iOS Client - Validation support added (based on form configuration).
  • Windows Mobile Client - New Quick Sync feature added.
  • XslHandler - For Purchase Order forms, all assets collected against a single line item are passed to the XslHandler in one XML document. Prior to this change, each asset generated its own XML document, and the XSLT output file specification was called for each collected asset.
  • XslHandler - New handler setting, "Create individual files". Creates individual output files for each record published from the Console.
  • New Asset field, Assignee2, added
  • API - Organization field support added
  • iOS Client - Support for the Organization field added
  • iOS Client - Vibrate option. You can now turn Vibrate and Sounds on and off from the Settings popup
  • Form Design / Windows Mobile - Stockroom scan pattern support added. Look up by stockroom code for scanned value.
  • API - Stockroom field support added
  • iOS Client - Stockroom support.
  • Server - The top navigation's 'Help' link now points to the AMI Service Desk, which has links to see product documentation, submit a help request, and check open requests.
  • Import Service - File import pre-processor support added enabling AMI to develop custom PO file format importing for individual clients.
  • Import Service - Loose file import service setting added enabling the File Import Service to import partial data, putting records that can't be imported into the Error folder but importing the remaining records.
  • Import Service - File Import Service support for consumable flag on Purchase Order Line item file records added.
  • Import Service - Allow re-import of location/organization/assettype with change to externalid, enabling users to recreate location and organizations that have the same name is previously deactivated locations and organizations.
  • XslHandler - Configurable filename for XslHandler - Administrators can now configure the filename created by the XSL Handler, vs. the file assuming the name of the task used to create it.
  • XslHandler - Configurable use of time stamp in filename for XslHandler - Administrators can now configure whether the XSL Handler will add a time/date stamp to the output file name.
  • XslHandler - Configurable use of headers for XslHandler - Administrators can now configure whether the XSL Handler will add a header row to the output file.
  • Server - FX9500 Directionality/Multiple antennae support enabling users to specify different location and status values to apply to passing RFID tags based on the antenna that last read the tag.
  • Windows Mobile Client - Win Mobile PO Forms allow empty product, enabling users to receive line items without product information, using the PO line item consumable flag to determine if the line item requires serial numbers or not.
  • Form Design - Enable user to customize Older Data Exists in Queue validator in form designer.
Bug fixes
  • Importer - During Service Desk import, the output would say "Querying UAPM Extended Fields".  Corrected to "Querying Service Desk Extended Fields".
  • iOS Client, API - Look-up support  was failing for the Description, Service Status, and Line Item Number fields.
  • iOS Client - Date fields' collected values were changing slightly in the queue (due to time zone conversion issues).
  • Windows Mobile Client - When using Windows Authentication security, users who had successfully logged in once, were required to be connected to the network to successfully log in again. This cached authentication feature was mistakenly removed for Windows Authentication configurations. It is back in again.
  • Windows Mobile Client - When using Windows Authentication security, the Asset Track security setting for locking out a user after x invalid login attempts was not working.
  • Console - In the queue, performing a refresh does not remove records that may have been published by another instance of the console.
  • Windows Mobile Client - In some configurations, the Assignee's submitted field data was not correctly represented in queue. Usually this was triggered by autocomplete being turned off and entering the assignee code as the field value.
  • Windows Mobile Client - Long-running sync plans could corrupt the data base if the machine was suspended prior to the sync plan finishing. When a sync plan is run, the device is prevented from fully suspending (the display may dim, but the sync plan should still complete).
  • iOS Client - On a bulk form, if a field was one that required a field-specific search to populate (e.g. Location) and that field was never populated, the application should have submitted a blank value for the field. Instead, the app would submit data that resulted in the queue showing the collected asset's current value for that field.
  • Windows Mobile Client - When opening previously-collected purchase order data from "Tools" > "View Collected Data", and the "Save" button was clicked, the application would fatally except.
Have more questions? Submit a request


Please sign in to leave a comment.