Jump to content

Steve G

Hornbill Developer
  • Content Count

    85
  • Joined

  • Last visited

  • Days Won

    7

Steve G last won the day on August 1 2017

Steve G had the most liked content!

Community Reputation

24 Excellent

About Steve G

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Hull, UK

Contact Methods

  • Website URL
    http://www.hornbill.com

Recent Profile Visitors

892 profile views
  1. Steve G

    CI linking to external site

    Hi @HHH , The requested integrations should now be available on your instance When adding an integration node to a workflow using the Hornbill Integration Bridge as the defined connector, you can now create, update or retrieve Ideas against your products in Aha! from your Hornbill workflows: Documentation for this integration can be found on our wiki. Let me know how you get on with these integrations! Thanks, Steve
  2. Steve G

    CI linking to external site

    Hi @HHH , Would you be using Aha! Ideas as "development proposals" in the Aha! platform? We could build integrations that are used within your Hornbill workflows, to create and update Ideas when requests raised in Service Manager reach a certain point in their workflow. And using the response from the Idea creation, you could then write a link to the Aha! Idea in the Service Manager request. Is this the sort of integration you're looking for? And are there any other Aha! integrations that you'd want us to take a look at? Thanks, Steve
  3. Hi @Keith, Sorry, I must've missed this post. Getting Flow to fire API calls off to Hornbill is fairly trivial (albeit not very elegant) with the HTTP action. Following this up with a Parse JSON action containing the relevant schema means that you can read/use the API response too. It's not pretty, but it works... Here's an example that will log an Incident in Service Manager, and how the HTTP and Parse JSON actions should be configured (with the instance name and API key hidden). This will make available the requestId, summary and warnings API output params available to the rest of your flow. The XML for the XMLMC call needs to be manually added to the body of the POST action, with details (summary and description) being populated using inputs to the flow: The JSON schema to parse the output of logIncident, as an example, is: { "type": "object", "properties": { "@@status": { "type": "boolean" }, "params": { "type": "object", "properties": { "requestId": { "type": "string" }, "summary": { "type": "string" }, "warnings": { "type": "string" } } }, "flowCodeDebugState": { "type": "object", "properties": { "step": { "type": "string" }, "executionId": { "type": "string" } } } } } Hope this helps, Steve
  4. @Lyonel Glad to hear we have a viable workaround I'll also track the issue, and when I get a spare couple of hours I'll see if I can replace the SQL driver with one that doesn't fall-over when IPv6 is thrown into the mix Steve
  5. HI @Lyonel, Looks like this may be an issue with the SQL driver library that I used in this tool. It appears to have an issue with SSO and hostname resolution in networks pushing IPv6 addresses. See this open issue for more details: https://github.com/denisenkom/go-mssqldb/issues/177 Could you change your config so that the value of "SQL Conf > Server" uses the IP address of the SQL host instead of its hostname, and give that a whirl please? Thanks, Steve
  6. Hi @Lyonel, Apologies for the late response, I'm currently on holiday so haven't been checking the forum regularly Looks like you've used the config supplied by @Victor, and within that authentication is set to SQL and not Windows. So if you've not supplied SQL credentials, then that is why the "database config not set" is being returned... Could you change authentication back to Windows and let me know if that works? If not then I'll try to get logged in tomorrow to take a look. Thanks, Steve
  7. Steve G

    Duplicated Assets

    @clampj, The h_serial_number column is in the AssetsComputer entity, not the entity you have defined, when trying to search for assets of type Desktop - which is why the API call is failing. You just need to change the Entity to AssetsComputer for the types where you want to search against the h_serial_number column. Hope this helps, Steve
  8. The details are here: https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.hornbill And a tutorial by Microsoft on how to use this is here: https://docs.microsoft.com/en-gb/azure/active-directory/saas-apps/hornbill-tutorial
  9. @Lyonel, Did you manage to get this working? Also, I've just released v1.5.0 of the database asset import tool which makes the UserName and Password fields non-mandatory when using Windows authentication (plus some other enhancements). Details on the wiki and the Github repo. Steve
  10. Steve G

    Duplicated Assets

    @clampj , How about now I had an epiphany last night and managed to fix this entirely in the tool, rather than having to make changes to Service Manager. The changes are documented on the Hornbill Wiki: https://wiki.hornbill.com/index.php/Database_Asset_Import As well as the Github page: https://github.com/hornbill/goDBAssetImport And the link for the new release (v1.5.0) download is here: https://github.com/hornbill/goDBAssetImport/releases/download/1.5.0/goDBAssetImport_v1_5_0.zip As a TL;DR, I've removed the AssetIdentifier and SQLConf>AssetID params from the tool config, and bundled these into an enhanced AssetTypes section: AssetTypes is now an array of objects instead of a flat object; Each object contains the following: AssetType - the Asset Type Name which needs to match a correct Asset Type Name in your Hornbill Instance (the left-string from the AssetTypes section of the previous release) Query - additional SQL filter to be appended to the Query from SQLConf, to retrieve assets of that asset type (the right-string from the AssetTypes section of the previous release) AssetIdentifier - an object containing details to help in the identification of existing asset records in the Hornbill instance. If the value in an imported records DBColumn matches the value in the EntityColumn of an asset in Hornbill (within the defined Entity), then the asset record will be updated rather than a new asset being created: DBColumn - specifies the unique identifier column from the database query Entity - the Hornbill entity where data is stored EntityColumn - specifies the unique identifier column from the Hornbill entity So for each asset type, you can now define how the tool should look for matching records - the source column from the database query, and the entity (primary asset entity or related asset details entity - specific to the class of asset you're searching for) plus entity column. Note - if the DB column is NULL (so if you don't have a serial number in a returned record for instance), then a new asset will be created - so please make sure you cater for this in your query. There are examples in the readme, and on the Wiki, but if you need any help just tag me in here and I'll take you through it. Hope this helps! Steve
  11. Steve G

    Duplicated Assets

    Hi @clampj @Victor I've just had a look at the code and this is a defect (well - an unfinished feature that's partially made its way in!). It's only searching against the h_name field in the Assets entity for existing records, hence why it never finds a matching asset in Hornbill and duplicates the record. It's not going to be a straightforward fix - it will definitely need changes to the Service Manager app as well as the import utility. There are complications due to the limited Asset fields currently defined as searchable, plus the fact that the serial number field doesn't live in the main asset entity - it's in an asset type-specific related entity. I'll have a think about the best way to handle this and will post back here when I have a solution. Thanks, Steve
  12. @Lyonel I'll update the Wiki to mention that, thanks. Looking at the code (as it was a LONG time since I wrote that ), those fields are mandatory, so I'll remove that in the next release when Windows is the authentication method. I've just stuck a letter "a" in my config for testing, and it does work ok. The connection issue is an odd one. What version of SQL Server are your asset records held on, and is it set to enforce encryption? If it's SQL Server 2008 R2 Service Pack 2 or above, can you try enabling encryption in the import tool SQLConf, and see if that helps? Encryption should only be set to false on SQL Server 2008 R2 or below, as they contained a defect with the handling of encrypted login records. Thanks, Steve
  13. Hi @Lyonel, I've just tested the latest version of the tool with Windows authentication to an MS SQL Server containing an asset database, and it works fine. What was the actual crash error message? One thing to note: the content of the username and password fields in the SQLConf section of the config are ignored if you choose Windows as your authentication method, as it actually authenticates using the Windows session account details that the tool is run within. So the account that actually runs the tool (either your account if you're running it locally, or the system, account used when scheduling the tool to run outside of an interactive session) needs access to your database. Just use empty strings for your values of Username and Password. Thanks, Steve
  14. Steve G

    Power BI Stopped Working

    Hi @JamieMews , I can't replicate this issue (although I am seeing another issue with the latest version of Power BI Desktop, which I'll come to). A quick search of the Power BI Community pages reveals that this may be down to antivirus software causing permissions issues between Power BI and your R installation: https://community.powerbi.com/t5/Desktop/R-with-Power-BI/m-p/344077 After updating my Power BI installation, I saw an issue where Power BI's security settings had been set to require approval for new native queries. This needed unticking before I could run any R script: Let me know if this helps, Steve
  15. Steve G

    Add ability to do wildcard request searches

    Hi @AndyHodkinsonPrincesIT, At the moment it is not possible to do first-character wildcard searches in the global search (you could search for S*62776 and this would return that request, but as you've raised, *62776 doesn't work). I've raised this with our development team who will look into the possibility of getting this added. In the meantime you can wildcard search in the request list Filter as so (as long as your selected views/filters allow the request to be seen): I hope this helps, Steve
×