Jump to content

Steve G

Hornbill Developer
  • Content Count

    559
  • Joined

  • Last visited

  • Days Won

    22

Steve G last won the day on March 5

Steve G had the most liked content!

Community Reputation

158 Excellent

About Steve G

  • Rank
    Senior Member

Profile Information

  • Gender
    Male
  • Location
    Hull, UK

Contact Methods

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

Recent Profile Visitors

2,551 profile views
  1. Hi @vhayer and @MattZ, Apologies for the delay in responding, I've been on annual leave. The issue here is that you're providing the entire URL to the web frontend for your instance in the instanceName variable, instead of just the instance name. So for example, if your instance was called myinstance, you are currently setting: instanceName = "https://live.hornbill.com/myinstance/" When this should actually read: instanceName = "myinstance" Hope this helps, Steve
  2. Hi @vhayer, That error is likely due to an incorrect value in the instanceName varible (row 2, attached), meaning that the script can't access your instance details to proceed: Note, the instance ID is case sensitive. Kind regards, Steve
  3. Hi @Martyn Houghton, The process would be: HTTP POST the file to the users session folder in dav, providing the API key in the header in the same was as you do for other API calls: https://mdh-p01-api.hornbill.com/yourinstanceid/dav/session/yourfilename.png Make an API call to apps/com.hornbill.servicemanager/Requests::attachFileFromSession as below to attach the file HTTP DELETE the file from the users session folder (same URL as above) <methodCall service="apps/com.hornbill.servicemanager/Requests" method="attachFileFromSession"> <params> <req
  4. Hi @AndyGilly, The preferred method to do what you need is: Write-Output "{{SISJobOutputParameterStart:MoverADGroups}}$($output){{SISJobOutputParameterEnd}}" Note the use of a subexpression $($output), this will ensure your variable is printed as you would expect, in the event it's not of type string. Cheers, Steve
  5. @AndyGilly The operation is now documented, here: https://wiki.hornbill.com/index.php?title=Active_Directory_User_Management Cheers, Steve
  6. Morning @AndyGilly, Great stuff There actually already is a Get operation in the AD User Management package, I just appear to have forgotten to document it on the Wiki... I'll correct that this morning! Cheers, Steve
  7. Hi @Jeremy, This would suggest your form is not submitting its data - e is an object that should contain the form response when your Form project trigger runs the onSubmit action: So this will be an issue with your Google Form configuration, probably in the project triggers... Cheers, Steve
  8. Hi @Paul Alexander, This would require a small change in Service Manager to be able to add this feature to the cleaner tool - I'll add it to the list, but if you're after a quick fix you could always export a list of references for the requests you wish to delete, and add them to the RequestReferences array in the cleaner config. With this set and CleanRequests set to true, running the tool will delete just those requests (and related records). Hope this helps, Steve
  9. Hi @BillP, There's a good example of how to manage this requirement within the LDAP Import tool, in the userImageUpdate function from the image.go file you have linked above. The process is basically: HTTP PUT the file into the session folder in dav, with the link (replacing yourinstanceid and thefilename as appropriate ): https://mdh-p01-api.hornbill.com/yourinstanceid/dav/session/thefilename.jpg Use activity::profileImageSet to apply the profile image, where sourceImage would be /session/thefilename.jpg HTTP DELETE the file from your session folder in dav, with the
  10. HI @Samantha Melville, The Intune to Hornbill asset import script can be installed via the Runbook Gallery in Azure Automation: Note, this requires the Hornbill modules to be installed from the Modules Gallery: Thanks, Steve
  11. Hi @AndyGilly, This is posssibly due to the default ErrorAction for the cmdlet in question not being Stop. I've seen examples where the error is output to the CLI and the script continues as normal, even when in a try-catch. If the cmdlet you are using supports it, then set the -ErrorAction Stop argument (either directly in the command line, or by splatting the param(s) in a hash table, example below). This will ensure the error can be caught and handled gracefully. try { $Params = @{ Name = $Name ErrorAction = "Stop" WarningVariable = "warnings" Wa
  12. Hi @AndyGilly, Yes, I've added this to the list. Will let you know when it hits the top Cheers, Steve
  13. Hi @AndyGilly, This is not WW environment specific, Windows servers restrict script execution by default. We've provided a Set Execution Policy operation in the Windows Management package that can be executed either side of the operation you wish to run so that the local machine or current user policy doesn't need to be left in a permanently relaxed state. So in a runbook for example, you could use the Set Execution Policy operation to relax the script execution policy for the current user, then execute your actual operation, then use Set Execution Policy to restrict it again. I exp
  14. Hi @Ieuan Payne IPO, As Gerry has mentioned, we already provide a few DevOps integrations via the iBridge, based around Releases and Work Items, but we could certainly add more. What are the specific DevOps features you are wanting to automate, is it just to run an existing pipeline or are there other requirements? Thanks, Steve
  15. Hi @AndyGilly, This error would suggest that the value provided to the SiteID input parameter isn't a valid, or accessible, ECM site. The operation basically uses the Set-Location cmdlet to set the execution location to the ECM site drive using the provided site ID, then uses the Add-CMDeviceCollectionDirectMembershipRule cmdlet (alongside a couple of other bits) to add the supplied device to the collection. The SiteID will be case-sensitive too, so it may be worth checking this first. Cheers, Steve
×
×
  • Create New...