Have you logged a request with support to investigate your performance issues? Would be extremely helpful if you could provide specific scenarios to we can investigate on our end..
Hi, A component workflow should not allow you to select collections or dictionaries as initiation/output variables as they are both not supported. If this is happening please log a case with firstname.lastname@example.org so we can investigate further. Just confirm that you need to enable as component workflow first before configuring variables.. Thanks, Rick
42 votes5 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
With the work on a “Connection manager” MFA will be supported for those live actions that support OAuth authentication. Unfortunately not all actions do, and so there are exceptions. When connection manager is released the help will detail which will.
For the balance, the comment by Mike Oryszak below is an option for these actions.
If you create a connection that uses oAuth and the account you use has MFA then it will work, unfortunately at this stage the two actions you mention only support username/password (not oAuth) and hence won't work with MFA. We will be looking at updating these actions to support oAuth..
Hi, If we were able to store the name/email address of the user who responded via LazyApproval into a separate field on the task would that achieve your desired outcome? And if you could choose say between Display Name or Email address which would you choose? Cheers, Rick
4 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
If you are creating an oauth connection then it will validate the credentials when updating, this is not the case however when creating one with username/password as this happens at execution time.
I am pleased to announce this capability has rolled out this week as a Component Workflow. Learn more at https://www.nintex.com/blog/whats-new-component-workflows/
Hi KP, Can you explain what you are trying to do with content types specifically? Ta, Rick
You mention functionality limitations and wondering if can you share the types of limitations you are facing? Keen to understand what's stopping the move..
12 votesOpen for voting · 2 comments · 3 - Nintex Workflow for Office 365 · Flag idea as inappropriate… · Admin →
Thanks for the suggestion, as the product manager for DocGen I'll look into what we can do around template limits.