--- title: Integrating with Ivanti Neurons for Discovery (for ITAM On-Premises only) slug: neurons-for-itam/help/enu/latest/integrating-with-ivanti-neurons-for-discovery-for-itam-on-premises-only createdAt: 2026-07-06T09:08:30.361Z --- This topic describes how to integrate your local implementation of ITAM On-Premises with Ivanti Neurons for Discovery (accessed via the Ivanti Neurons Platform). Integration enables you to transfer data from Neurons for Discovery, such as device and invoice records, into your ITAM database. The transfer of data goes one way, meaning you can't transfer updated records back into Neurons for Discovery. :::hint{type="info"} At this time, **Installed software** information for device records is transferable from Neurons for Discovery, but **Licensable software** information is not. ::: ## Getting started Before getting started with the integration, make sure: - You're running ITAM On-Premises 2022.3 or higher. For details on setting up ITAM On-Premises, see [Setup](docId\:MF5NvRuMvJ5vSlSOR28gt). :::Paragraph{indent="1"} For existing ITSM customers, upgrade to ITAM by applying the latest ITAM content package (available from the [Ivanti Marketplace](https://marketplace.ivanticloud.com/?typesearch=C%23IvantiProvided+P%23AssetManagement)). ::: - You're licensed to access the Neurons Platform. - You have an Neurons for Discovery tenant set up with data you want to transfer. Next, follow the sections below, in the order listed, to complete the integration. ## Updating the UNO Landscape configuration This is a one-time update required to integrate with Neurons for Discovery. If you need assistance or details about the Neurons for Discovery tenant settings, contact Ivanti customer support. Before you can update the UNO Landscape, you first need to obtain URL and tenant ID values from the Neurons Platform. Obtain these values by following the procedure below. :::ExpandableHeading ## To identify the APIBaseURl and tenant ID needed for the UNO Landscape update 1. Log in to the Neurons Platform as Administrator using Chrome (or any other supported browser). 2. Click the browser's :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/VK2qXqGQ6etapIHvaQuMw_verticaldotsicon10x17.png" alt=" Vertical dots icon used to open a menu of available actions." caption size="10" width="10" height="17"} menu and open **More tools > Developer tools**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/o3FFe0tzdbHP9kE9jbMPg_apibaseurl.png" alt="The Developer Tools page used identify the values needed for updating the UNO landscape configuration." position="flex-start" size="88" width="877" height="343" initialPath="Images/APIBaseURL.png" githubPath="ITAM Help/Images/APIBaseURL.png" darkWidth="877" darkHeight="343" showCaption="false" indent="1"} 3. Under **Application > Session Storage**, copy the **baseServiceURl** value. This is the APIBaseURI value needed in step 3 of the next procedure. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/uZW2QtkiTAXlNt9NlHhRl_apibaseurl2.png" alt="Developer Tools page used to identify the baseServiceURI value." position="flex-start" size="91" width="908" height="454" initialPath="Images/APIBaseURL2.png" githubPath="ITAM Help/Images/APIBaseURL2.png" darkWidth="908" darkHeight="454" showCaption="false" indent="1"} 2. Under **Application > Session Storage**, copy the **tenantId** value (in the userName section). This is the UNOTenantRecId value needed in step 5 of the next procedure. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/XLmJt8UHc-Y26V-9vrSaj_tenantid.png" alt="Developer Tools page used to identify the Tenant ID value." position="flex-start" size="95" width="948" height="435" initialPath="Images/TenantID.png" githubPath="ITAM Help/Images/TenantID.png" darkWidth="948" darkHeight="435" showCaption="false" indent="1"} ::: ::::ExpandableHeading ## To update the UNO Landscape configuration 1. Log in to the ITAM tenant **CentralConfig** application as Administrator. If you need assistance accessing this application, contact Ivanti customer support. :::hint{type="info" indent="1"} If your ITAM installation doesn't currently display the Administrator user role, log in as Asset Administrator, then add the role via the Configuration Console > Roles and Permissions menu. For details [Setting up Roles](docId\:GT7R35F7DhfuezwDybAAO), see in the Configuring Ivanti Neurons for ITSM help. ::: 2. Open the **UNO Landscape** workspace. 3. Click **New UNO Landscape**, then enter the following values: - **Name**: Any identifiable name, such as "Neurons-OnPrem." - **APIBaseURI**: This is the Neurons Service fabric URL (without an http/s prefix) identified in the procedure above. - **Asset Import API URI**: This should be the same value as the APIBaseURI, also without an http/s prefix. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/flXCXiNjOpyD7Q5JbP0LJ_uno1.png" alt="Use the New UNO Landscape workspace to add information about the Neurons for Discovery tenant." position="flex-start" size="72" width="719" height="565" initialPath="Images/UNO1.png" githubPath="ITAM Help/Images/UNO1.png" darkWidth="719" darkHeight="565" showCaption="false"} 4. Click **Save**. 5. Open the **Tenants** workspace. 6. From the list, select the ITAM tenant where the data import from Neurons Platform is to occur, then enter the following values: - **UNO Landscape**: From the drop-down list, select the name created above in step 3. - **UNOTenantRecId**: This is the Neurons Platform tenant ID identified in the procedure above. - **UNOTenantURL**: This is the Neurons Platform tenant URL. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/KdQf4hg4AX_HGi6TRDd0S_uno2.png" alt="Use the Tenants workspace to select the ITAM tenant where the data transfer from Neurons for Discovery is to occur." position="flex-start" size="64" width="640" height="488" initialPath="Images/UNO2.png" githubPath="ITAM Help/Images/UNO2.png" darkWidth="640" darkHeight="488" showCaption="false" indent="1"} 7. Click **Save**. 8. Click the **Reset Tenant Cache** button (top right of page) to ensure that the updates will take effect immediately. :::: ## Setting up the app and client registrations Complete these procedures to enable the tenants for Neurons for Discovery and ITAM to communicate with each other. :::ExpandableHeading ## To set up app registration 1. Log in to the Neurons Platform as Administrator. 2. In the left navigation pane, click **Admin > App Registrations**. 3. Click **New Registration**. 4. From the New app registration drop-down, select **Ivanti Neurons for ITSM and ITAM**, then click **Continue**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/uuWw-gS5PxWFUYRYgq768_neuronsappreg1.png" alt="A drop-down menu used to set up new app registration on the Ivanti Neurons tenant." position="flex-start" size="100" width="1055" height="642" initialPath="Images/NeuronsAppReg1.png" githubPath="ITAM Help/Images/NeuronsAppReg1.png" darkWidth="1055" darkHeight="642" showCaption="false" indent="1"} 5. Add a meaningful description, such as "ITAM on-premises," then click **Register**. 6. Copy both the **Neurons Auth URL** and **Client ID**. (You'll need these for the next procedure when you set up client registration in the ITAM user console). ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/zSEFnswqb-L5W05Wcwbqn_neuronsappreg2.png" alt="To complete the new app registration, copy both the Neruons Auth URL and Client ID." position="flex-start" size="100" width="1052" height="644" initialPath="Images/NeuronsAppReg2.png" githubPath="ITAM Help/Images/NeuronsAppReg2.png" darkWidth="1052" darkHeight="644" showCaption="false" indent="1"} 7. Click **Finish and close**. ::: ::::ExpandableHeading ## To set up client registration 1. Log in to ITAM as Administrator. 2. Open the Client Registration workspace and click **New Client Registration** at the top. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/A1JDtPwFSSqh9oPOQ7ECI_neuronsclientreg.png" alt="Use the Client Registration workspace to complete client registration and validate the authentication." position="flex-start" size="50" width="498" height="292" initialPath="Images/NeuronsClientReg.png" githubPath="ITAM Help/Images/NeuronsClientReg.png" darkWidth="498" darkHeight="292" showCaption="false" indent="1"} 3. Add the following details from Ivanti Neurons: - **Name**: Any identifiable name, such as "Neurons." - **Is On Premise**: This option is selected by default—leave as is. - **Client Registration URL**: The Neurons Auth URL copied from the procedure above. - **Client ID**: The Client ID copied from the procedure above. - **Client Secret** isn't needed here and **VerificationUrl** will auto-fill in step 9 below. 4. Click **Save**. 5. In the upper right corner, click **Register Device** to register your ITAM tenant with Neurons. 6. A pop-up message displays, telling you to enter the URL into a web browser to finalize the registration. Copy this URL and click **OK**. 7. Open a browser and paste in the URL. (Log in as Administrator if prompted.) The following screen displays: ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/eEB-osJKuKg-Vip5pPZ-s_neuronsclientreg2.png" alt="The screen where you confirm client registration with the Neurons environment." position="flex-start" size="40" width="398" height="235" initialPath="Images/NeuronsClientReg2.png" githubPath="ITAM Help/Images/NeuronsClientReg2.png" darkWidth="398" darkHeight="235" showCaption="false" indent="1"} 8. Click **Yes, Allow**. "Success" will display if verification was successful. 9. In the Client Registration workspace, click **Get Token** (upper right corner). The **VerificationUrl** field should update. 10. Click **Save**. :::hint{type="info"} **Important**: You cannot access data discovered from Neurons for Discovery from more than one ITAM tenant at a time because of way app registration works—this is by design to prevent unauthorized access. The prior ITAM tenant ceases receiving data from Neurons for Discovery if the same Neurons for Discovery tenant is configured to communicate with another ITAM tenant. ::: :::: ## Enabling the ability to transfer data into ITAM Next, enable the ability to transfer data from Neurons for Discovery. Invoice transfers require an additional procedure to update a Web.config file. ::::ExpandableHeading ## To set up data transfers 1. Log in to ITAM as Asset Administrator. 2. Click the :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/wevvEsOtADDqOcTqHbPUf_configicon12x12.png" alt="Wrench icon Asset Administrators use to open the Configuration Console." caption size="10" width="12" height="12"} icon in the menu bar at the top of any workspace. The Configuration Console displays in a new browser tab. 3. In the left navigation pane, expand **Build > Global Constants**. 4. Scroll down the list to **EnableNeuronsSyncByAPI** and set the value to **True**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/XYn0au4bJ9cmx0JHorKcb_globalconstant.png" alt="Updating the global constants to set up device record transfers from Neurons for Discovery." position="flex-start" size="78" width="776" height="522" initialPath="Images/GlobalConstant.png" githubPath="ITAM Help/Images/GlobalConstant.png" showCaption="false" darkWidth="776" darkHeight="522" indent="1"} 5. Click **Save**. An Information dialog will display; click **OK**. 6. Expand **Configure > Cache Management**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/homHQTv-uTNuNN2rEw-mn_cachemgt.png" alt="Configuring cache management for the device record transfers from Neurons for Discovery." position="flex-start" size="88" width="881" height="316" initialPath="Images/CacheMgt.png" githubPath="ITAM Help/Images/CacheMgt.png" showCaption="false" darkWidth="881" darkHeight="316" indent="1"} 7. Click **Remove all cache items**, then click **Yes**. 8. Click **Reset cached validation lists only**, then click **OK**. :::hint{type="info"} **Important**: By clearing the cache and then resetting it, you can speed up the process for enabling the connection between the tenants. The data transfer may not work immediately if this step isn't performed. ::: Complete two final procedures: From the ITAM user console, open the **Asset Processor Configuration** workspace and enable the configurations as shown below: ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/cDrMxJqrnSNLT-N6kBBED_discoveryassetprocessorconfig.png" alt="Use the Asset Processor Configuration workspace to enable several configurations." position="flex-start" size="74" width="735" height="248" initialPath="Images/DiscoveryAssetProcessorConfig.png" githubPath="ITAM Help/Images/DiscoveryAssetProcessorConfig.png" showCaption="false" darkWidth="735" darkHeight="248" indent="1"} On the ITAM tenant, open the **IntegrationServiceHost.exe.config** file (located by default at C:\Program Files\HEATSoftware\HEAT) and do the following: - Update the **IsOnpremise** flag by setting it to **true**. The flag is case sensitive and should be in lowercase. - Restart IIS and the Integration service. :::: ::::ExpandableHeading ## To update a Web.config file for invoice transfers 1. On the ITAM tenant, open the **Web.config** file in the installation folder (located by default at C:\Program Files\HEATSoftware\HEAT\IMServer\IMServices\AssetProcessor). 2. Copy the data displayed below this section: :::Paragraph{indent="1"} **\** ::: :::Paragraph{indent="1"} For example: ::: `` `` `AQAAAN....AAAEAACAAAADQ6` `` `` `` 3. Paste the copied data into the **Web.config** file in the IvantiCloudDataProcessor folder (located by default at `C:\Program Files\HEATSoftware\HEAT\IMServer\IMServices\IvantiCloudDataProcessor)`. 4. Confirm **\
** is available in the IvantiCloudDataProcessor Web.config file. 5. Restart IIS. :::: ## Configuring the Neurons connector settings Finally, configure the Neurons Device and/or Invoice connector settings for importing the data into ITAM. Settings include data filters, field mappings, and the import schedule. This is a one-time configuration that is saved until you manually change it again. ::::ExpandableHeading ## To configure the Neurons connector settings 1. Log in to ITAM as Asset Administrator. 2. Click the :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/wevvEsOtADDqOcTqHbPUf_configicon12x12.png" alt="Wrench icon Asset Administrators use to open the Configuration Console." caption size="10" width="12" height="12"} icon in the menu bar at the top of any workspace. The Configuration Console displays in a new browser tab. 3. In the left navigation pane, expand **Extend > Integration Tools > Data Import Connections**. 4. Scroll down the list to **Ivanti Neurons Connector – Device** or **Ivanti Neurons Connector - Invoice**. Ensure the connector is **ON** and set to **Run Now**. Depending on the type of records you want to import (device or invoice), click the corresponding link to open and edit the connector. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/Y0vroeDSjOb_-0yiclsuO_neuronsconnector.png" alt="Configure the Neurons Device and/or Invoice connector settings for importing data from Neurons for Discovery." position="flex-start" size="80" width="1377" height="671" initialPath="Images/NeuronsConnector.png" githubPath="ITAM Help/Images/NeuronsConnector.png" darkWidth="1377" darkHeight="671" showCaption="false" indent="1"} 5. **Connection Setting page**: We recommend leaving the defaults as they are, although you can change as needed. Click **Test Connection** near the bottom of the page to verify that the connection settings work. It's important to test each connector that you're using. If the test connection fails, it's most likely a configuration issue and the data will not transfer into the ITAM database. Contact Ivanti customer support for assistance. 6. If the test connection is successful, click **Next**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/HNjlNTqbRjq_fhXgQhxHx_consetting.png" alt="Test the connector connection to ensure it works." position="flex-start" size="94" width="937" height="579" initialPath="Images/ConSetting.png" githubPath="ITAM Help/Images/ConSetting.png" darkWidth="937" darkHeight="579" showCaption="false" indent="1"} 7. **Object Mapping page**: We recommend leaving the defaults as they are, although you can change as needed. **Source mapping tables** is a list of populated tables based on settings defined on the previous page. **Batch size** is the number of records processed at a time for any given job. **Max size** is the number of records retrieved each time the connector queries the source database. **Root table** is the primary table containing the master data that defines all devices in your organization. **Unique key** uniquely identifies all devices in your organization. **Change-Time column** is not currently in use. 8. Click **Next**. 9. **Filter Setting page**: Click **Create Filter** to define optional filter conditions for the records you want to import. Based on the filters defined, only those devices or invoices will be imported from the source database. For example, you can choose to import an asset type of Laptop by creating the filter value **Laptop** as shown below. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/vrU-pkH4lq1wticduwZwe_filtersetting.png" alt="Create optional filter conditions for the records you want to import." position="flex-start" size="99" width="990" height="291" initialPath="Images/FilterSetting.png" githubPath="ITAM Help/Images/FilterSetting.png" darkWidth="990" darkHeight="291" showCaption="false" indent="1"} :::Paragraph{listStyleType="disc" indent="2"} In the left drop-down, select a field from the source database. ::: :::Paragraph{listStyleType="disc" indent="2"} In the middle drop-down, select an operator. In most cases, you’ll want to select **Equal**. ::: :::Paragraph{listStyleType="disc" indent="2"} In the field to the right, enter your filter condition. You can only add one filter per row. ::: :::Paragraph{listStyleType="disc" indent="2"} Use the AND/OR conditions as necessary and click the :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/YA2RGCC5KDyMa0AmWsAOY_greenplusicon12x12.png" alt caption size="10" width="12" height="12"} icon to add more filters to the list. To remove a filter, click the :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/tM6-6non9r2vPi6o7qrvf_redminusicon12x12.png" alt caption size="10" width="12" height="12"} icon. ::: 10. When finished, click **Next**. 11. **Field Mapping page**: Define how fields in the source database are mapped to fields in the target ITAM database. The left column displays source field names, the middle column displays transformation functions, and the right column displays target field names. It's assumed that the Source mapping names are known or identified in advance. For an overview of available functions, see (PDF). For guidance about target field mappings, see (PDF). ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/ZIUJmFXVh9uKuxb8QUUis_fieldmapping.png" alt="Define how fields in the source database are mapped to fields in the target ITAM database." position="flex-start" size="100" width="1017" height="547" initialPath="Images/FieldMapping.png" githubPath="ITAM Help/Images/FieldMapping.png" darkWidth="1017" darkHeight="547" showCaption="false" indent="1"} 12. When finished, click **Next**. 13. **Schedule Setting page**: Schedule when the connector will sync with the Neurons Platform to import data into ITAM. Available options are located in the Schedule List. You can select more than one schedule using the Ctrl button on your keyboard. 14. Click **Next**. 15. **Review & Publish page**: Click **Preview** to ensure that the mappings look as expected. Click **Back** to make any changes. When you’re satisfied with the results, click one of these options: - **Publish** to save your settings and run the connector at the schedule(s) you set. - **Publish & Run Now** to save your settings and run the connector immediately. With this option, you can monitor the data transfer in real-time. See the next section for details. - **Publish & Test Run** to conduct a test run of the connector but not save the records to the target ITAM database. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/88BuMW6h48k98Y_PSQSvh_reviewpub.png" alt="Preview the field mappings, publish the settings, and run the connector." position="flex-start" size="94" width="939" height="342" initialPath="Images/ReviewPub.png" githubPath="ITAM Help/Images/ReviewPub.png" darkWidth="939" darkHeight="342" showCaption="false"} :::: ::File{src="https://api.archbee.com/api/presign/parib0MC3hVoUNdfQdnac/MWvaKePsSMeQeP1XGsRYY_connector-field-mappings.pdf" label="Connector field mappings" initialPath="Connector-Field-Mappings.pdf" githubPath="ITAM Help/Connector-Field-Mappings.pdf"} ::File{src="https://api.archbee.com/api/presign/parib0MC3hVoUNdfQdnac/xj2L5dkaa5ClsHKwtYqf__connector-transformation-functions.pdf" label="Connector transformation functions" initialPath="Connector-Transformation-Functions.pdf" githubPath="ITAM Help/Connector-Transformation-Functions.pdf"} ## Confirming the data is importing correctly After integration is complete, you can view details about an import job as it's occurring. From the ITAM user console: - Open the **Integration Queue** workspace to monitor the job progress, which may take a while. Refresh the page as often as needed. You’ll see the status of the import job go from Queued to Running to Completed. The job will disappear from this workspace when completed. - Open the **Message Queue Journal** workspace to view incoming messages related to the transferred data. Click **Decompress Message** (top right of page) to view details about specific, discovered records. By default, this option is disabled. To enable it, see the **Troubleshooting** section below. - Open the **Integration Log** workspace to view any errors associated with the import job. If a job was successful, Stats display under **LogType**. When errors are encountered, Stats and ErrorStats display. Double-click **ErrorStats** to view a summary of the errors. Imported data will display in the correct workspace for the record type—devices display in **Hardware Assets** and invoices display in the **Invoices** workspace. You may need to refresh those workspaces before the data displays. :::hint{type="info"} At this time, **Installed software** information for device records is transferable from Neurons for Discovery, but **Licensable software** information is not. ::: ## Troubleshooting The **Integration Log** workspace may display an error during token renewal for the ITAM tenant. You can ignore this error or use the following workaround to prevent it from happening. ::::ExpandableHeading ## To work around a token renewal error 1. Log in to ITAM as Asset Administrator. 2. Click the :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/wevvEsOtADDqOcTqHbPUf_configicon12x12.png" alt="Wrench icon Asset Administrators use to open the Configuration Console." caption size="10" width="12" height="12"} icon in the menu bar at the top of any workspace. The Configuration Console displays in a new browser tab. 3. In the left navigation pane, expand **Extend > Integration tools > Web Service Connections**. 4. Scroll down the list to **Renew JWT for Neurons** and click the Edit :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/R-qoAlD9xyIucRFc206EQ_editicon13x12.png" alt="Edit icon used to edit certain fields within the user interface." caption size="10" width="13" height="12"} icon. 5. Click **Next** to open the Integration Script page. 6. Update the **Scripts** section with the following text: :::BlockQuote{indent="1"} console.log("Start : Token Refresh"); RefreshOnPremToken('RefreshTokenfromNeurons'); console.log("End : Token Refresh"); ::: ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/DmjR1yskBzwKmZTlJUUzG_integrationscript.png" alt="Update the web service connections to avoid a token renewal error." position="flex-start" size="100" width="1679" height="737" initialPath="Images/IntegrationScript.png" githubPath="ITAM Help/Images/IntegrationScript.png" darkWidth="1679" darkHeight="737" showCaption="false" indent="1"} 7. Click **Next** until you reach the Review and Publish page. 8. Click **Publish and Run now**. :::: The following tips address issues you may encounter when viewing the **Message Queue Journal** workspace during a data transfer. ::::ExpandableHeading ## To fix Invoice messages struck in a Dispatched state or marked as Timed Out Before updating the Web.config file in this procedure, make sure you make a backup of the original. 1. On the ITAM tenant, go to C:\Program Files\HEATSoftware\HEAT\IMServer\IMServices\IvantiCloudDataProcessor. 2. Open the **Web.config** file. 3. Under the **\** section, do the following: - Ensure there's only one element with an attribute binding of **NetTcpBinding\_IMessageQueueService**. If there are multiple elements, remove all except one. - Ensure the address attribute of that element is this address: **net.tcp\://localhost**:7200**/** :::Paragraph{indent="1"} For example: ::: :::BlockQuote{indent="1"} \ ::: :::Paragraph{indent="1"} You can use the host name/server name instead of localhost. Update the port number to 7200 if any other port is configured. ::: 4. Save the file. :::: :::ExpandableHeading ## To enable the Decompress Message option Enable this option to view details about specific records as they're being processed during a data transfer. 1. Log in to ITAM as Asset Administrator. 2. Click the :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/wevvEsOtADDqOcTqHbPUf_configicon12x12.png" alt="Wrench icon Asset Administrators use to open the Configuration Console." caption size="10" width="12" height="12"} icon in the menu bar at the top of any workspace. The Configuration Console displays in a new browser tab. 3. In the left navigation pane, expand **Build > Automation Tools > Quick Actions** to open the Quick Actions workspace. 4. Scroll down the list and click **Frs\_MessageQueueJournal**. 5. Click the **Quick Actions** tab. 6. In the left side panel, click **Decompress Message**. 7. Click **Edit** to open the Edit Expression window. 8. Add the **Device** type in the **Disable in UI when** expression field as shown below: ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/tPeLyCcFhCJBvTMllV0y3_decompressmessage.png" alt="Enable a Decompress Message option for the Message Queue Journal workspace." position="flex-start" size="90" width="1283" height="518" initialPath="Images/DecompressMessage.png" githubPath="ITAM Help/Images/DecompressMessage.png" darkWidth="1283" darkHeight="518" showCaption="false" indent="1"} 9. Click **Save**. :::