Final Day Judging and Demos

We’ve had a few questions about the sequence of things today, especially since the agenda has shifted a bit from what’s on the back of the name tags.

1600 – Judging

We will be doing a round of judging at 16:00 again. Be prepared to update the judges on your progress against the categories as before. At that point, we’ll be looking to understand what you’ve accomplished since the last round of judging on Friday at 1600.

Then we all break, clean up the room, etc.

1700 – “Free time”

1900 – Meetup @ bar

1930 – Challenge fine dinner

2100 – Demos and awards

After dinner, each team will have 7 minutes to present their solution. It should be a “pitch”, with a demo of what you have, remembering that you are mainly pitching to the other teams and esteemed guests. (We judges will have seen most of what you are doing, right?) The categories don’t matter at this point; you should talk about the solution and your results.

Think of it as the first time everyone will be seeing your solution (in many cases this will be true!). Your mission is to convince everyone that your solution is the best. It’s up to you what you emphasize, but here are some angles you could take:

  • We built the coolest thing that reflects the theme
  • We took on the hardest technical challenges
  • We used the highest number of cloud services – the best “mash up”
  • We’re the team with the best jokes
  • We can do the best multi-media presentation

You won’t know which approach the other teams will take, so plan wisely, especially since we will stop you at 7 minutes. Period.

After the demos, we’ll have a popular vote. Scott has built a cool voting solution on Dynamics we’ll use for this.

Then we judges will deliberate and come back with the awards and WINNER(s)!!!!

2200+ ASPC Party

Power user functionality AKA User power LOVE

In Zion security is King!
Users of the Command Center change departments and floors all the time. As an effect, the elevators are in constant need of repairs. More importantly users should be able to retain their security groups and the security roles if they, by any chance, change departments. Straight outta the cocoon (meaning: out of the box), this requires system admins to re-assign security roles. This is a major hassle and a complete waste of time, especially in the face of the always imminent Agent threat!
In order to cope with this we have implemented a data model and business logic to handle these challenges. We have implemented a new entity called Security Group consisting of a set of default roles. Whenever a user changes its security group or it business unit, a plugin figures out which security group you belong to and also which business unit you belong to, and it figures out which security roles you are supposed to have, and assigns them to you.
This is a solution created during Artic SharePoint Challange.. Hope you like it! We know how confusing the security roles in Dynamics CRM can be! Why do we have to assign security roles after we move a user who have the same role in a different department?
So we created this to earn some POWER USER LOVE archivement points šŸ™‚
Eat that, Mr Smith!




Using Office 365 Public CDN in SharePoint Online

In the void – bytes counts. You think that’s air you’re breathing? The Appsters wanted to improve their solution by using the public CDN functionality in SharePoint Online. It’s pretty easy to enable in a tenant. I recommend this Ā Office Dev Center guide for how to do it, and I’m not going into details of exactly that here.

What it does is that enables a library/folder of your choice to be reached from Office 365 using a specific path on the format<tenant host name>/<ID of the public CDN origin>/<sub-path under the origin>

The Appsters’ public CDN URL is

We wanted to share how we work with the Public CDN and Office PnP templates. We are incorporating this into our solution using the CDN URL as a parameter into our pnp-templates.

We are then able to use the parameter when specifying the URL to our JavaScript and CSS files (Of course we’re not referencing every single file – we use a JavaScript script-loader that uses the Sod-functionality to load dependencies (but that’s for another blog post :)). As an example, take a look at how we reference the script-loader from a custom action:

And for the site logo:

And with Chrome Source explorer you can see that our files are loaded from the CDN.

We’re using the public CDN for all of our JavaScript-files, CSS-files, images and logos etc. The only limitation we’ve hit so far is that Office PnP parameters doesn’t work in .spfont files, unfortunately needing us to have the CDN-URL multiple places.

That’s it – happy coding!

Project automation in CRM

We are working on project automation in Dynamics 365. This in order to plan what agents with certain skill sets will be most fitted for the mission. We’re radomizing skill setsĀ in order to use scheduleboardsĀ inĀ locatingĀ required skill sets.

Randomizing skill sets when automatically creating bookable agents:
LeadingĀ us to Ā being ableĀ to filter agents by their skill sets and their abilities: