Search
-
Re: Postal Task for Orchestrator Runbook
-
Re: BUG: Add KB to related items of a SR created via an offering
-
Re: SCSM Integration Pack with Orchestrator 2016
-
Re: How to add app.constants.workItemStatuses
-
Re: Increasing the GridViewRecordCap to more than 500
With some of our earlier ROs, we had looked at the user picker but just could't justify it's use as it was clunky and not easy for end users as well as the load times (approaching over 20k users) were less than desirable. Perhaps others in the community will have a more elegant solution but within a larger environment it… -
Re: Service Manager - SQL Server High Availability query
It really depends on your business needs. We have running a two node always on SQL cluster supporting SM, SCORCH. DW database. Our SQL made use to use the same keys for SCORCH so fail-over and DR is not an issue. For our community size and needs we went with a design of the high performance DBs to run on local SSD's. The… -
Re: Some types of emails not getting imported. Any idea why?
-
Re: Logs or Powershell for tracking down a workflow?
-
Re: Advanced Request Offering ARO
-
Re: Custom Area in Views
I also use this same approach in some other places, such as "Incident Resolution Categoy". Something like "Auto Resolved by Problem" or "Resolved by Parent Incident" or similar type values are useful to have for workflows or scorch automation, but I like to prevent analysts from selecting them manually.