Could you turn it into an (or set of) offering(s) then us the action processor to feed the relevant variables into a POST API? This would allow admins to make a modular script in the background for the service owners (etc.) to consume. This would allow you to define the mandatory and optional fields and use drop downs and system lookups to drive accuracy of the data coming in.We haven't done this in particular, but we do hold our offerings in the CMDB as items so that we can run lookups and expressions to provide a dataset to access through API and SQL.
Thanks for asking Software Craft and thanks for answering Kevin.I was just racking my brains over this one
Hi askey-s,Yeah we checked those. We have checked the system parameters, labels, local machine config, browser config and finally user preferences. All dates in the system are displaying correctly except this very specific location.
We are early on in our journey in this area too but have had some success triggering PowerShell based scripts from the Action Processor. Using Invoke-RestMethod and Invoke-WebRequest to trigger an Azure Hybrid worker runbook for some basic operational tasks.Edit - also dawned on me that we have some MS Teams webhooks receiving monitoring notifications. Function Invoke-TeamsAlert { [CmdletBinding()] Param( [Parameter(Mandatory = $true)][String]$Uri, [Parameter(Mandatory = $true)][String]$Title, [Parameter(Mandatory = $true)][String]$Text ) Process { [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 $JSONBody = [PSCustomObject][Ordered]@{ "@type" = "MessageCard" "@context" = "http://schema.org/extensions" "summary" = "$Title" "themeColor" = 'FF0000' "title" = "$Title" "text" = "$Text" } $TeamMessageBody = Convert
otherwise the user feels entitled to charge the approver directly. I suppose this depends on the type of approver. If said approver is part of their management structure then I would rather them chase directly than generate a call to the IT service desk. Though we don't do it ourselves, you could try triggering a REST post action from the Action Processor to take an action tailored for this purpose to show in the action history. By using the AP to trigger you would be able to be very specific about when it triggers (for example, when the decision is with the End User SVD). Something Similar to the example below….
Thanks Steve,We are a SaaS customer and do similar using the ETM PowerShell script provided by IFS (inporttool.ps1) for some of our regular imports (such as users and devices). However, Ive only managed to get this working on our on-prem infrastructure and I am being moved off into the cloud (at some point before November). I suspect there is something in in our cloud environment preventing the outbound traffic as it is also affecting Azure Automation account based API scripts. I will continue to work with my infrastructure team to investigate that one.I have thought about using something like MS PowerAutomate to convert the contents into csv data and send as a plain text email as an interim if necessary.
Thanks for the reply. I didnt think it was possible but I hold out hope for an enhancement.ETM Channel - Using attachment as a source | IFS Community
Under link type is there a ‘related help articles’ option to choose from? No. In my example we have created a ‘Catalogue Link Reason’ to separate services and knowledge for a smoother customer experience.Link Reason seems to drive the collections presented to the user and the wording of the sub-headers. Link type will drive the search functionality in the field below and the element that you are linkingI believe you could have a single link reason with both knowledge and offerings included if you wanted. We don't use it this way so here is a possible use case: Service Offering: Enhanced permissions account Link Reason: On-Premises Relation Type: Service Offering (Offering: Request a local admin account) Relation Type: Service Offering (Offering: Request an active directory admin account) Link Reason: Azure/ Cloud Relation Type: Service Offering (Offering: Request a cloud admin account) Relation Type: Service Offering (Offering: Request a cloud admin role) Relation Type: K
As nwest says, the article will needs to be published to assystNet users before it will appear. The other bits of config needed are…Catalogue Link Reasons:Example Catalogue Link ReasonLinks: (within the Service Designer -Offering Configuration)Example Service OfferingLink ConfigurationResult:Final result Caveat, I don't think I have missed any system parameters…
Hi Alberto,Do you mean like this? Linking predefined knowledge to your offerings?The Offerings Details Panel of the Service Designer - assyst11-5Wiki (axiossystems.com)
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.