Limited Action Workflows and Nintex Workflow Allowance Policy

eharris04
Workflow Hero
2 2 2,380

Many customers and organizations have workflows with a small number of actions to automate different business processes and help bring efficiency into the organization. Recognizing that this is a common scenario, Nintex has introduced a concept called Limited Action Workflows to help customers understand what will or will not be counted against the their workflow allowance.

 

What is a Limited Action Workflow?

Workflows that have less than or equal to five actions and don’t start another workflow will be considered as Limited Action Workflows. These workflows will not be counted towards the workflow allocation. This will allow customers to automate simple common business scenarios without adversely impacting a customer’s workflow allowance. For example, a simple approval workflow to route a document to my manager for approval which consists of three simple actions would be free.

 

Are there workflow actions that cannot be used in a Limited Action Workflow?

A Limited Action Workflow cannot use any Nintex Design Actions from the following list below:

  • NintexSign
  • Start Workflow
  • Start Nintex Workflow Cloud Workflow
  • Call HTTP Web Service
  • Web Request Action
  • Custom Xtensions for Nintex Workflow Cloud

 

Also note that if a User Defined Action (UDA) containing one or more of the above actions will also be considered a Limited Action Workflow and is subject to count against the workflow allowance.

 

Will a Limited Action Workflow be counted against the workflow allowance?

No. Any workflow that meets Nintex’s definition of Limited Action and does not include any actions included in the list above will not be counted against the workflow allowance.

 

What if a customer uses a User Defined Action (UDA) in the Limited Action Workflow?

Customers can leverage a UDA in a Limited Action Workflow. The actions within the UDA will be counted towards the 5-action count, so if the total Nintex Design Actions in the Limited Action Workflow and actions within the UDA being called are greater than five, the Limited Action Workflow will be considered a Nintex workflow.

 

Are all Nintex design actions counted towards the five-action count in a limited action workflow?

The following actions are NOT counted against the five-action count for limited action workflows:

O365:

  • Log to History
  • Set Workflow Status
  • Pause for Duration
  • Hawkeye Beacon
  • Hawkeye Beginning Beacon
  • Hawkeye Ending Beacon

 

NWC:

  • Log to Instance
  • Set Instance Name
  • Pause for Duration
  • Hawkeye Beacon
  • Hawkeye Beginning Beacon
  • Hawkeye Ending Beacon

 

SharePoint On-Premises:

  • Log to History
  • Commit Pending Changes
  • Hawkeye Beacon
  • Hawkeye Beginning Beacon
  • Hawkeye Ending Beacon
  • Set Workflow Status
  • Pause for Duration

 

All other actions count towards the 5-action count for limited action workflows. For more information about the use policy, subscription policy or End User agreements - visit https://www.nintex.com/legal/.

2 Comments
cju
Automation Master
Automation Master

Thanks for this post! Very useful!

Can you add rules regarding component workflows? Is it the same as UDA?

rossk
Design Dabbler

@eharris04 

Should "Run Component workflow" be added to the list of actions that cannot be used in a Limited Action Workflow?

Thanks!