Skip navigation
All Places > Getting Started > Blog > 2015 > December
2015

Products: Nintex Workflow 2013, Nintex Workflow 2010

 

This article provides instructions on how to locate all lists and sites in a farm that are utilizing Nintex Workflow Content Types.

 

WARNING: This script is fairly resource intensive. It is recommended to run this script in a non-production environment to gauge its impact.

 

Run the below (attached as well as a *.txt file for your convenience) PowerShell script (PowerShell ISE works well) from a SharePoint Server:

 

PowerShell Script

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
[void][System.Reflection.Assembly]::LoadWithPartialName("Nintex.Workflow")
[void][System.Reflection.Assembly]::LoadWithPartialName("Nintex.Workflow.Administration")

function Get-NintexContentTypeIDQuery{
"0x0108010064E42B14ADA442C78E98D686760A8493|0x010801005CC0A86910A24687A76ECAC954D3E3F3|006EBD0FA4731041D9804386A7FEA568DC|000568DBB766D0491684897A230753AAF9|0x0108010079DBDE612F7B46928C6A2516BA2CAE37|0x0108010079DBDE612F7B46928C6A2516BA2CAE3700E0B65C5281234030AA8CA4D8F8910E72|0x0108010079DBDE612F7B46928C6A2516BA2CAE3700D4A837248A47E040ABD1A569613E898B|0x01010024055591300C45C3B4C2854A24EF05CE|0x010100F815D979DC2B4F48A9DBCA64AED3C636|0x010100F8376F5313D041EF85718B229F4FBFA8"
}

function Get-SharePointWebsContainingNintex {
PARAM
(
[Parameter(ValueFromPipeline=$true)] [Microsoft.SharePoint.SPSite] $SPSite
)

BEGIN {
  }

END {
}

PROCESS {
  if ($($SPSite.OpenWeb().ContentTypes | Where {$_.Id -match $(Get-NintexContentTypeIDQuery)}).Count -gt 0){
  $SPSite.OpenWeb()
  }
 
  $SPWeb = $null
  $SPSite = $null
  [GC]::Collect()
}
}

function Get-SharePointListCollection {
PARAM
(
[Parameter(ValueFromPipeline=$true)] [Microsoft.SharePoint.SPWeb] $SPWeb
)

BEGIN {
  }

END {
}

PROCESS {
  $SPWeb.Lists
  $SPWeb = $null
  [GC]::Collect()
}
}

function Get-SharePointListContainingNintex {
    [CmdletBinding(DefaultParameterSetName = "frompipe")]
PARAM
(
    [Parameter(
        Mandatory=$true,
        ValueFromPipeline=$true,
        ParameterSetName="frompipe"
        )]
        [Microsoft.SharePoint.SPList]$SPList
)

BEGIN {
  }

END {
}

PROCESS {
   
  [bool]$HasContentType = $false

  foreach ($SPContentType in $SPList.ContentTypes){
 
   if ($SPContentType.Id -match $(Get-NintexContentTypeIDQuery)){
    $HasContentType = $true
   }
 
  }
 
  if($HasContentType){
   $SPList
  }

  $SPList = $null
  [GC]::Collect()
}

}

Get-SPSite | Get-SharePointWebsContainingNintex | Get-SharePointListCollection | Get-SharePointListContainingNintex | FT Title, ParentWeb

 

Additionally, the properties returned can be changed by appending properties to the end of the script (default is ParentWeb, Title).

 

Nintex User Voice - Current Status

 

User Voice is a great tool used by Nintex to collect customer feeback, where you can post your desired feature and other users can vote for your posted feature, then Nintex people collect that information to enhance their products.

 

Currently there are 15 planned features for Nintex Workflow for Office 365.

 

Here is a list of title of those features.

 

  • Schedule Site Workflow
  • Conditional Start
  • Prevent other users from approve/reject task not assigned to them
  • Workflow Column Status
  • Add Action Sets
  • Update document and convert document controls for Office 365 version
  • Keep tasks for more than 60 days
  • Provide visualisation mechanism
  • Where are some templates that I can get started quickly.
  • Allow Carriage Returns/New Lines in Yammer Messages
  • Add BCS Query support
  • List Lookup Detail in O365 Set Variable Action
  • Manage your Workflows tasks from a mobile device using the Nintex Mobile App.
  • Ability to Group activities and collapse and expand
  • Dutch translation

 

All those features came from users and were considered by Nintex.

Visit https://nintex.uservoice.com/ and add your wishlist and votes to further improve the products.

