Nintex

June 15, 2021

The article below concerns Nintex Workflow Cloud. Nintex Workflow Cloud is a cloud-based platform where you can design workflows to automate simple to complex processes using drag-and-drop interactions without writing any code. You can build digital forms, integrate web services, and connect to third-party applications to create a seamless experience for your end users throughout the workflow.


Topic




Why Nintex is requesting to have Read and Write permission to Azure Active Directory for the User Directory Lookup below:


 


https://help.nintex.com/en-US/nwc/Content/Settings/UserDirectoryLookup.htm


 




Additional Information




User Directory Lookup leveraging on our Xtensions functionality for Azure Active Directory and Azure Active Directory Administration connector which requires Write permission.


For this functionality to work, we needed to use Azure Active Directory Administration connections because it provided access to Read the directory permissions.


 


The permissions were inherited because we are using this:



https://help.nintex.com/en-US/nwc/Content/Designer/Connectors/AzureADAdminConnector.htm


 


Connections created in the User Directory Lookup settings page will not be accessible to workflow designers, and thus any write operations using that connection will not be accessible to workflow designs.


 




Related Links



Related Posts

You May Also Like…

Workflow Start Threshold and Throttling

Jun 28, 2022

Topic

 
Nintex Workflow Cloud (NWC) tenants have Workflow Start threshold of 10,000/hour per tenant.
 

Additional Information

 
Why does this threshold exist?

To provide a high-performance environment for all customers, in a fair usage environment. 
Ensure our service operates reliably and predictably for all customers.
Avoid performance degradation incidents.
The threshold level is well above the typical usage for most customers.  97% of our O365 & NWC customers have workflow starts below 5,000/hour.

 
What is considered a ‘Workflow Start’?
Any request to start a workflow through any of the following channels: Manual start, Form Submission, Start Event (i.e. item added to SharePoint list), Component workflows (i.e. started from NWC API, Start Workflow action, etc.), or a Scheduled start.
 

How can the threshold be avoided?

Optimize request operations:

Add more granular conditions for a request to start workflows
Fewer requests per hour
Stagger requests throughout the day
Reduce the frequency of requests

 
What happens when the threshold is reached?

External starts (API calls, component workflows, etc.) – No new workflows start;  Returns a 429.
Start Events – Workflow start is queued and retried in next hour.
Form submissions – Workflow start is queued and retried in next hour.
Scheduled workflows – Postponed until the next hour.

 
Additionally, an in-app banner message in Automate page will be displayed stating the following:
 
Due to higher volumes within the past hour some workflows have not yet started and are queued to commence shortly.  For more information, please visit the manage workflow starts help document.
 

Remove The Account To Configure Azure Active Directory Identity Federation After Completed The Setup

Mar 10, 2022

Topic

Can we remove the Admin account that is used to configure the Azure Active Directory identity federation after the setup has been completed? 
 

Additional Information

Yes, you can remove this Admin account after successfully finishing the setup and it will still work even after the account has been removed. 
 

Related Links

https://help.nintex.com/en-US/nwc/Content/Settings/ConfigureAzureAD.htm