3.5.1.88 (Jun 29, 2012)

Enhancements
  • The AssetTrack procurement module is an existing feature that allows users to receive assets and consumable items against a PO. This release adds form designer support for this feature, so users who have purchased the module can design and modify PO receiving forms in the Console. 
  • The procurement module has been enhanced to work alongside CA APM. Data collected with PO forms can be selectively delivered to both APM and a procurement system like Peoplesoft, Oracle Financials, or SAP.
  • RFID scanning support added. Using the Motorola MC9090-G, you can scan RFID tags into a bulk form. (This is currently Ami-Mellon dev branch and is not slated to be included in GA)
  • License information is now stored in the database. The license key is still sent by AMI as a file, but once uploaded into AssetTrack, it is stored in the database.
  • On the server Settings page, there are new settings in the CA Service Management tab for specifying what extended field to use for population of Product Part Control Number during import.
  • Overage and Underage Validator can be added to the data policy of a Procurement form.
  • Overageand Underage Validator queries custom external data source or AssetTrack (if custom data source is not specified in the data policy settings ) for the number expected with the PO line item.
  • New handler setting for CA handlers (Service Desk, APM 11.3 and 12.6) to allow user to specify if the new asset validator should use the external repository or the AT repository for validation.
  • On the server Settings page, there are new settings in the CA Service Management tab for setting for APM 11.3 / 12.6 and Service Desk to allow import of only managed assets, only unmanaged assets, or both.
  • On the server Settings page, there are new settings in the CA Service Management tab for setting for APM 11.3 / 12.6 and Service Desk to indicate how to set the managed flag for publishing when the import setting is set to import both managed and unmanaged assets.
Notable fixes
  • XslHandler XML data was not providing values for Vendor.Tag nor the entire Stockroom node.
  • Installer was not using the ATUser sql credentials to run DB update scripts.
Have more questions? Submit a request

Comments

Please sign in to leave a comment.