Comments
-
Another thing which good old Web Help Desk does better!
-
Would be nice for this to be pushed into the non ESM enabled systems as well.
-
FYI - We have customers who have requested this feature before, see Support cases #00498866 & #00533206.
-
This came up today from a different angle, a Tech working in UAE office only works half day Thursday, WHD cannot accommodate this. :-(
-
I would agree. Customers who have migrated from WHD to SWSD will be used to such functionality where there maybe 5 Approvers but it only requires 2 to Approve to more the Approval Forwards.
-
Sean, Matt & Michael - some great content even if you are not coming from Cherwell.
-
I think the key here is in the Help Text Business Zone Specifies the business zone to use when formatting dates and times. A business zone consists of a time zone and a schedule of business hours (see Setup > General > Time & Place > Business Zones) This is Business Hours, not working hours
-
Hi @"amirb" Do you have more detail of "New version option for WMI Integration available for Windows" I can see the new option but it has no help and can find nothing new in the manual or release noes, how does this work? Thanks
-
Another thing which the SW WHD solution does better!
-
Sign up for the 12.3 Beta!
-
You wish! Not like-for-like functionality as well. WHD still does some things better. Do your homework to make sure SWSD is a good fit for you.
-
This is a must and surprised this is not available currently. We have many customers with the SW WHD solution and are trying to get them to move to SWSD, within WHD this has been standard forever! How do SW expect WHD customers to migrate to SWSD when this is "again" a loss of functionality?
-
No that is for Modern Auth Inbound only, currently MS are not doing anything Outbound on SMTP but have introduced the ability to do Modern Auth on SMTP as well if you so desire. Is it this which this Feature Request is about.
-
A default of USD is useless for any customer based outside US.
-
Needs this, for existing SW customers who come from their WHD solution this is a negative enhancement. WHD does this well, select Tickets A, B F & J and merge. Done!
-
OK, You have created this Feature Request within the SWSD application area, you should do similar within the WHD area so the correct people see it. The SWD team are likely to just pass this by.
-
Would you be prepared to pay for an Agent like SWSD?
-
Why do you not create an Action Rule with the Criteria of Level 3 Alert, Action send an Additional E-mail to whoever needs to know?
-
Now that 12.7.13 resolves the issues with the OoO module, the ability to do Option 2 would be nice in a future release.
-
I can see your pain but for most, a PO is an Accounting function rather than a Help Desk so the control would be on that side. You also have the fact that Assets is not a chargeable module in WHD so little incentive for Dev to invest much into this area.
-
A lot of the Hyperlinks in this update are giving 404 errors
-
The Logical place to put such a setting is within Setup > Techs > Tech Permissions > Other Permissions - like here
-
This is a very good idea to streamline productivity.
-
Hum, I always separate Incomg from Outgoing so I have separate App Registrations. I know it's more work after 90 days is up to reauthorise but never had an issue since. The SW documentation is not always truthful depending on which one you are reading. * I am OOO for the rest of the week so cannot check my settings for you…
-
The middle "mail send" looks incorrect to me. Are you using one Registered App to Send & Receive from same mailbox? I tend to have separate registrations even if using same Mailbox.
-
Hi @"navco_loop1" , This is more like a MS issue rather than WHD where the API Graph may not support the expunge like EWS did. What WHD version and can you share the permissions you have in Entra as the SW documentation is contradicting.
-
Trouble is bigger systems use Linux because it requires so much less resources. PostgreSQL support should not be stopped either - considering in the "real" world it is used much more than MS-SQL, alot of customer cannot use Cloud solutions.
-
Each Ticket should show the Tech Group derived from the Request Types associated with it.
-
Are all your Techs Type = Admin or Tech ? Are these HR Requests part of their own Tech Group where only HR Techs are members? Do your Techs you want to restrict, belong to a Tech Permission Group which has the option "Limit to Assigned Tech Groups" enabled?
-
Yes, use CABs instead