From our experience if your business case for purchase involves the cost of printed forms being replaced with this as a solution then understand your about to significantly “under promise” ……and “over deliver”…. Those who manage widely remote workforces need to look at this as a potential solution, the cost is reasonable when compared to what you get. We could live without it but it would be very painful. (update September 2018:- This solution has evolved from being peripheral to our business to being almost core to everything we measure and manage across 2 separate businesses. Just the cost of previous paper forms more than pays for the solution alone, let alone the efficiency gains it provides.
#APPENATE V2 GET FORMENTRY SEARCH FULL#
To get around this.Our business is mostly mobile, this solution enables those things traditionally only available in an office with full computing infrastructure to be made available to people who are remote and in poor mobile coverage areas. Next add a ‘ Search for users‘ action from office365 connector, and pass in the PVA dynamic value from the trigger Mine is:Īdd a Text Input to pass in the Display Name variable You will now be navigated to a new screen where you will build your Flow.įirst give the Flow a meaningful name. We will now build a new Flow to get the user details we want. Under the ‘Trigger Phrases’ and select ‘Call an action’. To get all the user details from Office365, scenario 2 will cover this Customize Greeting Scenario 2 (Office365) Which gives the Bot more of a human type feel.
Testing this, the Bot now knows my Display Name. Inside the message under the Trigger, you can customize the greeting message to include the variable bot.UserDisplayName Navigate to ‘Topics’ and select the ‘Greeting’ Topic, this is under ‘System Topics’. Select ‘Only for Teams’ Customize Greeting Scenario 1 (DisplayName)Īfter enabling the Authentication, you will now have access to Two variables,
#APPENATE V2 GET FORMENTRY SEARCH REGISTRATION#
This will work for ‘Manual’ as well, but will require additional steps to setup a App Registration in Azure. To check clickįor this example we will be using the ‘Only for Teams’ option. Once you have your Bot created, make sure the Authentication is set to ‘Only for teams’. (Keep in mind this might affect performance by a couple seconds) Contents We can also use this in the Greetings Topic to address the user by their first name, rather than their display name. This post will show both scenarios, on using the bot.UserDisplayName variable as well as getting all the user details that are stored in Office365 like: This is awesome, but what if we want more information about the logged in user? Summaryīy default PVA in Teams has some valuable variables handy, like ‘bot.UserDisplayName‘. We will be using the ‘Only for teams’ Authentication on the bot. This examples is based on building a Virtual Agent in Microsoft Teams.
0 kommentar(er)
