What’s new in Ivanti HEAT Neurons for ITSM/ITAM 2023.1?

With the Cherwell convergence (or as I call it, the return of the prodigal son) there are some very exciting features coming up in the 2023.1 Ivanti Neurons for ITSM/ITAM release, however experience dictates that it will take a few months to flush out the gremlins.

  • Visual Graphic Action Designer
  • Trusted Agent (Windows)
  • Webhooks (Insert)
  • Advanced Monitors Updates (alphanumeric ID, group business objects)
  • Simplified Expression Editor
  • Stored Prompts Enhancements
  • ITAM: Consumable Enhancements (assigned to financial owner or user)
  • Microsoft Teams Integration Enhancements
  • Other Feature Updates
    • Responsive Analyst improvements
    • Responsive Analyst fixes for localization
    • Analytic Metrics – label and percent options for Pie/doughnut chart
    • Self Service Chat Timeout removed from chat configuration workspace; analyst timeout is set to application timeout by default
    • Localization Workbench (BETA)

Seeking API Developer

Seeking Ivanti (HEAT) Neurons API Developer


  • API Development Experience Ivanti Service Manager (Powered by HEAT) aka Ivanti Neurons for ITSM
  • Attention to detail
  • Self Starter
  • Excellent Communication Skills


  • Configuration of Ivanti Service Manager and Ivanti Asset Manager as per Solution Design Specifications
  • Good understanding of Incident Management, Configuration/Asset Management, CMDB, Business Rules, Workflows, Service Requests, Request Offerings
  • API Development with AAD, DialPad

Apply Here

Ivanti Integration API Flat File Ivanti Project Implementation UK Ireland EU Australia New Zealand Canada US Consultant Developer Freelancer Ivanti Service Manager HEAT Neurons ITSM ITAM

Ivanti Integrations: Flat File or API?

Ivanti Integrations with Ivanti Service Manager (HEAT) aka Ivanti Neurons for ITSM/ITAM are a hot topic.

Since direct database connections are not available with cloud and the majority of customers are in the cloud vs on-premise, the questions is….

Flat File or API?

File-based Integrations have been around for a long time and for that reason are great not only for older and legacy systems but also because they are simply easy to create, maintain, and troubleshoot. Flat files are usually in CSV format, although some of you might remember the pipe delimited HAF files and heat structure files, I believe HSF. These files are scheduled typically daily, hourly, or as needed.

API (Application Program Interfaces) Integrations have been a buzz since they first emerged in 2005. Still a great buzz word thrown around in sales presentations. But are they worth the effort? API integrations require a much greater technical effort to create, maintain, and troubleshoot. Arguably once set up, the API should be easy to support. Key word is “should”.

APIs are secure and real-time. This is a clear advantage, but Flat Files too are secure and can be “near” real-time. Just schedule more-frequently and push flat files for time-sensitive needs such as HR Terminations for example.

Where the lines get blurry is with support, troubleshooting, and compatibility.

Flat files are straight forward, easy to support & troubleshoot, and compatible with legacy systems. Arguably flat files are backward and forward compatible provided the structure doesn’t change. If structure changes on either end of the system (Source, Target) then flat files and APIs need to be updated. Arguably Flat Files win here too because flat files are easy to maintain and support.

But are APIs forward compatible? What if the Application changes? The API changes too. There aren’t any API standards per se across different applications. Applications change, APIs therefor change too and then there are dreaded “bugs” or “features” Something you don’t get with Flat Files. Flat files are based on structure. APIs are code. Development.

Until Codeless Integrations are available, something Ivanti is rumoured to have in the works, the hands down winner for me is Flat File Integrations!

What are your thoughts?