Hi all,

 

I am working with nintex workflow 2010. I have create workflow to delete the sharepoint list item once the list item column 'task Finished' set to Yes.I have added condition in workflow setting to trigger only when the sharepoint column 'task Finished' set to Yes.

 

I am not sure why this is unable to proceed further even the workflow status column showing starting and workflow is running on it but nothing happening further. When i try to run same workflow manually on same item it deleting item with in fraction of seconds. and i tried all the possible ways purging workflow history and current running workflows on sharpeoint list everything but nothing seems to work with it.

 

Can someone please advise how can make my workflow to trigger conditional basis instead of manually triggering it ?

We've made a few changes on the community, and I thought it was a good time to provide an update on how to find some new features and get more out of your time here. I'll outline the changes and then dive into some of the best ways to use Nintex Connect.

 

First, you've probably noticed we removed the icons on the landing page.  That's because we have so many spaces, we wanted to surface quick access to them all. You can click them directly below our banner or find even more by clicking the menu items in the black bar across the top of the page and seeing what's in the dropdown menus.

 

landingpage

 

 

 

We've also added a new widget to the upper-right corner, which will take you to Nintex websites for corporate and product information and the Nintex Learning Center.

 

 

 

 

 

 

 

 

 

Let's dive briefly into the "forums," which we also refer to as "spaces."

Getting Started

This is where you literally get started with help with Nintex for SharePoint, Nintex Forms and mobile forms. If you're new to Nintex products, this is a good place to search for answers to your questions and to post new questions.  If you think you'll post a question starting with, "I'm new to NIntex, and..." then this is where your question belongs.

gettingstarted.PNG

 

 

 

 

 

 

 

 

 

 

 

You'll notice on the left side of the page that we've provided links to information on our products. Below that is recent content.  On the right are quick links to "ask a question" and product help links.

 

 

 

 

Read more on asking questions in this blog post Where can I find the forums and ask questions?

 

Where's the Content?

 

Each space has a Recent Content area on the main page, this is where you'll see the most recent discussions on that space. Look out for it to see new, and newly responded to posts.

 

If you want to browse through all the discussions, and questions on a space you'll need to go to the Content tab of the area of interest. Here you'll be able to browse through any discussions, documents or blog posts.

content

 

You can also filter by latest activity, or by a specific tag, even use the Categories on the left-hand side to find information in that category. Break it down further by selecting either blog posts, documents or discussions!

 

content2

 

 

How to "follow" Content or a Person

Did you find a document you want to return to? Or maybe you want to know if it ever gets updated. Or maybe you want to know when a community member posts new content.  Just "follow" that person.  Simply look for the "actions" link in the upper-right corner of a page. Click it for the "follow" option.  Now make sure your profile is set so you receive notifications (click your avatar in the upper-right and select "preferences"). If you do that, you'll get notifications on updates!

avatarprefs

Today I wanted to edit a Nintex form and received this message

 

"Your subscription has expired. You will be unable to save or publish the form. Contact Nintex to renew your subscription"

 

I found out that you need to write to support@nintex.com to solve this situation.

 

Here below there is more help about this situation that it 's good to know.

 

What happens at the end of my subscription?

Nintex Workflow for Office 365 and Nintex Forms for Office 365 are each provided under a subscription license. Whilst an organization has an active subscription, users will be able to build and run workflows built with Nintex Workflow for Office 365 and build and run forms build with Nintex Forms for Office 365.

As a subscription expiry approaches, a number of communications, prompts, and warnings are displayed as outlined below.

60 days prior to your subscription expiry

The primary contact is notified that the subscription is due to expire in 60 days.

30 days to your subscription expiry

All registered contacts are notified that the subscription is due to expire in 30 days.

Nintex Workflow for Office 365: Visual prompts are added to the Nintex Workflow designer. Workflow history records are added stating that the subscription is due to expire. Nintex continues to notify all registered contacts of the upcoming expiry at regular intervals over the 30 day period.

At subscription expiry

Once a subscription has expired, you will no longer be able to save or publish workflows through the Nintex Workflow designer or forms through the Nintex Forms designer. Any existing workflows that are published will enter a suspended state.

Account details will be kept on record for 30 days following a subscription expiry, after which they will be deleted.

You can choose to renew your subscription period at any time in the last 3 months of the contract. Once a subscription is renewed, you will receive a notification acknowledging the subscription renewal and the new expiry date.

