Jump to content

Steve G

Hornbill Developer
  • Content count

  • Joined

  • Last visited

  • Days Won


Steve G last won the day on August 1 2017

Steve G had the most liked content!

Community Reputation

21 Excellent

About Steve G

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location
    Hull, UK

Contact Methods

  • Website URL

Recent Profile Visitors

807 profile views
  1. Hi @Dan Munns, Spotted the issue with your config. The input param names for all APIs in Hornbill are case sensitive, so serviceID should be serviceId, and catalogID should be catalogId. The following config worked for me, raising a Change Request every minute while it was running, with the summary, service and catalog item all correctly added: { "APIKey": "redacted", "InstanceID": "redacted", "Zone": "eur", "Schedule": [{ "Enabled": true, "CronSchedule": "0 * * * * 1-5", "ScheduleFrom": "2018-07-03T13:00:00.000Z", "ScheduleTo": "2020-01-01T00:00:00.000Z", "Service": "apps/com.hornbill.servicemanager/ChangeRequests", "API": "logChangeRequest", "APIParams": { "0": { "Type": "Content", "Parameter": "summary", "Content": "Some summary text" }, "1": { "Type": "Content", "Parameter": "description", "Content": "Some descriptive text" }, "2": { "Type": "Content", "Parameter": "serviceId", "Content": "568" }, "3": { "Type": "Content", "Parameter": "catalogId", "Content": "132" }, "4": { "Type": "Content", "Parameter": "catalogName", "Content": "Change Request Config Item" } } }] } Hope this helps, Steve
  2. Steve G

    Re-Index Knowledge Centre - Error

    Hi @Martyn Houghton, Apologies for the ambiguous description against those settings, but it's actually the HornbillITSM index that requires reindexing for the Knowledge Centre to function correctly, not the Knowledgebase index. Please select "All" when running this reindex, as each index document needs to include new columns, so a "New" reindex won't cut it. Also, please ensure that a Page Size of 10 is selected when you run this reindex. While I was looking at this issue, I also noticed that the reindex of your HornbillITSMTimeline index was cut short due to a platform update starting during the job. So once the reindex of HornbillITSM is complete, please start another reindex of the HornbillITSMTimeline, ensuring you select "New" (as you don't want to re-index everything that's already been done ), and keep a Page Size of 10. And once this is complete, all your request timeline posts and comments will then be searchable in the Global Search Let me know if you have any issues with the above. Thanks, Steve
  3. HI @Dan Munns, As per the API docs, you need to call one of the request type log request APIs, rather than the one you've selected (which is for internal use only): So to log an Incident, your service & API should be: "Service":"apps/com.hornbill.servicemanager/Incidents", "API":"logIncident", The rest of the config looks fine to me... Let me know how you get on. Cheers, Steve
  4. Steve G

    Hornbill Integration with Power BI

    Hi @MizeelA, This appears to be an issue with Power BI in the cloud not being able to authenticate against your locally installed Power BI Gateway, which is required when scheduling the running of reports that get data using R scripts. You need to check the configuration of your locally installed gateway and ensure that Power BI in the cloud can communicate and authenticate with this. See the following pages from the Power BI website for more information: https://powerbi.microsoft.com/en-us/blog/visualizing-and-operationalizing-r-data-in-power-bi/ https://docs.microsoft.com/en-us/power-bi/service-gateway-personal-mode Kind regards, Steve
  5. Hi @Dan Munns, That's done, and released to Github, with details & release download there and on the wiki page: https://github.com/hornbill/goSnowCloudAssetImport/ https://wiki.hornbill.com/index.php/Snow_License_Manager_Cloud_Asset_Import I've added the ability to switch on/off the adding or updating of discovered assets. Let me know how you get on with this. Cheers, Steve
  6. Hi @Dan Munns, Sorry I thought I'd already replied to this. The asset importer will update any assets it finds where the value contained within the field defined in the AssetID object in the config matches an asset value in Hornill, where the Hornbill table column is defined by the AssetIdentifier object in the config. So where the value returned by Asset.Name here: Matches a value in the main Hornbill assets table column h_name, as defined here: Which, if the AssetGenericFieldMapping is configured as so, should find matches on the second+ run of the import tool: So as long as the tool finds a match, and the operational or record state of the record (or indeed any of the other mapped columns) contains a different value, then the record will be updated. If no match is found, then a new asset record is created. Kind regards, Steve
  7. Hi @Dan Munns, Apologies for the late response, I've been on leave Great to see that you're using the tool and it's working for you! Yes this can be done in the tool, by setting the value of one (or both) of the following fields in the AssetGenericFieldMapping section of the config JSON, but this means you will need one JSON config file defined per record state being imported as the values will need to be hard coded in the JSON: h_record_state : this is the State field from the asset record, and will take the following integer values: 0 - Current 1 - Active 2 - Archived h_operational_state : this is the Operational State field from the asset record, and will take the following integer values: 0 - Operational 1 - Pre-Production 2 - Retired So if you include a state clause in your asset type filters to only return assets with a specific status (Status eq 'Active' for example)to match the hard-coded values set in h_record_state and/or h_operational_state, then you should see the correct statuses against the imported assets. In this example, all assets imported/updated by the tool using this config file would have a state of Archived and an operational state of Retired. I'll add support for record & operational status mapping in to the tool when I get chance, so you can roll these up in to the same config. Will let you know once that's available. Kind regards, Steve
  8. Hi @Dan Munns, As per the email I've just sent, a 404 error here generally points to an incorrect instance name being used. Could you check the instance name in the conf.json please, ensuring that it's correct, and in the correct case? Thanks, Steve
  9. Hi @Oscar Stankard, We are in the process of making a number of enhancements to how the request search works, but in the meantime did you know about the Ctrl+Shift+F shortcut? Hitting this button combination from anywhere within Hornbill will present you with a Quick Search box, allowing you to quickly get to a Request that you know the reference for. Just type or paste in a Request ID, and click Open Request to be taken straight to it Kind regards, Steve
  10. Steve G

    Hornbill CSV Asset Import

    Hi @samwoo, I've had a look at the CSV asset importer, and defined the h_location_type column to be populated using the locationType mapped column from a dummy CSV file, and the location type is populated correctly. So from the config file: And the CSV & resulting asset once the import has ran: I've also tried hard-coding the h_location_type value in to the config JSON, but still the field is populated as expected: So I'm not sure why your assets are not populated with the location type I'm afraid. If you want to PM me a snapshot of your CSV, and a copy of your import config, then I'll take a look and see if I can spot what's different for you. Kind regards, Steve
  11. Steve G

    Hornbill CSV Asset Import

    Hi @samwoo, The latest release of the CSV importer (v1.1.0), released on 04/12/2017, does include the executables, and is accessible from here: https://github.com/hornbill/goCSVAssetImport/releases/latest With regards to the Location Type, I'll have a look and see what's going on there as this field should be independent from the Location field. I'll let you know when I've found what's causing this. Kind regards, Steve
  12. Steve G

    Export List Defect

    @Dan Munns, I've replicated and fixed this issue, it'll be in the next Service Manager update. Kind regards, Steve
  13. Steve G

    Updating Existing Assets

    @dwalby, Yes, if the imports are configured correctly then existing asset records will be updated rather than duplicates created. Kind regards, Steve
  14. Steve G

    Updating Existing Assets

    @dwalby, As @Victor has suggested, you could do this with a report. We do have a story planned to add export functionality to the assets lists, so I'll add you as an interested customer to the story. Kind regards, Steve
  15. Steve G

    Updating Existing Assets

    Hi @dwalby @DeadMeatGF @DC-BEN, Yes, the CSV Asset Import tool can import new or update existing asset records from a CSV, and can be scheduled. Please see the wiki & github pages for more information: https://wiki.hornbill.com/index.php/CSV_Asset_Import https://github.com/hornbill/goCSVAssetImport Kind regards, Steve