This post is a third part of the series about Adaptive Cards technology. It is entirely dedicated to what the technology is about, how it works and how can be used in your solutions. If you are interested in the history of the concept, please open the first part from the series here.
It was fairly easy to say to SharePoint Workflow (both in 2010 and 2013 versions) that certain action or actions should be executed with the elevated permissions.
Sometimes when we are working with PowerApps, adding new connections like to Microsoft Flow or external services and then we decide we don’t need some of them anymore and therefore we are removing it, but forgetting to first delete it in PowerApps, we are finding ourselves in situation, where when trying to export the app as a package, we are facing a very hard to debug issue.
Post was inspired by a comment with a question posted some time ago under the post about hand written signatures. Kevan asked, if this is possible to take a photo, then sketch-note on it and finally save two images as a single one.
In the first part of the series I wrote a general overview of Message and Adaptive Cards, their brief history and purpose. This part is focused only on Message Cards – the technology from which it all begun and that is still available to use although recommendation is to move to Adaptive Cards.
Some time ago a customer asked me about a more effective user experience when approving tasks in workflows. The reason was that a manager, who was always involved at some time, was on the position, that if he is just sent an e-mail with approval request, this e-mail is going to simply get lost in his inbox and therefore he wouldn’t be able to respond. On the other hand he is using Microsoft Teams often, so asked if he can be notified about a task approval via that app.
In my previous post I have presented in details how the new Forms Pro differs from its older brother – Forms. Since then, having the possibility to play around with the new product, I would like now to describe you it’s outstanding feature – option for personalization.
When preparing for a new project, I started to check whether different customer expectations are feasible with PowerApps. The first of these is the ability to use an XML file as input, to build a table in the application and possibly to save them to SQL later.
Microsoft Forms application has been in Office 365 for quite a time. As soon as it was made available to commercial tenants, I made a post in which I reviewed the product and compared it to Google Forms. Almost two years have passed and we have a new product – Microsoft Forms in the Pro version. What is that? Read on!
In my daily work over business processes in Office 365, specifically in SharePoint Online, one thing annoys me the most – namely the lack of mechanisms to inform me that the workflow has hung up – that it is in a “Suspended” state.
The solution for that issue is not provided by Microsoft or Nintex – the company with which products I have been working for a quite long time. There are only workarounds, but they are inadequate, and I wanted to be able to react proactively and not reactively to any flow suspension event.