Best practices of Nintex Cloud

Hi @devendra14321, while there is not a 'Best Practices' document for NWC the same way there is for workflow for O365, I would recommend checking out the Product Documentation as it gives some guidelines around how to build workflows if you're just getting started. Also regarding your questions:

• Q: Is this applicable to Nintex cloud as well? 
  
  
  
  • A: No. The O365 Best Practices document does not apply to NWC workflows as they run on completely different workflow engines. Nintex for Office 365 leverages the workflow engine directly within SharePoint Online (the Workflow Manager engine), while NWC has its own new workflow engine that was built by Nintex.
  
  
  
  


• Q: Are there any other things we should consider before we use Nintex Cloud?
  
  
  
  • A: The biggest thing to remember before using NWC is that it is very API based. When we make connections to other SaaS systems we are doing so via their public APIs, and as such there are sometimes limits on what those APIs allow the workflow to do. 
  
  
  • When you build a Connection in NWC, any actions that use that Connection will execute using the credentials of the user that created the Connection, so it is recommended that when connecting to systems like Salesforce that you use a Service Account instead of just your own personal credentials.
  
  
  
  


• Q: How can we measure the size of the workflow in Nintex cloud? 
  
  
  
  • A: When you say size, do you mean the definition size (how big the workflow is in memory), or the action count size? 
    
    
    
    • With the new workflow engine in NWC, workflow size is not really a concern any longer, as we are not constrained by the publishing limitation within Office 365. While it is still recommended to keep your workflows below 200 actions, this is just from a manageability perspective. As someone that manages workflows frequently, I've found that anything over 200 actions gets difficult to keep track of without very strong workflow organization using Action Sets and good action naming.