[AD Notes field available in ITOM]

@Sam P We have indeed, Ricky's raised that one with me directly, that's also on the list

Cheers,

Steve

[AD Notes field available in ITOM]

Hi @Sam P,

I've added this enhancement request to the list, will let you know when the team have implemented it.

Cheers,

Steve

[Integration Tools - Open Source?]

Hi @Martyn Houghton,

This feature is now in v4.3.0 of the Asset Import Utility:

It's documented on the Hornbill Documentation Library, which should be updated in the next 10 mins.

Let me know if this helps.

Cheers,

Steve 

[Azure Import Utility - invalid memory address]

Hi @Cristian,

This version of the utility was released back at the start of August, so it's unlikely that the 4.1.1 release caused the above issue. I've not been able to replicate your issue, but on reviewing the code it appears that this issue could be environmental, and caused by a problem with the HTTP proxy setting on the machine running the import.

I've made some changes to better handle that eventuality, and to output more useful debug information to the log in the event that this doesn't fix your issue, so we'll have more information to assist with the fix.

v4.2.0 is on GitHub now:

 

 

Let me know how you get on with this.

Cheers,

Steve

[Integration Tools - Open Source?]

Hi @Martyn Houghton,

The import utilities have been made closed-source as part of a wider strategy around security, API endpoint availability, and import usability improvements. We can't provide the code I'm afraid, but we could (and should, to be fair) add Shared With capabiities to the tool. I'll have the team take a look and get back to you.

With regards to the Wiki, my team are in the process of porting the data imports documentation from the wiki over to the new documentation platform, and references to open source in the content will not be ported.

Cheers,

Steve

[Catching a Webhook]

Hi @DRiley II, hope you're well!

Integrations into Hornbill from other platforms can only be done using the Hornbill API - we don't currently provide listener/target services for external webhook requests. There are lots of platforms which do provide webhook targets, that will allow you to make API calls into Hornbill when those are triggered though (Zapier, Azure Automations, Google Cloud Run, etc etc).

Hope this helps,

Steve

[LDAP Import - not working]

Hi @Malcolm,

That error would suggest you're either:

• Running the import as a different user that originally ran it 
• Running the import on a different machine that it was originally ran on

See the documentation for more information, specifically this bit:

Cheers,

Steve

[Line feed in request update]

@HHH,

If you set the input to Manual rather than Variable, then you get a multiline text entry which supports newlines, and a variable picker (button top right) to inject your field values:

Cheers,

Steve

[Python API]

Hi @RichardD,

The matchScope input param is your friend here, with a value of any (basically an OR) and each value set as its own exact match search filter, as follows   

xmlmc.AddParam("matchScope", "any");
xmlmc.AddParam("searchFilter", new List<XmlmcParam>() {
   new XmlmcParam() { Name = "column", Value = "h_status" },
   new XmlmcParam() { Name = "value", Value="status.onHold" },
   new XmlmcParam() { Name = "matchType", Value="exact" }
});
xmlmc.AddParam("searchFilter", new List<XmlmcParam>() {
   new XmlmcParam() { Name = "column", Value = "h_status" },
   new XmlmcParam() { Name = "value", Value="status.open" },
   new XmlmcParam() { Name = "matchType", Value="exact" }
});
xmlmc.AddParam("searchFilter", new List<XmlmcParam>() {
   new XmlmcParam() { Name = "column", Value = "h_status" },
   new XmlmcParam() { Name = "value", Value="status.new" },
   new XmlmcParam() { Name = "matchType", Value="exact" }
});

Cheers,

Steve

[You need the right 'app.h.searchEntityRecords' to perform this entity operation.]

@RichardD 

The role you're looking for is Hornbill Service Manager Integrations. This grants a number of entity and stored query privileges. NOTE - This role is only intended for accounts that are used for integrations or to perform data imports, and should not be applied to interactive user accounts.

Cheers,

Steve

[Python API]

Hi @RichardD,

searchFilter is unbounded, as per the API reference guide, so you can simply add another searchFilter element to the request as so:

elem = xmlmc.add_param("searchFilter")
elem.add_child("column", "h_name")
elem.add_child("value", "Asset00")
elem.add_child("matchType", "wildcard")
elem = xmlmc.add_param("searchFilter")
elem.add_child("column", "h_class")
elem.add_child("value", "computer")
elem.add_child("matchType", "exact")

You can use print_params() to review the request payload params before it's sent to Hornbill too, as you can see in this really basic example:

 

Hope this helps,

Steve
 

[Update Microsoft O365 integration to MS Id Platform v2]

@Gareth Cantrell This work is still ongoing, but we have deprecated the old Azure User & Group operations (that required the full Microsoft admin permissions) and replaced them with operations that require much fewer permissions to operate. Details can be found on the Hornbill wiki.

As and when more operations are replaced to use the new endpoints and fewer scopes, they will be published on the Announcements forum when released.

Thanks,

Steve 

[Unable to Manually Select Assessments in the BPM]

@Alistair Young 

Just to confim as discussed, this has been accepted as a defect by the development team and will be fixed in an upcoming update of Service Manager. Please check the release notes in the announcements forum for when this fix is deployed. 

Cheers,

Steve

