Jump to content

Steve G

Hornbill Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


Steve G last won the day on December 15 2020

Steve G had the most liked content!

Community Reputation

149 Excellent

About Steve G

  • Rank
    Senior Member

Profile Information

  • Gender
  • Location
    Hull, UK

Contact Methods

  • Website URL

Recent Profile Visitors

2,432 profile views
  1. Hi @Ann, You could always access the CSV file using the Database Asset Relationship Import tool via an ODBC data source, and write the query as appropriate to your data. See the DBConf details on the wiki page you've linked above for more information: Thanks, Steve
  2. Hi @JoanneG, The errors are rights-based, so the user who owns the API key you are using doesn't have the correct roles to perform the operations, specifically this one: If you apply this role and try again, then this should be fine. Cheers, Steve
  3. Hi @samwoo, Yes, this will likely require a fair amount of work to achieve - I expect we'll need to cache all asset and extended information records from Hornbill into memory tool-side, then check each of the assets being imported against that cache. It's been on the to-do list to add this feature for a while though... I'll take a more detailed look in the new year and get back to you. Cheers, Steve
  4. Hi @Jeremy, Apologies for the late response on this. There's a utility node to escape strings ready to be inserted into JSON, this is what you need to use on the field in question before using the result of this node in your JSON: So without pushing the description through this node, and adding it in its vanilla state to the JSON, your output is (as you have seen): But preparing the string with the workflow utility before adding it to your JSON, and you get the desired result: Let me know if this helps. Cheers, Steve
  5. Hi @JoanneG, The decoding error is due to this erroneous comma in your config: Removing this comma would mean that just Change Request CH00006679 is deleted. Cheers, Steve
  6. Hi @samwoo, I didn't notice the Create/Update/Both request when doing the PreserveState etc feature, so I've added that into the tool, v1.12.0 contains that feature https://github.com/hornbill/goDBAssetImport/releases/tag/v1.12.0 Check out the OperationType property of the AssetTypes objects, you can set them to Both, Create or Update. Leaving the parameter blank (or indeed not even including it) will perform the previous logic (so Both ). Cheers, Steve
  7. Hi @samwoo, I've just released v1.11.0 of the DB Asset Import Tool, that supports preserving Status/SubStatus/Operational Status values for updating assets. Can be downloaded from here: https://github.com/hornbill/goDBAssetImport/releases/latest Check out the new PreserveState, PreserveSubState and PreserveOperationalState options in the AssetTypes definitions. Setting the Status to Active when assets are inserted is alredy possible, you just need to add: "h_record_state": "1", To the AssetGenericFieldMapping. Cheers, Steve
  8. Hi @Frank Reay, As assets are audited, this can be done with a report against the audit table. I've attached an example report definition, which can be imported into your Service Manager reporting in the admin console. Cheers, Stevedeleted-assets.report.txt
  9. Hi @AndyGilly, That's done, give it 5 mins and you should see the change on your instance. Note, rather than using the Could Automations to interact with Service Manager on your instance, you could use the Hornbill Automations to log new requests - which means you no longer need to provide an API Key in keysafe: Cheers, Steve
  10. Hi @Michael Risby, This was indeed a defect, which we've just fixed and released. Try it again on your instance in 5 mins or so and you should get the requested content type passed to your external endpoint. Let me know how you get on. Cheers, Steve
  11. No worries @AndyGilly. Nope, the process is all automatic, it can just take a few mins for the fix to be delivered. The next time you open your workflow/runbook designer, it should just work. Cheers, Steve
  12. Hi @AndyGilly, Apologies for any inconvenience caused, but this issue is now fixed and will be available on your instance in the next few minutes. Cheers, Steve
  13. Hi @m.vandun, This message just means that the report is already being run on your Hornbill instance, either from the admin tool or a script that has executed it. You can check the running status of a report in the admin console - it's on the Status column in the Report History tab. You (or your automated scripts) will need to wait until the current report run is complete before firing off another request. Cheers, Steve
  14. Hi @AndyHill, This is already possible using ITOM Runbooks. Cheers, Steve
  15. Hi @JamieMews, This is a known issue with reporting in the platform, which has been fixed and is awaiting release. As a workaround, we've updated the R scripts (and the Python ones too) so that they now support the use of XLSX report output. Please see the following post for details of the R updates: Kind regards, Steve
  • Create New...