Note: You can request a temporary extension of the subscription for a period of 30 days to provide operational continuity whilst the renewal is being processed.

If your subscription is not renewed, you will no longer be able to modify, save or publish workflows via the Nintex Workflow designer or modify, save or publish forms via the Nintex Forms designer. Published workflows will be suspended when a Nintex action is executed. The subscription expiry period will last for a period of 30 days, during which you can export any relevantNintex related data before the workflow expires. Once the 30 days are complete, any data stored on Nintex servers will be deleted and is not recoverable.

fhunth

Nintex Mobile Video in Spanish

Posted by fhunth Champion Dec 16, 2015

Baufest | Nintex Mobile: Manténgase productivo, esté conectado o no. (en español)

 

As part of a much larger case management system, a client wanted to have one form with multiple yes/no radio buttons. These questions act as gatekeepers: the user cannot proceed to the next question until the previous question has been answered.

nintex-yesno.png

 

I have written a blog post explaining how to set up the form and handle the output using SharePoint 2013 on premise + Nintex Workflows and Forms 2013.

 

http://sharepoint.hannahswain.eu/2015/11/20/nintex-workflow-and-form-with-multiple-yesno-radio-buttons/

In my previous blog post Advanced Calculated Values I wrote about using calculations in a Nintex Mobile Form to sum occurrences and points to my Warehouse Inspections demo. Using check boxes (or sliders) and input boxes, the form would calculate the sums. But we found that there are some user experience issues with the form. In this blog, I will show how to use rules within a form to improve the user experience.

 

Looking back, I had three types of user input to the inspection form.

  1. Add to the sum a multiple of a value. The multiple must be provided by the user.
  2. Add to the sum a fixed value
  3. Add to the sum a incremental value. If 1, then 25, if 2 then 75, if 3 or more then 300

 

Using Formatting Rules

 

The first input would allow the user to type in the input box even before they select the incident as occurred. I would like to disable the input box until the user slides the slider to indicate that there was an issue. To do this you click on the input box and then click Add in the rules pane as seen below.

 

Then configure the rule as a formatting rule, set to disable, then configure the condition using the fx button to the right. I set the condition formula to not(chk1) which will say that when it is not checked to disable the input box.

 

And the result is as follows

 

 

 

For the third selection I needed to disable the sliders for the various amounts when the initial slider was disabled. That was no problem as I simply added the same rule as before with not(chk3). But that was not all. The user could still select multiple values instead of just one. To remove that possiblity I added rules for each slider using formatting rules to disable the control if at least one of the other two were selected. Take the first slider for example. I named it chk3a, to disable it if one of the others were selected use the rule or(chk3b, chk3c). So if one of them were selected then that control would provide a TRUE value. The OR formula returns TRUE where either logical arguments are true. Returns FALSE when both logical arguments are False.

 

To follow this, for the second slider the formula was or(chk3a, chk3c). Then or(chk3a, chk3b) for the third. The results would appear as follows.

 

all values disabled until the incident is selected

Incident is selected, so now all three are enabled

Selecting the first one disabled the other two and so on.

 

Using Validation Rules

There are several ways to use validation rules in this scenario in Nintex Mobile forms. We could require at least least one incident to be reported, require a certain sum from the calculation, or require data from input fields at the beginning at the form.

 

But two important validations that became useful based on user feedback was to require a value to be inputted for the incidents that allow a number to multiply the points. This way the user would know they answered the form correctly and not accidentally left a field blank where a number greater than 1 was required. Because we assumed a multiplier of one when the slider was selected, this became possible. The formula used on this option was If(chk1, If(tv1<1, true, false), false). Let's break this down.

If the first incident was selected, then the input control is invalid if the value is less than 1. Otherwise it is valid.

 

Trying to submit the form without providing a value would result in the following

 

The last validation we added was a slider check box at the very end of the form. Imagine a form with dozens of questions. It may be very long and you want to make sure that the user checks on the total incidents and total points. In order to make sure the user saw this we added a slider/checkbox at the end with a simple label beside it. "Do you accept the total violations and total points?" A validation rule of not(chkLast) would make sure that it was checked, otherwise it was valid. Remember, the checkbox control provides a boolean value. So if it is checked, a TRUE would be returning. For validation rules, a TRUE value means the control is invalid. A little backwards, but it works. So if the use the "not" formula, we use the opposite. So if the slider is checked, then force the value to be FALSE, which means the control is valid. Read that a few times, and make sure you see the tooltip when creating formulas to help you with the intended value.

 

