Steve G

Hi @Dan Munns, Good news I've just written and released a Powershell module for making API calls against the Hornbill platform. The Github repo for this module is here: https://github.com/hornbill/powershellHornbillAPIModule So your Powershell developers can now use this module, alongside the Hornbill APIs, to develop scripts to add or update your assets in Hornbill with AD as its data source. I'll be looking at automating the import of assets from a CSV in the near future, so watch this space... Kind regards, Steve

Hi @Paul Alexander, If you're a user of Microsoft Power BI, you could build your dashboards in there using Hornbill report data, and then share these to your Sharepoint users instead... Check out our Wiki page for mode details: https://wiki.hornbill.com/index.php/PowerBI_Reporting Kind regards, Steve

Hi @Dan Munns, Looks like the duplicate API call issue was actually down to a defect in the Go Cron package I used to build the scheduler (https://godoc.org/github.com/robfig/cron). It appears that an enhancement has been made to this Cron package to fix a timing issue that caused the intermittent duplicates (as well as a number of other bugs) since the last time I produced a release of the API scheduler. I've re-compiled the executables with the fixed library in place, and released as v1.0.3 to our public Github repository. The new zip containing these executables can be downloaded from here. Let me know how you get on with this new version of the tool Steve

Hi @Dan Munns, Hope you're well. I wrote the API scheduler, and haven't come across duplicate API calls generated as yet, but I'll take a look and get back to you. Could you send me your scheduler configuration file, with the API key removed, in a private message please? Thanks, Steve

Hi @nasimg, Apologies for the (very) late response to this query! I believe this issue has been fixed since your original post. I can no longer replicate this issue (see attachment). Kind regards, Steve

Hi @Lyonel, Apologies for the (very!) late response Just to close this thread off, this has since been fixed in a later version of Service Manager, so anyone running the cleaner against more recent versions of Service Manger won't be affected by this issue. Kind regards, Steve

Hi @lee mcdermott This is most likely due to the following system setting being set to off: security.database.allowSqlQueryOperation With this set to Off, the sqlQuery API is disabled by the platform. Switch this setting to On for the duration of the clean, before switching it back to Off again when the clean is complete. Hope this helps, Steve

Hi @Akash Savani, I've added support for Windows Authentication to the Database Asset Import Utility. You can find details of this release on our Wiki: https://wiki.hornbill.com/index.php/Database_Asset_Import And on the Hornbill Github: https://github.com/hornbill/goDBAssetImport I hope this helps. Kind regards, Steve

Hi @Sonali, When creating a new Workflow, its ID will be the Workflow Title, all in lower case, and any spaces replaced with hyphens. So, unless you've used underscores in your Workflow Title, your Workflow ID to populate that setting should be: camelot-standard-problem-bp-v1 Rather than the one in your screenshot above. Let us know how you get on with this. Kind regards, Steve

Hi @Dan Munns, I've not had chance to rewrite the areas of the tool to cater for this specific requirement as yet, but in its current form your Dev Team Admins could use it to do what you need by each having their own copy of the tool and adding their own Hornbilll authentication details to the config file. And for each on the fly import they could just amend the request type specific "Import":true/false and "SQLStatement" parameters as appropriate (setting the Import parameter to true depending on the class of request being imported, and by adding AND opencall.callref = callreferencenumber to the relevant SQL Statement parameter). It's unlikely that I will have any spare bandwidth in the next couple of months to work on updating the Supportworks importer to your specific requirements, but if I do then I'll certainly let you know once it's released. With regards to the free-text search, the global search bar allows the searching of request data using Lucene expressions. This does not include timeline or historical diary entry data at this point in time, but we do have conversations ongoing internally as to how this could be implemented. Kind regards, Steve

Hi @Dan Munns, Glad to hear the update to the scheduler worked for you. With regards to the Supportworks request import tool, there would be a number of changes required to be made to the code to support this requirement. As well as changes to the logic, there are security concerns about sharing the tool in its existing state to end users (Devs, or no Devs ), as it currently uses a username and password within the config to create a Hornbill session, so this will need converting to use API keys for session creation too before you allow end users to use this. It's certainly all doable, but not a particularly quick change, so I'll add this request to my to-do list and will let you know when it's done. In the mean time, it may not be ideal but it is possible to define specific requests to import in the SQL statements within the configuration file. So if your Dev teams could supply you with a list of requests that they want importing, then you could do this fairly quickly and on an ad-hoc basis. Steve

Hi @Dan Munns, Great to see you using this tool, and I hope that you're finding it useful! This was a defect in the utility, which I've just fixed and released v1.0.2 on our Github. The following is a link to the packaged release: https://github.com/hornbill/goAPIScheduler/releases/download/1.0.2/goAPIScheduler_v1_0_2.zip The documentation etc haven't changed, you just need to replace the executable with the one in the zip. Let me know how you get on with this update. Kind regards, Steve

Hi @Tina.Lapere, I've added an activity to the Change Request to remind me to post back here once the functionality has gone live Kind regards, Steve

Hi @DeadMeatGF @DC-BEN, No, the tool will only connect to MySQL, MariaDB or MSSQL data sources. Steve

Hi @PSG, We are currently developing functionality to allow Portal (Service and Customer) users to cancel their own Service Requests in the event that the request is no longer required. Access to cancel Service Requests via the portal will be controlled by system settings and user permissions. As this is in development, please keep checking our update notes within the Admin console for when this functionality is available! Kind regards, Steve

Improved logging capabilities have been added to the Database Asset Import tool, details of which can be found on our Github: https://github.com/hornbill/goDBAssetImport And Wiki page: https://wiki.hornbill.com/index.php/Database_Asset_Import Kind regards, Steve

Hi @DeadMeatGF, I've fixed this issue with the asset import tool, and this is now live as release v1.3.0 on our Github repository: https://github.com/hornbill/goDBAssetImport I've also added improved logging capabilities too the tool, as requested in the following post: Let me know if I can be of any more assistance! Steve

Hi @Melissa Gurney, Thank you for the post! With regards to your question, we don't actually have a tool that imports assets directly from Active Directory. We have one that takes input from a SQL (MySQL or SQL Server) database, which I presume is the one you are using? The DB asset import tool does include logic to ensure that, if correctly configured in the JSON, you should have no duplicate assets in your database when using this tool. Could you please Private Message me a copy of your configuration file so that I can see if this is configured as required? Many thanks, Steve

Hi @DeadMeatGF, Thanks for posting! Firstly, from within your admin console, could you please delete the API key that you've been using to perform these imports, as you've posted the config file with this key to this public forum. We've removed the config file from the original post for you. I've not come across this issue before unfortunately, and have run dozens of imports from SCCM data. The config looks good to me, there's nothing obvious in there to point to why this would be failing some times and not others. What is the last line written to the log file before the tool ends? I've had a look at the code and there are areas within the tool where we could increase the level of logging to help debug what is happening to cause your import to fail. I'll update the Go code and provide another binary with advanced logging. Once this is done, I'll post the link to the Github release here so that you can download and give it a whirl, and feedback results. Kind regards, Steve

Hi @Ralf Peters The ,\"$$hashKey\":\"object:xxxx\" values are not required by the taskCreate2 API, these are object identifiers added by the Hornbill web application framework and not used by the API. So your example above could be re-written as: "Type":"Content", "Parameter":"extra", "Content":"{\"checkLists\":[{\"value\":\"To Do\",\"children\":[{\"value\":\"Ash Room\",\"checked\":false},{\"value\":\"Oak Room\",\"checked\":false},{\"value\":\"Hawthorn Room\",\"checked\":false}]}],\"files\":[]}" With regards to the CronSchedule parameter, this accepts any standard Cron expression. So in your example, this would raise a task every hour on the hour on Tuesdays and Thursdays. Kind regards, Steve

Hi @Reena Mahatma, This is configured on a per Service & Request Class basis. Please see attached image for loction of this configuration parameter. Kind regards, Steve

Hi @Kelvin, There is a button to the right of the BPM display on the affected requests (see attached image). Clicking this will attempt a re-run of the failed workflow node. You need to have the Service Desk Admin role against your user account to be able to access this button. Kind regards, Steve

Hi @Kelvin, Were the Change Requests that are affected by this issue raised prior to you upgrading to Service Manager v2.36.5? And are new Change Requests also affected by this issue? The reason I ask is that we fixed this issue in v2.36.4, which was released on Wednesday morning (this week). If this is just affecting Change Requests raised prior to the 2.36.4 release, then the workflows will need to be restarted on the affected requests to retry the failed node. Kind regards, Steve

Good afternoon @Martyn Houghton, We've just released patch 2.36.5 to live, which includes the fix for the assignTeamOwnerCreator issue. Please feel free to upgrade to this patch at your convenience to take advantage of this fix. Kind regards, Steve

Hi @Martyn Houghton, This is another BPM defect, and wasn't directly related to (and not reported with) the issues from yesterday - although it does appear that it was present yesterday too. This issue is only affecting workflows that contain an Assignment > Assign to Requets Creator. I have fixed this issue, and it's currently being tested for release in another patch. I will let you know as soon as I have a timescale for deployment. Kind regards, Steve