Having it as a static dropdown is annoying. It’s easy to forget to switch it back to “integrated windows authentication” when publishing, after testing with “interactive token.”
I considered putting two different versions of it inside a Switch, with the setting set in the config file, but even that is a poor solution because all the code inside the Office 365 Scope’s body must then be repeated.
It’s too bad there is no way to output the connection like we can with other activities like Use Appliction/Browser. If we could at least do that, then I could use O365 scope inside a Switch based on authentication type, output the connection to a variable, then have another O365 scope that has my process inside it and uses the previously generated connection.
Even making the body steps its own workflow and using Invoke Workflow won’t work, because the Get Mail and other activities will complain that they aren’t inside an O365 scope.
In my opinion, NOTHING should be a static dropdown in an activity’s properties. We should be able to set any property with a variable, expression, etc.
prashant1603765
ashokkarale
imad-pro
Matias_Clemente.Arg
Shah_Rukh