<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>M365 on When Pigs Fly</title><link>http://derekcp.com/tags/m365/</link><description>Recent content in M365 on When Pigs Fly</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 16 Aug 2023 00:00:00 +0000</lastBuildDate><atom:link href="http://derekcp.com/tags/m365/index.xml" rel="self" type="application/rss+xml"/><item><title>Redirecting List Forms</title><link>http://derekcp.com/posts/redirecting-list-forms/</link><pubDate>Wed, 16 Aug 2023 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/redirecting-list-forms/</guid><description>&lt;p&gt;I recently encountered a situation with a client where I was working on setting up a list for a business process. The process required users to access a dedicated site to fill out a form, and we decided to embed the new form directly onto the site&amp;rsquo;s homepage. Additionally, we wanted to display a list of all the submitted items by users.&lt;/p&gt;
&lt;p&gt;&lt;a href="images/formembeded.png"&gt;








&lt;figure class="image component image-fullbleed body-copy-wide nr-scroll-animation nr-scroll-animation--on image-big"&gt; &lt;div class="component-content"&gt;
 &lt;div class="image-sharesheet"&gt;
 &lt;div class="image image-load image-asset image-f690380b380130644851a9c89c1ab97e" id="lhtf690380b380130644851a9c89c1ab97e"&gt;
 &lt;picture class="picture"&gt;
 &lt;img class="picture-image" data-src="http://derekcp.com/posts/redirecting-list-forms/images/formembeded.png" alt="" /&gt;
 &lt;/picture&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="image-description"&gt;
 &lt;div class="image-caption"&gt;
 
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Automated Provisioning of Flows</title><link>http://derekcp.com/posts/automated-provisioning-of-flows/</link><pubDate>Wed, 09 Jun 2021 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/automated-provisioning-of-flows/</guid><description>&lt;p&gt;I have a client that needed to automate their site provisioning. We are using &lt;a href="https://www.orchestry.com/"&gt;Orchestry&lt;/a&gt; to handle the site setup but there are some gaps in that provisioning. The biggest gap is that they need to attach workflows in PowerAutomate to do things like approvals and notifications. Out of the box when you create a new Flow in Power Automate and you can create a trigger on a specific list or library on a specific site. These connections and urls get stored in the manifest for the Flow. In this instance, once the site is created I need to add tasks with dates to a task list and then add an approval workflow to those tasks when they are marked for completion.&lt;/p&gt;</description></item><item><title>Creating Status Indicator using PowerApps</title><link>http://derekcp.com/posts/creating-status-indicator-using-powerapps/</link><pubDate>Mon, 01 Mar 2021 00:00:00 +0000</pubDate><guid>http://derekcp.com/posts/creating-status-indicator-using-powerapps/</guid><description>&lt;p&gt;I was working on creating a demo for a conference session on user experience and design for Power Apps and part of that included creating a PowerApp to illustrate the point. In the session we talk about the &lt;a href="https://www.nngroup.com/articles/ten-usability-heuristics/"&gt;10 Usability Heuristics for User Interface Design&lt;/a&gt; and how to map them to the work we do with the Power Platform. One of those heuristics is &lt;strong&gt;Visibility of system status&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;What this means is:&lt;br&gt;
&lt;strong&gt;The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.&lt;/strong&gt; When users know the current system status, they learn the outcome of their prior interactions and determine next steps. Predictable interactions create trust in the product as well as the brand.&lt;/p&gt;</description></item></channel></rss>