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.
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.
A server which handles web page requests from users is called Web Front End (WFE). Thus, each time when user opens a SharePoint page in a browser, it is processed by WFE server. SharePoint farm may have multiple such servers. If there are multiple WFE servers, Network Load Balancer is distributing requests between them. It is the way to scale SharePoint.
Many Plumsail products are licensed per Web Front End server. You may need to calculate number of WFE servers in your SharePoint farm to purchase correct number of licenses.
SharePoint WFE server usually has “Microsoft SharePoint Foundation Web Application” service started. You can check it in SharePoint Central Administration: Central Administration > System Settings > Manage services on server. In the Services on server page, select server and check if the service is started. If it’s started, the selected server is acting as a web front-end server.
Thus, you can switch between your servers and find all Web Front End servers.
Probably, most companies need different e-mails for each department, that’s why in this tip I will show you how to create multiple help desks and configure them with different inboxes in Plumsail HelpDesk.
Let’s say that you have several departments — R&D, HR, and Support. Each of them has unique practices, different e-mail boxes and you want to separate them one from another. Configuring is effortless, first of all, we need to create a subsite for each department and then install help desk there.
Note that licensing of Plumsail HelpDesk allows you to install any amount of help desks within one web domain in Office 365 and one server on-premises. Due to it, we can create a separate mailbox for every department, give different permission levels to users and configure an e-mail notification according to needs of a department.
Today we’d like to talk about our new feature introduced as part of our recent release of SharePoint Dashboard Designer 2.6.0. It is the ability to display a practically unlimited number of series on one graph. Such series may be based on entirely different list columns or may have, say, a common category but separate value fields.