In this example, I will create a process that needs two approvals.
With Microsoft Flow, you can easily send out Approvals with the Start an Approval action. After publishing, we can return to SharePoint and open the item again to view the result: Your email address will not be published. We obviously don’t want this text to be shown, so we need to change the HtmlText property of the text control to Parent.Default (which is the default value of this cards’ attribute, which is the approval history field).
Give my suggestions a try and let me know what happens. To store the outcome of each approval to the ‘ManagerApproval’ and ‘FinalApproval’ field we’ve just created, we need to compose the output after each approval so that we have the following information: The Response date is available in the Dynamic content from the Approval action, but this is not in a friendly format so we need to convert this to a friendly format by using the formatDateTime() expression: Where ‘dd-MM-yyyy’ will result into the following date format: 20-09-2018. When using PowerApps multi-line text inputs, behavior on line breaks is not always consistent. You may have also noticed that your Microsoft Flow approval comments will not (always) return line breaks.
Save my name, email, and website in this browser for the next time I comment. This can easily be done by adding the ‘ManagerApproval’ or ‘FinalApproval’ field from the Dynamic content to your Compose action.
After making some modifications on position, size and title (Approval history instead of ManagerApproval), we can publish the form by going to File and clicking on Save, followed by Publish.
I am trying to create an app where co-workers can submit supplies requests and have that request routed to their manager for approval.
If your Microsoft Outlook client doesn't support actionable messages, it displays approval requests in HTML format. We have also added a new list builder into flow that can be used for adding multiple attachments to an email, for example. Create a temporary label and place the arguments to Run in the code one-by-one.
Rik de Koning - October 10, 2018. ---Please click "Accept as Solution" if my post answered your question so that others may find it more quickly.
This identifier isn't recognized.
The default value for this text control is “Show your HTML text here.”.
I will not go into detail of the Approval part of the Flow, because that is pretty forward. to ‘Disabled’. Each disapproval will stop the process and inform the requester about to correct what’s wrong and restart the process after correcting it. Markdown is not currently supported for GCC and GCC High customers. Because we used the plain text option, all history is shown as HTML. You can use the Response option from the Dynamic content of the Approval action, which is ‘Approve’ or ‘Reject’, but this does not fit well into the context of my Approval history, so I just used plain text, which was ‘Approved’ or ‘Declined’. That is where Microsoft Flow and PowerApps kicks in. For this, I will create two new multiline (plain text) columns called ‘ManagerApproval’ and ‘FinalApproval’ where I will save the HTML based approval history from Microsoft Flow.
to the approval history that possibly might screw up the formatting. I am new to FLOW and POWERAPPS and having trouble.
Therefor, we need to check if comments have been entered.