Since we didn’t show enoug last time when trying to clam the Retro badge, here we go again! Here we will show how we used paint to create the sause for the Pizza in the Head 2 Head challenge. But, paint wasn’t enoug, so we had to use Power Point as well. Had to make the transparent background in Power Point, as it’s not possible in Paint. We think that all graphic designers would either shoot themself or turn around in their grave if they knew we did this to make a red round object with a transparent background. So, if this is not a dirty hack, then how would you explain why not to the graphic designer that’s about to …… Yeah, you know…
Well, let’s all agree on something, this is a good old fasion LAN for us adolt nerds. And we love it! But, for us, it wouldn’t be a LAN without some good 90s music! That’s why we wanted to share this mood with you all Friday night! And yes, we saw both hands in the air, heads nodding a little bit more than normal to the beat, and legs mysteriously move to the music. Thank you all, we love being here and hope you enjoyed it (we know Ulrikke did)! <3 And, since we got several request fro the playlist link, here it is (yes, it’s called Øyvind 30 år, it was the playlist for that birthday): https://open.spotify.com/playlist/21bam2VESfvhlmNsZi0SDF?si=aa0660cc2e5d4d17
Let’s face it, we all love Microsft (and yes, sometime hates Microsoft, but any type of feeling is a lot better than no feelings!). We use Microsoft technology every day, and of course we use a lot of this in our solution. Let’s go for the one first. Using Power Automate to use data input in Dynamics 365 HR to create a user in Azure AD (I know, you’ve seen this before in a previous post, but it might be easier for you to see everything in one post than for us to reffer to other posts):
Then, why should you leave it up to every employee to create their email signature? Don’t worry, we’ll solve it for you. We’ve created a solution that attach a signature on all outgoing emails that have our company name in Azure AD, configured in the Exchange setup in office365 with data from Azure AD:
Create a disclaimer as a flow rule in ExchangeApplied to senders that are employed in our company, AxShredder IncThe signature itself is created with HTML-codeAnd this is how it will be, without data addedAnd with data added
And then, the night before a new employee starts at our company, have a Power Automate that imports the user in to Dynamics so that the user can log in to the system. Also, connect the user to the correct worker so that it can access the Employee Self-Service to see and edit data regarding himself:
Before we came to ACDC, who would have thought we ever would create a pizza creation app? But, here we go! Simplicity and speed was the important thing in order to be the first team to solve this task. The most timeconsuming task was to get hold of some images for the solution. And what better way of creating pizza sause than using the good and old bucket in MS Paint? Just close youre eyes, think about all the hours you spent playing around in Paint to create something beautiful you printed and gave to your sweetheart in the 5th grade! Oh, the memories!
We’ve now been sitting here for, well, let’s just say, for some time, and this is what we’ve done so far (and a little reminder of what we want to end up with) within the different categories (nice and orgenized for your pleasure):
Excelent user experience:
As our total solution is planned to make the Onboarding process a lot easier, streamlined and reduce the possibility of errors down to a minimum for companies, and at the same time make it a lot more exciting for new employees in the time between the signing of the agremment and the first day of work in the new job, this will not only be excelent user experience from the tech side but also from the personal side in the process!
So far in this hackaton, we have made it easier for both the HR department and the IT department to make everything ready for the new employee coming in. Now the two departments doesn’t even have to talk to each other to create a Azure AD user for the new employee, give the licences the employee needs and give the user acces to the systems it needs. Our Power Automate handles all of this! And, it even connects the AAD user to the correct worker in Dynamics and assigns it the Employee security role!
But, before the new employee even starts, why should it be difficult to send an Employemnt Agreement? Shouldn’t HR be able to do that from the same HR system they use evfery day? We say yes, and that’s why we’ve today integrated Dynamics 365 HR with OneFLow, so that you can send an Employement Argeement directly from D365 HR to the new employee, ready for signing, with information about the candidate entered into D365 HR! We are now creating the app for this, and the app will be embedded in the HR system. And, just to be very GDPR friendly, we do not ask the new employee for the National ID number in an email or something, the Employee writes this directly in the contract to sign, so that we can pick it up and automatically enter that information to D365 HR as well, without anyone needing to see it (work in progress, see also earlier post tagged with Right Now):
Most extreme business value
It almost sounds too cocky, but how is this solution not an extreme business value? It takes away a lot of manual work done today, and it is also a lot more GDPR friendly as sensitive information don’t need to be sent around by email. Tomorrow, we will also create a PowerApps Portal, where the new employee will get a lot of information about the company before it starts, and this is also the place where the new employee will fill out a lot of information about himself, and this information will automatically be imported to Datavers and to D365 HR, without anyone needing to see the information on the way! But, for now, we have the Power Automate that at least gives all current employees the notifications they shoukld recieve reguarding the tasks they need to perform in the process. This makes sure that nothing is forgotten, and the new employee will haver an amazing onboarding and start in the company:
Rock solid Geekness
With every technoligy and tools that we are using here, we use it to make the workday and the world a better place for botjh HR department, IT department and the new employee that is starting! If that’s not the best use of tools and technology, then what is??
Killer app
Our total solution consists of so many different parts, and they will all work together beautifully! It’s amazing to see how much functionality you can combine in a solution, and have it ready to import to many different customers. With a little personalizations here and there, this solution can be used by any company in the world that uses Dynamics FO or Dynamics HR.
We started this mornig with a call to a company called OneFlow. We have had some conversations with them before, and decided that we wanted to try to get something done together with them today. We wanted to bulid an API integration from Dynamics 365 HR to OneFlow, so that we can sen out Employment Agreements for digital signatures directly from Dynamics! If this is not a huge business value, then we don’t know what are! This is what this we did together with them right here and now, and how it works:
Contract is generated in oneflow, and is sent to the company representative as well as the employee.
When the contract is signed electronically by both parties, power automate get a callback with information on which employee that has signed and we can tick off “contract signed” in HR and add an url link to the contract in oneflow.
The solution is set up to support Swedish BankID,
Danish NemID, Finnish BankID,
Norwegian BankID and advanced e-signature for other countries with e-mail/phone verification
Why wouldn’t you want to save time on a process that can (and to be honest should) be automated in all companies that uses Dynamics? We have now created two different flow, where the first one creates a Azure AD user atomatically when you hire a new employee in Dynamics HR, and mark that the employee should have a user in AAD (Goes without saying, but for you that now wants to ask the question, yes, the flow assigns the created user to a group as well):
But why should we stop there? How many times haven’t new employees showed up at their first day of work, just to se that someone has forgotten to import you AAD user to the system, so you can’t log in? Don’t worry, this flow runs every night, finds the employees that have their first day of work the coming day, and gives the AAD user the right to log in to Dynamics 365 HR:
Since the tenant for our Demo environment is located in USA, we do get accsess to some functionality that is not yet available here at this side of the ocean. Therefore, for us how embrace the LowCode/NoCode functionality, we just love the way you can write what you want to do directly in the PowerApp with AI-powered assistance, and the suggestion for the code that should be used pops up right under it!
We have creagted a flow that once a day lists that tasks that are assigned to different employees in the company in the Task Management module in Dynamics 365 Human resources. We filter out the tasks that are completed and canceled, and we only look for tasks that are due in 10 or 3 days, or that is due today or is overdue. By using Vitual Tables in Dataverse to gather this data, we’ll have the flow looking up the data we need in other tables than the table for tasks, as we of course want the email to be sent to the assigned employee, with the information the employee needs to perform the task:
It finally works like a charm, as we now in Dynamics 365 Human Resources have 1 overdue task, and no tasks falling due in 10 or 3 days or today, and the flow sends 1 email with the correct information:
