shruti.shukla

Top Features in Nintex Workflow for Office 365

Blog Post created by shruti.shukla on Apr 30, 2015
ActionDescriptionUse CaseBenefits
LoopThis workflow action runs a set of child actions while a condition evaluates to true. When the condition is true, the workflow will continue to the next action after the loop. For example, a request for manager approval will repeat five times before failing, if an approved or rejected response is not received, within the escalation limit.Workflow designs can now use complex logic that will progress a workflow based on looping conditions.
State Machine This workflow action provides a construct to define a number of states that the workflow can be in. Each state contains actions that will execute when the workflow is in that state. Users can model workflow processes to jump between different levels of business logic in a way that's easy to understand and maintain.  For example, managing a document approval workflow in an editorial process where an article goes back and forth between ‘states’ of completion.Allows for creation of non-linear workflows.
Run IfWorkflows execute action(s) only if a condition is met. For example, if the condition evaluates to true, the workflow executes actions within the Run If action. If the condition evaluates to false, the workflow bypasses the Run If action and continues with later actions.For example, in a lead nurture workflow, if a record is  updated to have a lead score over 50 then run a campaign to send follow up emails.Sets a condition to dictate the logic that is processed at runtime in a workflow.
Execute SQLConnect SharePoint Online platform to your organization’s internally hosted SQL servers. Using this action, users can execute SQL queries to create tables, retrieve/update data, and modify/delete data in a connected SQL database.For example, retail stores (that run as part of a franchise) maintain a local database for each store. Using Execute SQL action, information can be retrieved for use in a centralized workflow. Information stored in a local SQL database can be used throughout a workflow.
Conditional BranchThis action adds conditional branches to the workflow to define process logic, dependent on a condition. When the condition evaluates to true, the workflow follows the Right branch. When the condition evaluates to false, the workflow follows the Left branch.For example, if a purchase request is made that exceeds a certain dollar amount and requires additional approval, a Yes/No condition can be used to determine which branch the workflow should be routed to.Boolean logic allows workflows to use one of two branches (true/false) or in determining workflow state (when combined with state machines.)
Assign a TaskAssigns a Nintex Workflow task to a single user, for example routing leave requests to the manager of the person who submitted the request.Examples include routing approval requests for workflow scenarios such as: Leave Request/Human Resources OnBoarding/Purchase Requests.Outcome branches can be used to determine approval/reject path of workflow, including the ability to add additional outcome branches.
Call HTTP Web ServicesThe Call web service workflow action allows the workflow to make a call to a SOAP web service method. It is used to interact with custom created web services and to create/edit/delete list items across team sites. A common use for web services is performing simple create, read, update, delete, and query operations on customer data in a database. Workflow designers can call upon external applications that provide open Web API's to retrieve data.
Parallel BlockActions in the workflow will run in parallel. If the condition completes to true, the parallel block completes when an individual branch completes. If the condition evaluates to false, or is not set, the parallel block waits for all branches to complete before continuing to the next action.
For example, hiring of an employee must be approved by all 3 Vice Presidents at an organization. In this case, using parallel block, workflow designers can route an employee hire request to all three Vice Presidents at the same time.Multiple actions can occur at the same time allowing for certain actions to execute at the same time.
For EachA "For Each" action is used to step through each value in a collection variable and store it in a workflow variable. A simple scenario would be to run a workflow through several items in a list and to update each item in a given field from “No” to “Yes”.Enables simple iteration through each value in a dictionary of data while eliminating any possibility of infinite loops.
SwitchSwitch action directs the flow of actions based on the value of a single variable. A branch for each possible defined value is used to determine which branch of workflow actions will run.For example, setting a workflow variable called "varDepartment" where the outcomes can be IT, Finance, HR, Sales or PMO.Makes it easier to read, faster to design, looks more logical and instead of configuring several different Conditional Action branches, you only configure one Switch action.
LazyApprovalA key capability that allows users to respond to tasks assigned to them, using email, from a device of their choice. For example, by including relevant details in notification messages and enabling lazy approvals, managers only need to read the e-mail and respond with text as simple as “Yes” or “No” to approve.Saves time and effort.  Users can approve tasks from email enabled mobile devices, by entering a one-word response(for example, 'Approved').

Outcomes