[logServiceRequest - struggling with questionFieldMap and connectionMap]

Evening @samwoo,

I've just tested updating those custom fields using the Requests:update API, and it seems to be working fine:

On the right is the call I made in Postman to the API, with the XML payload & JSON content for the custom fields, and the left is the fields as populated by this call, so I'm not sure why it's not working at your end. 

Looks like you're using the HornbillAPI module, so it'd be worth outputting the content of the Get-HB-Params cmdlet to see what is actually being sent (before the Invoke-HB-XMLMC call, as that clears the params), should help with debugging.

Let me know how you get on.

Cheers,

Steve 

[asset_import.exe: You need the right 'app.h.executeQueries' in order to invoke the query: getAssetsListForImport]

Hi @SteveJM,

The role you need is Hornbill Service Manager Integrations. It appears that this role was missed from the Data Import Guides, I'll get that corrected.

Re: the KeySafe Key ID, as per the documentation, if you're importing from CSV files then KeySafe is not used and the value should be 0 or the property can be removed entirely from the configuration:

Thanks,

Steve

[Integration Request - Aha! Roadmap Software -]

@Martyn Houghton We've dropped some new operations in to do what you need:

 

Note, Create a portal user with employee permissions is actually just the Create a portal user API with the Permissions input set to true 

Hope this helps,

Steve 

[Integration Request - Aha! Roadmap Software -]

Hi @Martyn Houghton,

We'll take a look and get back to you.

Cheers,

Steve

[Azure iBridge Functionality]

@CraigP Microsoft have rebranded Azure AD to Entra ID, so you will find the operations you need in:

Microsoft > Entra ID > Groups

Cheers,

Steve

[You do not have a sufficient priv level to access this resource]

Hi @Rob Gething,

We've found and fixed the issue, this will be in a platform update during the usual release cycle so please keep an eye on the announcements forum for it appearing in the release notes.

As a workaround through, before you attempt to do the PUT, have your script make a call to one of the Hornbill service APIs to properly generate a session using the API key to ensure that the dav/session endpoint is available. I'd recommend calling the session:getSessionInfo API, and just disregard the response before performing the PUT request.

Cheers,

Steve

[Email update without request ID]

Hi @billster,

We do have a number of Hornbill to SolarWinds integrations in iBridge - check out the Premium Integrations section of the Solution Center on your instance:

 

To get SolarWinds to log/update/resolve incidents in Hornbill you would most likely need to use the Alerts HTTPS function within SolarWinds, and the Hornbill APIs to raise the tickets. We are not SolarWinds experts though I'm afraid so that question would need to be directed to your SolarWinds administrator.

Hope this helps,

Steve

[LDAP Import - Missing fields]

Hi @Malcolm,

these fields are no longer required, as the instance ID and API Key are now encrypted alongside your local copy of the import tool as of version 4 and above. Please see the First Run section of the documentation on the wiki.

Cheers,

Steve

[New Update: User Import - Database (v4.0.0)]

Hello everyone,

The latest update of User Import - Database (v4.0.0) has been released to live and is now available for download on GitHub.

The change log for this update is as follows:
 

Features

• Removed the requirement for plain-text API Key and Instance ID from being hard-coded in the config files - they are now encrypted client-side
• Removed the ability to store database credentials client-side, and instead store them securely in KeySafe
• New command-line argument (-creds=true) to check that that API Key has been entered correctly

Changes

• Included conf.json example in release archive
• Closed-source the tool, marked existing repo as private, added auto-publish to a new public repo: hornbill/user-import-database
• Improved logging output
• Updated GitHub workflow actions for posting release notes to the Hornbill community forums and internal workspace
• Removed support for macOS and Linux as we're using Windows cryptographic APIs to encrypt/decrypt the authentication details

[LDAP User Import failing with Errors]

@Ketan.lakhani 

This appears to be to do with LDAP configuration hardening at your end, rather that an issue with the tooling. See the following page for more information: https://support.microsoft.com/en-gb/topic/kb4034879-use-the-ldapenforcechannelbinding-registry-entry-to-make-ldap-authentication-over-ssl-tls-more-secure-e9ecfa27-5e57-8519-6ba3-d2c06b21812e

Cheers,

Steve

[New Update: Asset Relationship Import (v2.0.0)]

Hello everyone

The latest update of Asset Relationship Import (v2.0.0) has been released to live and is now available for download on GitHub.

The change log for this update is as follows:

Features

• Removed the requirement for plain-text API Key and Instance ID from being hard-coded in the config files - they are now encrypted client-side
• Added command-line argument (-creds=true) to check that that API Key has been entered correctly
• Moved the storage of the client-side database connection credentials into keysafe

Changes

• Closed-source the tool, marked existing repo as private, added auto-publish to a new public repo: hornbill/asset-import
• Removed support for macOS and Linux as we're using Windows cryptographic APIs to encrypt/decrypt the authentication details§
• Added code-signing to build process
• Added publish and release note automation in GitHub Workflow

[Asset Update Scripts]

Hi @Jim,

It's likely you've downloaded the source code zip (which does just contain the readme, as that's all that is in the repo now that we've closed-source the tools). You need to download the architecture-specific release zip, highlighted here in green:

Cheers,

Steve