CIID to AssetID Migration
: Behavior Changes

Asset association to a request will no longer be mapped to the CIID. Instead, it will be mapped to the ASSETID. Therefore, users will need to update the following:

1. Requests created through APIs or scripts with asset associations must be updated with the AssetID. To obtain the ASSETID, use the GET Asset API.
    
2.  Scripts used to update asset status using request json must be updated. If you've used a python script to update the asset status using the CIID from the request json, reconfigure the script to point to the ASSETID instead of the CIID.
   
   
    

CIID to AssetID migration related to ZReports

A new table Request Asset Map is introduced as a replacement for the existing Request Asset Mapping table. Use this new table to add new or re-create the reports which were created using Request Asset Mapping. A re-sync is required after a successful migration.

Other Behavior Changes
 

Associate Assets Pop-up:

• AssociateCIList.do popup is replaced with an API based Attach Asset(s) Pop-up in Request Form, Request Details Page, and Preventive Maintenance Task Form.

• The existing filter that lists Assets Owned by User, Assets Owned by the user's Department and CI Types is split into two filters.

    Filter-1: This filter will have two options i.e., Assets Owned by User and Assets owned by the user's Department. All assets will be selected by default.

    Filter-2: Product Types will be listed in this filter instead of CI Types. No product type will be selected by default which means all product types will be selected.

• The existing Site filter is changed to an API-based one. The site selected in the background (request/maintenance- form/details page) will be selected by default in the filter and assets will be listed based on that. Showing Site as Text-Box based on GlobalCOnfig is discontinued. Site Home Icon will not be available next to Site Filter. 

• Asset Bulk Select icon and popup will not be available when Request Form/Request Details Page is opened in previews built using iframe. (Ex: Request Details Page Preview in Kanban View)

• Users will be redirected to Asset Details Page instead of CI Details Page when clicking on the asset icon in requests details page properties and right panel.

• In Request API, the response for asset field will be array of Asset IDs instead of CIIDs.