New Microsoft products made a lot of clutter — what is Office 365 Groups and what is Microsoft Teams? What’s the difference between them, is it have something in common with SharePoint Team sites? In this short article, we will make it loud and simple.
We have been working untiringly on some major updates in Plumsail HelpDesk and we think that you will love it! So, what’s new?
New triggers and scheduler We pretty much rebuilt our triggers from scratch and now they are even faster and user-friendly. It applies to the scheduler as well. Now you can send emails, start workflows and set ticket fields there.
Widget for internal users Let’s say that you want to have internal communication channel for users in your service desk but you don’t want them to see all tickets that you are operating. How can they easily manage, track and resolve issues? The solution is quite simple — Plumsail HelpDesk widget. With the widget, you can provide a UI for internal users without giving them access to all tickets. Providing an intuitive user experience that empowers your users by making it easy for them to get service, support, and information no matter where they are. The widget can become your service desk with remote control capabilities to help you resolve issues without initiating a desk-side visit.
And other minor bug fixes and performance optimizations.
Probably you are familiar that using SharePoint Designer you can consume SharePoint REST API.
The API is very flexible and allows you to manipulate items, lists and almost every aspect of SharePoint. On the Internet, you can find many articles describing how to use it and how to correctly configure the workflow.
In most cases this will be very simple use cases, I suppose this is because the complexity of the workflow increasing dramatically with number or required requests and processing data.
We are in Plumsail try to simplify things, that is why we added “Get Items by Query” workflow action.
A guy describes how to create a simple workflow which gets items from a list and log a Title of each item to the history list.
I reproduced the case and it takes almost half of an hour to create it.
After that, I installed Workflow Actions Pack and I created the same use case but using actions from Workflow Actions Pack. Of course, it took just 5 mins and the final workflow looks more clear for anyone who has to maintain it in the future.
Now let’s imagine that you need to implement more complex workflow, indeed in a production environment, I saw workflows which take 3-5 pages and it’s hard to understand their logic and I do not mention that consultant that creates it costs a lot of money. Using Actions Pack you can save your time and your money. Moreover, Workflow Actions Pack allows you to get data from another site or even tenant, it opens new possibilities comparing with OOB workflows.
As a conclusion, I would like to say: – “Do a smart investment!”. The product has a really good ROI.