Summary

Hopefully these two posts were of help. This one was a little winded, but I wanted to make sure you could see the full example. This post reviewed how adding formatting rules and validation rules to forms (and Mobile forms) can improve the user experience. Let me know if you have questions and I will try to track the comments below. Happy Nintexing!

Nintex Workflow 2013

Nintex Workflow 2013 requires that the following software is installed and correctly configured:

  • Microsoft SharePoint Foundation 2013 or Microsoft SharePoint Server 2013
  • SQL Server 2008 R2 SP1, SQL Server 2012, or SQL Server 2014
  • Microsoft Windows Server 2008 R2 or Microsoft Windows Server 2012
  • Microsoft Internet Explorer 8.x although Microsoft Internet Explorer 9 or greater is recommended

 

Nintex Workflow 2010

Nintex Workflow 2010 requires that the following software is installed and correctly configured:

  • Microsoft SharePoint Foundation 2010 and/or Microsoft SharePoint Server 2010
  • SQL Server 2012 or SQL Server 2008 or SQL Server 2005
  • Microsoft Windows Server 2008 or 2008 R2
  • Microsoft Internet Explorer 7.x although Microsoft Internet Explorer 8 or greater is recommended

 

Nintex Forms 2013

Nintex Forms 2013 requires the following software is installed and correctly configured:

  • Microsoft SharePoint Foundation 2013 or Microsoft SharePoint Server 2013
  • SQL Server 2008 R2 SP1 or SQL Server 2012, or SQL Server 2014
  • Nintex Workflow 2013 v3.0.5 or higher (if using Nintex Forms with Nintex Workflow 2013)

Nintex Forms 2010

Nintex Forms 2010 requires the following software is installed and correctly configured:

  • Microsoft SharePoint Foundation 2010 and/or Microsoft SharePoint Server 2010
  • SQL Server 2012 or SQL Server 2008 or SQL Server 2005
  • Nintex Workflow 2010 v2.3.9.0 (if using Nintex Forms with Nintex Workflow 2010)

 

 

Nintex Workflow for Office 365

Nintex Workflow for Office 365 requires an Office 365 plan with the 2013 version of SharePoint Online. View details about Office 365, including plans and pricing, atoffice.microsoft.com/business.

Browser requirements:

  • Internet Explorer 9.0

  • Internet Explorer 10.0

  • Google Chrome latest release

  • Mozilla Firefox latest

 

 

Nintex Mobile

Nintex Mobile apps can be installed on devices running any of the following systems:

  • Microsoft Windows 8 for x86 platforms (32 and 64 bit) or ARM (eg. Microsoft Surface)
  • Apple iOS 5 or greater for iPhone, iPad or iPod
  • Windows Phone 8 or greater
  • Android 4.x or greater

SharePoint On-premises

Nintex Mobile App require at least Nintex Forms 2013 version 2.1.1 and Nintex Workflow 2013 version 3.0.3.0 OR Nintex Forms 2010 version 1.3 and Nintex Workflow 2010 version 2.3.9 to be installed and configured.

Office 365

Nintex Mobile App requires Nintex Forms for Office 365 to be installed and configured.

Please Note: Nintex Mobile App connected to Office 365 will only support Forms functionality. No workflow task capabilities are currently available.

There are so many applications to using the Nintex Mobile App. You can create items from forms, respond to tasks. Then we were given Mobile Enterprise to create our own apps with specified forms. To add to this we learned how to link directly to a form on our mobile app using the methods described in Dude you're so deep, Nintex Mobile deep linking that is..

 

As seen in the details of the help documentation, Nintex mobile linking uses the format nintexmobile://[{ACTION}][?{PARAMETERS}]

 

You can build Nintex Mobile links that perform the following functions.

  • Form navigation: Display a specific form in Nintex Mobile.
  • Authentication: Launch Nintex Mobile with pre-populated authentication fields.

 

Use Nintex Mobile links to ease deployment of Nintex Mobile in your organization.

  • Customers and employees can quickly access forms with form navigation-enabled links. They don't have to remember the form name or location. All they need to do is tap or click the link on their mobile device and then sign in.
  • Customers and employees can easily sign in with authentication-enabled links. They don't have to remember their authentication type, URL, or domain. All they need to do is tap or click the link on their mobile device and then enter a password.

 

All of this is explained in the links above, except how to find the form's ID in order to add the the parameters. So if we need to build the link nintexmobile://form?id=c0a89c70-0781-4bd4-8623-f73675005e00, then where does the guid come from.

 

Currently there are only two ways to get the Form's ID, but hopefully soon there could be new alternatives. The first method, if you have onprem SharePoint, could be to look inside the Nintex forms database. But a much easier method is to Export the form and examine the XML.

 

To export a form:

 

  1. Open the form that you want to export by accessing the Nintex Forms designer for the associated list or library.
  2. In the Designer tab of the Forms designer ribbon, click Export. The browser determines if the site is trusted and then initiates the file download process.
  3. Respond to prompts from the web browser to download and save the form

 

Once you have this xml file, open it in notepad and search for the tag <MobileId>

 

 

Copy out the GUID and place it after the nintexmobile://form?id= and send it in an email and click within your phone. That's it!.

 

 

I posted the suggestion to find the ID in a means of query or reference in the Uservoice, please vote!

For any form or workflow logic around user filtering and person or group value matching you will eventually run into working with the SharePoint claim. The actual value of the user within SharePoint. So as I respond to those posts I came across two blogs that explain what the formatting actually means for the claims and why i:0#.w|domain\user is used. I hadn't seen these before and I thought it to be helpful to post the explanation here to help others.

 

Joe Davies

Wictor Wilen

 

SharePoint 2013 and SharePoint 2010 display identity claims with the following encoding format:

<IdentityClaim>:0<ClaimType><ClaimValueType><AuthMode>|<OriginalIssuer (optional)>|<ClaimValue>

Where:

  • <IdentityClaim> indicates the type of claim and is the following:
    • i” for an identity claim
    • c” for any other claim
  • <ClaimType> indicates the format for the claim value and is the following:
    • #” for a user logon name
    • .” for  an anonymous user
    • 5” for an email address
    • !” for an identity provider
    • +” for a Group security identifier (SID)
    • -“ for a role
    • %” for a farm ID
    • ?” for a name identifier
    • "\" for a private personal identifier (PPID)
    • "e" for a user principal name (UPN)
  • <ClaimValueType> indicates the type of formatting for the claim value and is the following:
    • .” for a string
    • +” for an RFC 822-formatted name
  • <AuthMode> indicates the type of authentication used to obtain the identity claim and is the following:
    • w” for Windows claims (no original issuer)
    • s” for the local SharePoint security token service (STS) (no original issuer)
    • t” for a trusted issuer
    • m” for a membership issuer
    • r” for a role provider issuer
    • f” for forms-based authentication
    • c” for a claim provider
  • <OriginalIssuer> indicates the original issuer of the claim.
  • <ClaimValueType> indicates the value of the claim in the <ClaimType> format.

While creating a Nintex Mobile Form, I had a scenario that required I calculate the sums of values. Not very out of the ordinary, but in this scenario each calculation could have differing values. In this form are questions for an inspection form. In general, an office inspection to make user it is safe and secure. If there are issues, then report the point hit. If too many points then different actions will be required. On this form I had several questions asked, if the user checked the question answering Yes, then the related value could be calculated by:

 

  1. Add to the sum a multiple of a value. The multiple must be provided by the user.
  2. Add to the sum a fixed value
  3. Add to the sum a incremental value. If 1, then 25, if 2 then 75, if 3 or more then 300

 

There would be dozens of questions on the form all using one of the three methods above. So I would have to keep track of which question, which value, and what multiple in the calculated field.

 

First here are some screen shots of the form design.

 

And view in Nintex Mobile from a user

 

 

To keep track of the questions and their values I would name the controls like chk1, chk2, chk3 for the check boxes. For the multiplier MV1 for multiply value 1 related to chk1. For the choice of value, chk3a, chk3b, or chk3c.

 

The total violations calculated value was easy, just have it sum the check boxes checked.

 

I would use the formula If(chk1, 1, 0) +  as to keep the value working in case a question is not checked. For the addition to work I had to add 0, adding nothing would cause no value to appear in the sum.

 

To calculate the sum of the points was the unique part. See the configuration below

I would use the formula If(chk1, 500*(If(mv1>0, mv1, 1)), 0) + If(chk2, 100, 0) + If(chk3, If(chk3a,25,If(chk3b, 75, If(chk3c, 300, 0))),0)

 

For the first question, if it was checked, then multiply the defined value of 500 by the amount provided by the user. If they provide nothing, then have at least a multiple of 1, otherwise the number they provide. A good tip here is to make sure the value that can be provided in the field is set to Integer only.

 

For the second question, just see if it was checked, then provided the defined value, otherwise 0.

 

