Mario

Hello Team Pulseway! Can we assign a ticket to a custom queue by scanning keywords in the subject line? For example, we have made some custom queues for Hardware, Email issue, Epicor, etc. and would like to create rules to scan the subject line for specific keywords and place them in a specific queue and assign them to specific users too. I tried under Admin -> Business process -> Workflow, but it didn't seem readily apparent exactly what I should be doing from there. Also, forgive me if this is a double post, I don't remember if I posted this question already, it's been a crazy couple of days. Thanks! Mario Roberti Myron L Company

Hello! We just got PSA installed and working, now we're wrestling with auto-assigning / auto-queue routing. Does anyone have some tips on how to get this working? I've been trolling through the manual, and checking the docs and forums, and I thought I had it narrowed down to Admin -> Business Processes -> Workflows, but that thing doesn't quite seem to have what we'd normally use (i.e. Enchant, SupportBee, Freshdesk all had a "If subject contains (your word here) then put in queue (your queue name)", where as I can't seem to find the analogous setting in PSA. Appreciate any help in advance! Mario

Thanks for this thread. It's been pretty insightful and we've been working hard to implement it in our enterprise. A couple questions to make sure we're taking the right approach for optimal execution. We're copying the dll and .exe file from our network repo to the local machines across the enterprise We're going to elevate the Powershell permissions under the Pulseway Manager running locally from under the Settings tab and then under runtime at the bottom, the part titled PowerShell User Agent and we're filling the necessary fields there (user, pass and domain) We're then executing a powershell script to push the registry entries and referencing where we copied the executable and dll, in this case, ""C:\scripts\Notification Bridge 1.2\Release\NotificationBridgePlugin.dll" Set-ItemProperty -Path "HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\Plugins" -Name Count -Value "1" New-Item -Path "HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\Plugins" -Name Plugin0 New-ItemProperty -Path "HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\Plugins\Plugin0" -Name ClassName -Value "NotificationBridgePlugin.NotificationBridgePlugin" New-ItemProperty -Path "HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\Plugins\Plugin0" -Name Description -Value "A bridge between Pulseway notification system and scripts." New-ItemProperty -Path "HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\Plugins\Plugin0" -Name FileName -Value "C:\scripts\Notification Bridge 1.2\Release\NotificationBridgePlugin.dll" New-ItemProperty -Path "HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\Plugins\Plugin0" -Name Name -Value "Notification Bridge" And then restarting all our machines for the registry addition to take effect. At that point, we think all the machines running Pulseway will then be able to fire off the NotificationBridge commands and have the mothership detect them and put them in the alerts area. Does that sound about right? I hope we're not over thinking this. Appreciate any input, and I included the above for posterity in the hopes it might help someone attempting to do the same thing. Thanks! Mario