Merge branch 'master' of https://github.com/microsoft/powerapps-tools

Apps/CrisisCommunication/readme.md

@@ -17,12 +17,12 @@ In the walk through provided in the [documentation](https://aka.ms/crisis-commun
 Please read the full documentation for installation instructions and more details [https://aka.ms/crisis-communication-app-docs](https://aka.ms/crisis-communication-app-docs).
 
 ## Package contents
-|Component|	Filename |	Description
-|-|-|-|
-SharePoint list creation flow|	DeploySPLists.zip <br>GCC: DeploySPLists.zip|	Creates the lists necessary to hold the data in the app.
-End-user app and send a request flow|	CrisisCommunication.zip <br>GCC:	CrisisCommunicationGCC.zip|	Displays content to the end-user and submits requests to the central crisis management team.
-Admin application|	CrisisCommunicationAdmin.zip <br>GCC: CrisisCommunicationAdmin.zip|	Allows the crisis management team to update the content in the end-user app
-News push notification flow|	CrisisCommunicationNewsNotification.zip <br>GCC: CrisisCommunicationNewsNotificationGCC.zip|	Sends a push notification to end-users whenever there is a new internal company update
+| Component | Filename | Description |
+|--|--|--|
+| SharePoint list creation flow | DeploySPLists.zip <br>GCC: DeploySPLists.zip<br>No Outlook: DeploySPLists.NoOutlook.zip | Creates the lists necessary to hold the data in the app. |
+| End-user app and send a request flow | CrisisCommunication.zip <br>GCC:	CrisisCommunicationGCC.zip <br>No Outlook:	CrisisCommunicationNoOutlook.zip & CrisisCommunication.Request.NoOutlook | Displays content to the end-user and submits requests to the central crisis management team. |
+| Admin application | CrisisCommunicationAdmin.zip <br>GCC: CrisisCommunicationAdmin.zip <br>No Outlook: CrisisCommunicationAdmin.zip | Allows the crisis management team to update the content in the end-user app |
+| News push notification flow | CrisisCommunicationNewsNotification.zip <br>GCC: CrisisCommunicationNewsNotificationGCC.zip <br>No Outlook: CrisisCommunicationNewsNotification.NoOutlook.zip | Sends a push notification to end-users whenever there is a new internal company update |
 
 ## Download pack
 Directly [download all assets](https://github.com/microsoft/powerapps-tools/raw/master/Apps/CrisisCommunication/CrisisCommunicationPackage.zip).
@@ -71,6 +71,8 @@ To update a flow:
 ## Latest Update
 Date | Notes
 -|-
+2020.05.06 | Updated News Notification Flow to use the Office 365 Groups connector (instead of the Azure AD connector) to avoid admin consent requirement for developers to instantiate the connection.
+2020.05.05 | Uploaded No Outlook version, which removes the dependency from the Outlook connector in all apps and flows. Special setup instructions are available in the download package.
 2020.03.25 | [V2.20200325](https://github.com/microsoft/powerapps-tools/commit/fb7171ea2ba8bf0a0d029583942f6737b3e77039)<br>News Notification flows (regular & GCC)<br>- Updated default pagination limit of the Azure AD action to 5,000 to accomodate configurations for users with base licenses. This can be reconfigured to 100,000, see the documentation on how to update this.
 2020.03.23 | [V2.20200323](https://github.com/microsoft/powerapps-tools/commit/3b3cb2fdee7f8971dfa9d941f3b721d6e0baf4b5) <br>Crisis Communication App <br>- FAQ now sorts by Rank. <br>- Corrected text for Links. <br>- Fixed issue with navigating to the news screen when accessing the app by deep-linking. <br>- Implemented first round of easier styling. <br><br>Crisis Communication Admin App<br>- Fixed issue in which the selected item would not appear in some forms. <br>- Changed navigation behavior to occur OnSuccess of submitting a form. <br><br>Crisis Communication Request flow <br>- Fixed issue with quotation marks in adaptive cards. <br><br>News Notification flow <br>- Improved Azure AD connector to be able to page through members of a security group (up to Power Automate limit of 100,000) <br>- Filtered out non-users in security group. <br><br>DeploySPLists flow <br>- Columns are no longer hidden when flow is run. <br>- Fixed an issue affecting running the flow trigger.
 2020.03.16 | Updates: <br>- Bugfix: fixed a bug affecting setting up auto-replies. <br>- Implemented a way to configure more work status options more easily. <br>- Gallery navigation for Tips, News, and RSS have been changed to scroll bars due to a bug. 

Apps/RegionalEmergencyResponse/readme.md

@@ -12,10 +12,13 @@ Please do not open a support ticket if you encounter any bugs with the solution
 
 |Date   | Notes  |
 |---|--|
-|April 22, 2020|Initial release|
+|May 06, 2020|Ability for users to request access to the solution via the portal |
+|May 06, 2020|Admins can see all active users for their Parent Organization |
+|May 06, 2020|Addition of  Pediatric Beds To Bed Capacity Questionnaire |
+
 
 ### Disclaimer
 
 This app is a sample and may be used with Microsoft Power Platform for dissemination of reference information only. This app is not intended or made available for use as a medical device, clinical support, diagnostic tool, or other technology intended to be used in the diagnosis, cure, mitigation, treatment, or prevention of disease or other conditions, and no license or right is granted by Microsoft to use this app for such purposes. This app is not designed or intended to be a substitute for professional medical advice, diagnosis, treatment, or judgement and should not be used as such. Customer bears the sole risk and responsibility for any use of this app. Microsoft does not warrant that the app or any materials provided in connection therewith will be sufficient for any medical purposes or meet the health or medical requirements of any person.
 
-Sample data included in this app are for illustration only and are fictitious.  No real association is intended or inferred.
+Sample data included in this app are for illustration only and are fictitious.  No real association is intended or inferred.

Apps/ReleasePlanner/deployment.md

@@ -0,0 +1,187 @@
+# Deployment
+
+Follow the steps given in this document to install the Release Planner App in your environment.
+
+### Step by step instruction
+
+1.  On the environment where you intend to import the solution go to
+    “Solutions”.  
+    #### Classic UI
+
+
+    ![Classic UI - Advanced Settings](./media/classicui-advancedsetting.png)
+
+    ![Classic UI - Solutions](./media/classicui-solutions.png)
+
+    #### Modern UI
+
+
+    ![Modern UI - Solutions](./media/modernui-solutions.png)
+
+2.  Select “Import” on the toolbar.  
+    #### Classic UI
+
+
+    ![Classic UI - Import solution](./media/classicui-import.png)
+
+
+   #### Modern UI  
+
+   ![Modern UI](./media/import.png)
+
+
+
+3.  Select the solution package ZIP file you have downloaded on step 1 and click
+    “Next”:  
+
+
+    ![Import - Choose the solution file](./media/import-choosefile.png)
+
+4.  Click “Next”:  
+
+
+    ![Import solution - Click next button](./media/import-next.png)
+
+5.  After the import has completed, click “Publish All Customizations”:  
+
+
+    ![Import soltuion - Public all customization](./media/import-publishall.png)
+
+### Post-deployment steps
+
+#### Configure “Generate Release Plans Word Document” flow
+
+This flow should be configured if you are looking to generate the Word Document
+from the release planner app that contains all the features for a particular
+release wave and particular application.
+
+1.  On the environment where you have imported the solution go to “Solutions”
+    using the Modern UI:  
+
+
+    ![Modern UI - Solution](./media/modernui-solutions.png)
+
+2.  Select “Release Planner” solution:  
+
+
+    ![Release Planner Solution](./media/releaseplanner.png)
+
+3.  Select “Flow” filter on the upper right:  
+
+
+    ![Search Flow](./media/search-flow.png)
+
+4.  Select “Get Filter Criteria to fetch specific Release Plan records”:  
+
+
+    ![Flow - Get filter criteria to fetch specific release plan records](./media/getfiltercriteria.png)
+
+5.  Select “Edit”:  
+
+
+    ![Flow Edit](./media/flow-edit.png)
+
+6.  Expand “When an HTTP request is received” step and copy its URL to the
+    clipboard:  
+
+
+    ![Copy HTTP URL Request](./media/getflowhttp.png)
+
+7.  Go back to the list of flows and select “Generate Release Plans Word
+    document”:  
+
+
+    ![Search Generate Release Plans Word document flow](./media/searchgeneratereleaseplan.png)
+
+8.  Scroll down to “For each application” step:  
+
+
+    ![A screenshot of a cell phone Description automatically generated](./media/scroll-for-each-app.png)
+
+9.  Expand “For each application”, expand “Hierarchy Product value is not null”,
+    scroll down to “Get Filter Criteria” step and expand it:  
+
+
+    ![Expand HTTP Request step](./media/expand.jpg)
+
+10. Paste the URL copied on step 1.6 into “URI” field.
+
+11. Scroll up to “Init FilePath” step and expand it. In the “Value” field enter
+    the path to the SharePoint folder, where the resulting .doc files will be
+    saved:  
+
+
+    ![Update the File Path](./media/initfilepath.jpg)
+
+12. Copy “HTML.htm” template file (supplied with the Release Planner solution)
+    to the SharePoint folder you specified on step 1.11.
+
+13. Scroll down to “Initialize SharePoint SiteAddress” step and expand it. Enter
+    your SharePoint site address into “Value” field:  
+
+
+    ![Update SharePoint File Address](./media/initsharepointfileaddress.jpg)
+
+14. Scroll to the very beginning of the flow. Expand the first “When a HTTP
+    request is received” step and copy its URL to the clipboard:  
+
+
+    ![Copy HTTP Request](./media/copyhttprequest.png)
+
+15. Go back to “Solutions” list using Modern UI. Open “Release Planner”
+    solution. Select “Other” filter on the upper-right:  
+
+
+    ![Select Other](./media/select-other.png)
+
+16. Select “Generate Word Doc Ribbon script” web resource:  
+
+
+    ![Select Generate Word Doc Ribbon script](./media/select-generate-word-script.png)
+
+17. Select “Text Editor”:  
+
+
+    ![texteditor](./media/texteditor.png)
+
+18. Find “flowUrl” variable and replace its value with the URL copied on step
+    1.14:  Click OK.
+
+
+    ![Find Flow URL](./media/find-flow-url.jpg)
+
+#### Configure “Daily Email Alerts” flow
+
+1.  On the environment where you have imported the solution go to “Solutions”
+    using the Modern UI:  
+
+
+    ![Modern UI - Solution](./media/modernui-solutions.png)
+
+2.  Select “Release Planner” solution:  
+
+
+    ![Release Planner](./media/releaseplanner.png)
+
+3.  Select “Flow” filter on the upper right:  
+
+
+    ![Search Flow](./media/search-flow.png)
+
+4.  Select “Daily Email Alerts”  
+
+
+    ![Daily Email Alerts Flow](./media/dailyemailalert.png)
+
+5.  Select “Edit”:  
+
+
+    ![Edit Flow](./media/edit-flow.png)
+
+6.  Expand “Initialize Environment URL” step and enter your environment URL into
+    the “Value” field:  
+
+
+    ![A screenshot of a cell phone Description automatically generated](./media/environmenturl.jpg)
+
+    Click save and close the Flow.