Did you know you can show vacancies beautifully inside your organization chart in SharePoint? If it’s either SharePoint 2013, SharePoint 2016 or SharePoint Online in Office 365, you can do this easily with Plumsail Org Chart. In this article, I want to show you how to display vacancies in SharePoint Org Chart. It is very useful to organize vacancies inside of OrgChart and be able to visualize them within organization’s structure.
Vacancies are enabled inside of PlumsailOrgChart’s settings and use a data source different than the chart itself.Org Chart will use a different list to pull data from and show vacancies which needs to be filled with data regarding open positions through the company. Let’s see how to do it step by step, inside our SharePoint page, just like the image above.
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.
Don’t hesitate and check the new version of Plumsail HelpDesk.
Services like Slack and Microsoft Teams dramatically changed the way teams are communicating. To make your work even faster and efficient, you can configure notifications about new tickets from Plumsail HelpDesk for Microsoft Teams and Slack. So, every time a new ticket comes to your HelpDesk, you will get a nice reminder about it in your channel.
In the previous article, I compared Get Items by Query workflow action with OOB workflow. In this post, I would like to dive deeper and describe a few more actions and describe how they work.
We have the following actions that you can use to get items from a list:
- Get Items by Query
- Get Items from View
- Get Items by CAML Query
- Get Items by CAML Query (Many Lists)
They all starts from “Get Items” but they have some nuances of usage and actually could be useful for different situations.
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.
Let’s have a look at the following article: Call HTTP Web Service Using SharePoint Designer 2013 (SPD)
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.
Let’s imagine a situation where during a day people work with documents in SharePoint Document library. To work with some document user takes it to work and mark it as check out, but at the end of the day, every document should be checked-in back.
Below you can find an example of a small workflow which gets all documents in check-out status and does check-in for each one.
I used Get Item by Query workflow action with the following configuration:
Please pay attention that I used “client.svc” endpoint to get the data and expand File property to get File/ServerRelativeUrl
To check-in a document I used Check-in Document workflow action.
To run the workflow each day you can use Workflow Scheduler.