For the third question type, if it was checked as yes, then determine the values based on the other checked values. The If formula works as    IF(condition, true value, false value). I required nested if statements to make this work.

 

And that's it, just do this a few dozen times and tada! Cool Mobile form. I can even add attachments of the violations in question.

 

In my following post, I will show how to use validation and formatting rules to make this more user friendly. Take the scenario when the user could check question 3, but then checks both 1st and 2nd violation. How can we prevent that to not make it confusing?

This describes a bug found in this 2010 Nintex Workflow action:  Create item in another site.

(No worries: This has been reported to support)

 

When configuring the action, these errors occur when creating an item in a list with an Ampersand (&) in the Title (not in the url.)

 

When the title contains a Space ( ) and an Ampersand (&) in the title, these errors appear:

Warning: Error validating configuration. An error occurred while parsing EntityName. Line 1, position 40

Message from webpage: XML is not valid; CAML builder could not be populated.

 

 

When the title contains an Ampersand (&) with no preceding Space (  ) these errors appear:

Warning: Error validating configuration.  ‘  “ ‘ is an unexpected token.  The expected token is ‘;’. Line 1, position 47.

Message from webpage: XML is not valid; CAML builder could not be populated.

 

Note: Lists with these characters did NOT produce an error:

underscore ( _ )

exclamation ( ! )

Semi-colon ( ; )

At ( @ )

Pound ( # )

Dollar ( $ )

Percent ( % )

Asterisk ( * )

Left parenthesis (
(  )

Right parenthesis (
)  )

 

Work Around:  If you are stuck with the Title and process dictates that you cannot remove the offending character, just create a new list in the target site that is an exact duplicate of your target list.  Make sure the Title of the new list does not contain any offending characters.  Use the new list as a holding area. Write a workflow on this list to copy the items from this temporary list to the target list using the Copy Item or Create Item action to copy the item to the target list.  After the item is copied, delete the item from the temporary list.

If, like me, you don't want to give the users you support the opportunity to mistakenly (or mischievously) delete the list item whilst in the form interface, then this is for you.

Just insert the following script into the Custom CSS box of the Form Settings, before the other CSS already in there (so, it's easy to find):

On-Premise SharePoint 2013 Nintex Forms:

/*hide delete button in ribbon for Display form*/

#Ribbon\.ListForm\.Display\.Manage-LargeMedium-1

{

display:none;

}

/*hide delete button in ribbon for Edit form*/

#Ribbon\.ListForm\.Edit\.Actions\.DeleteItem-Large

{

display:none;

}

SharePoint Online 365 Nintex Forms:

/*hide delete button in ribbon for Display form*/

#Div1

{

display:none;

}

/*hide delete button in ribbon for Edit form*/

#RibbonDeleteButton

{

display:none;

}

 

I got this using a bit of trial and error based on previous posts I've seen elsewhere. Hope it is useful for others, too.

Since some months ago we have this feature Task Escalation comes to Office 365 and is the way you can configure it for delegations. This is an extract of that post.

 

There's a new section called "Escalate and auto-complete options".

NewSecttion.png

The default behavior, as you can see above, is "Do nothing".  Which really means, if someone is slacking off and not responding to a task, your business process is on hold.

 

The other options are :

  • Escalate to person or group
  • Auto-complete the task

 

Escalate to person or group

EscalateTo.png

 

You can specify when a task is going to be escalated.  But you don't have to have a static value.  Most likely, you'll be using an item field or a variable.  Probably a DateTime variable.  That opens up the usage here dramatically.  Not only can you specify when to escalate, but you can also add business or calendar days.  That's impressive and again, make this functionality so much more powerful.

 

Don't forget about the option to information the original participants.  You'll have the option to customize the email too.  This may actually help them in future tasks, knowing that if they don't respond to a task in a reasonable amount of time, it will get escalated/delegated.

 

As part of this process, if you're going to set an expectation that the task will be responded to within a set amount of time, make sure you update the email those goes to the original participant, to they are aware.  Also, don't forget to use Reminders!!.

 

Auto-complete the task

 

This is a piece of functionality where there is a person or group that is expected to respond. If they don't, there's no one else to go to.  So we want to automatically complete the task, and that could be Approve, Reject or one of the other outcomes.  The rest of the configuration is the same as the previous option.

Auto-complete.png

There is help available for all new functionality.

 

Help for Assign a Task

Help for Start a Task Process

Filter Blog

By date: By tag: