Badge – Chameleon

One platform that just doesn’t get enough love is the Model Driven Apps. You automatically know who is writing this because of this statement, but it is really the one true Low Code Platform.

Not only is it low code, but it is actually highly responsive as well.

Take this Contact as example

The view is showing everything on contact with a 3 column view. The columns are responsive, and the subgrids are responsive.

2 column. Using the length.

1 column using more of the length.

Even the BPF will automatically scale to the screen:

Even opening it on my Android in chrome

We personally feel that this app is rather quite amazing, and highly responsive. I could even open the app in Outlook and in native app, and it would function the same.

An app that truly deserves the Chameleon

Badge – Power User Love

Claiming the Power User Love for the app created for the technician to follow up on his tasks post disaster. A combination of PCF component in a Model Driven app to help the tech do his jobb faster, and while he is on the move!

This of course coupled together with a few Power Automates behind the scenes to move data through the DataVerse for better user flow.

Point Taken – Vipps technical approach

It was easy enough to connect to the Vipps API, but could we do it within technology that we use everyday in the Power Platform? We chose to have a look at Power Automate to see how this could be done.

When the Work Order reaches a certain stage we create a sales order. During this process we create a payment in Vipps. First thing we do is find the Contact from the Work Order.

After that we send an HTTP call to the Vipps service to receive an Access Token. This token is extracted via the Parse Json.

After parsing, we can now send the actual request to the Vipps API

We now have an active payment within Vipps that will send to a given user, and the user can continue to pay the sales order.

Point Taken – Vipps

A terrible disaster recently destroyed several houses in Lego City, leaving several citizens with destroyed houses 😥 The mountain of doom had a terrible outbreak and lava rocks flew many hundred meters onto the houses nearby.

Citizen self service

After the smoke has settled the citizens can return to the houses to see the damage. They take pictures and send these pictures to the portal provided from the City of Lego.

Repair

In Lego City they are lucky, because they have repairmen that have trained for this exact scenario

He will work on service cases from his mobile phone

Before fix

After fix

Payment

Once the Work Order is complete, we have to receive payment for the parts that have been mended. Luckily this system has an integration with Vipps, so the payment can be done over the phone instantly.

Simply open the work order and click on the button to invoice the customer

This generates a payment confirmation box

And then eventually a payment request for the end user.. It’s as simple as that!

Badge – Hipster

React app that runs on node.js server to serve conductors the possibility to drive trains from home office.

The app consumes 2 apps running on a raspberry PI, 1 app for live feed from train webcam and 1 app for controlling the trains through bluetooth.

The conductor portal in vs code to show that we are running it on node.

BTW we are also using react router for our menu handling.

The 2 apps that is serving the video feed and the remote control on the raspberry pi for the train is using sockets.io for communicating with frontend.

The resulting portal with live feed and further integration to PYTON controlled Rasberry PI

Badge – Plug n Play

It’s not going to win any beauty contest, but the button is critical for Lego City! Once the Mayor confirms the disaster is eminent, every citizen has to be notified about the problem.

This is a button written as a SPFx to trigger an azure function. The azure function will send notifications to citizens that it retrieves from Dynamics.

It has to be said that this button was created by a CRM dude with a lot of help from SP.. UX badge??!??!!;)

Badge – Go with the flow

To manage the important task of notifying the crisis team when disaster occurs we have created a logic app that runs through a process.

IF the IOT device goes offline (LAVA killed the device) a notification is received to logic app. This in turn triggers a message in Teams of the Mayor, and rends the mayor an approval request for “Create Task Force”.

The logic app awaits the confirmation from the Mayor.

Once the Mayor confirms, we have a Disaster Team ready to coordinate the help we need, and a task to be completed.