cancel
Showing results for 
Search instead for 
Did you mean: 

What is a Subscription WF On Premises or in the Cloud?

Workflow Hero
11 3 1,895

What is a Subscription Workflow?

  • Subscription provides our entire suite of software, and is only limited by the number of Workflows you create, not the SharePoint version you are running, or the number of WFE's you have. The Workflows you purchase can be used wherever you need them, on premises (2007, 2010, 2013, or 2016), in SP Online, or Nintex Workflow Cloud. The idea behind our subscription model, is to provide our customers with flexibility, and use Workflows only where you need them.

Types of Workflow's

  • Simple Workflow = 5 actions or less
  • Standard Workflow = 6 +
    • 75 actions = 1 Workflow
    • 120 actions = 1 Workflow

How are Workflows under 5 actions counted?

  • Simple Workflows are not counted as a workflow.

What constitutes as a development workflow?

  • When you begin to build your Workflow, you designate whether or not the workflow is a production or development workflow.
  • Standard Development Workflows = 2 x purchased number of Workflows
    • 5 Workflows = 10 Development Workflows
  • Enterprise Development Workflows = 4 x purchased number of Workflows
    • 5 Workflows = 20 Development Workflows   

How/when does the "true up" process happen if you are over your limit?

  • The end of your contract during your renewal process.

LET'S GET TECHNICAL!

What is a Production Workflow?

  • A Nintex Workflow that is designed and published into a production environment.

Simple Workflow or Limited Action Workflow

  • A Production Workflow which is comprised of not more than five (5) Nintex Design Actions and does not initiate a separate Nintex Workflow.
  • A Limited Action Workflow will not count towards the applicable Subscription Workflow Limit. 

A Nintex Form

  • A form designed and published by use of the Nintex Form designer.


A Production Form

  • A Nintex Form designed and published into a production environment.


Nintex Design Action

  • A workflow action used by a workflow designer to construct a Nintex Workflow.
    • The following Nintex Design Actions will not count as an action during the contruct of your workflow:
      • Log to history, Beacon(Hawkeye), Beginning Beacon (Hawkeye), Ending Beacon(Hawkeye), Set Workflow Status, Commit Pending Changes

User Defined Action

  • A set of Nintex Design Actions configured to perform a function and incorporated in a Nintex Workflow as a single Nintex Design Action.
  • A User Defined Action will not be included in the applicable Subscription Action Limit. Nor will, the number of Nintex Actions within the User Defined Action count towards the applicable Subscription Action Limit. 

Test Data

  • Production data or other data utilized for the sole purpose of testing and evaluating workflow and/or forms designs.


Nintex Enterprise Edition Subscription Support includes:

  • Software Upgrade & Maintenance, Self Help Access, Customer Support Portal Access, Sandbox Availability and Inbound Phone Support (24x5)


Nintex Workflow is defined as:

  • A set of Nintex Design Actions which include a manual or automated start and a termination or end.

Development Workflow:

  • A Nintex Workflow which runs on Test Data solely for the purpose of developing and testing a Nintex
    Workflow design.

Subscription Workflow Limit

  • The maximum number of Nintex Workflows available to be published during the subscription term based on the End User’s Workflow Plan.

Stand-Alone Form

  • A Nintex Form that is not included within a Nintex Workflow or Limited Action Workflow.

Start/Task Forms

  •   A Start/Task form will not count towards the total allotted number of Forms. 

Development Form

  • A Nintex Form designed to run on Test Data solely for the purpose of developing and testing the Nintex Form design.

Subscription Forms Limit

  • The maximum number of Stand-Alone Forms available to be published during the subscription term based on the End User’s Workflow Plan. The number of available Stand-Alone Forms shall be equal to the applicable Subscription Workflow Limit multiplied by five (5).
3 Comments
Workflow Hero

That's a nice overview. Thanks.

As far as I know there are two additions. If I'm wrong it would be nice to correct them:

  • Workflow actions like "start workflow" or call web service always make a workflow count as complex workflow even if it doesn't contain 6+ actions
  • Actions inside a User Defined Action are counted normally in a workflow.
    • e.g Workflow has 5 actions, one of it is a UDA with 10 actions is
      • 5 (actions) - 1 (UDA itself) + 10 (actions inside UDA)

Best regards

Enrico

Workflow Hero

Nintex Design Action

  • A workflow action used by a workflow designer to construct a Nintex Workflow.
    • The following Nintex Design Actions will not count as an action during the contruct of your workflow:
      • Log to history, Beacon(Hawkeye), Beginning Beacon (Hawkeye), Ending Beacon(Hawkeye), Set Workflow Status, Commit Pending Changes

Do Action Set actions count against the limit of 5? Are these the actions listed below the only actions that do not count?

Workflow Hero

Hi Enrico, that´s not entirely correct. The actions that cannot be used in a Limited Action Workflow are those that can initiate a separate Nintex Workflow. Those include, obviously the Start Workflow action, but in regards to a Call Web Service action only if that action is used for calling another WF. Any other Call Web service action can be used as part of your Limited Action Workflow.

Hope it clarifies it a little bit more