Script repository
R
Rico Roodenburg
Current Situation
Currently, it is not possible to link an existing PowerShell script (from Automation) to a Product task action. Because of this limitation, you must copy and paste the script into each product individually.
Why is this an issue?
For auditing purposes, we want to make changes in TOPdesk (our ITSM platform) via their API. However, adding a separate script for each product is inefficient. Additionally, when TOPdesk updates their API, we would need to update the script in every product manually, which is time-consuming.
Workaround
As a solution, we can use an Automated Action in TOPdesk that is triggered by a webhook URL with Invoke-RestMethod. This way, the actions (such as creating and closing changes) are executed directly within TOPdesk.
Note: However, this workaround is not always possible for other products, so a permanent solution is really needed to address this issue properly.
M
Michiel van der Veeken
Hello Rico Roodenburg Thank you for your feedback. At this time, we have no plans to enable the reuse of PS scripts within our self service products. I understand your challenges; however, there are also some major drawbacks to making scripts reusable wich we have seen in the past. I will keep your feedback in mind if we start working on this topic (product actions) within HelloID.
If you're familiar with PowerShell and HelloID's API, it is possible to automate the creation and management of PS actions for products. This could help you avoid the need for repetitive manual scripting and updates.
R
Rico Roodenburg
Michiel van der Veeken thanks for your reply! I understand your concern, however maybe you can make the decision to make a PowerShell Modules repository only, instead of full PowerShell scripts repository.
Thanks for the API tip, I will consider it.