Alan McCollough

My feedback

  1. 238 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Alan McCollough commented  · 

    As a Farm Admin, I find it a bit irritating that I can delete site collections, web applications, or THE ENTIRE FARM, but I cannot remove a delegation on behalf of a user.

    Alan McCollough supported this idea  · 
  2. 410 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  Jon Hardy responded

    Without going into the technical detail; the previous value made available in conditional start is actually the current value just before any updates are made to the item. When the item is updated, we lose the ability to get the value prior to the update.

    To restate the workaround as indicated in the idea; create an additional column in the list or library and update this with the current value of the column of interest. Then when the actual column is updated, the previous value is still available in the additional column. Of course one need not make this additional column visible in the view or Form so the users are not confused.

    An error occurred while saving the comment
    Alan McCollough commented  · 

    I would love to see this functionality, and you know it already exists. Workflows allow for testing against previous values as part of the conditional execution evaluation. Use that same logic in the "Set a Condition" action. Either that or provide a mechanism for assigning previous values to Nintex variables that we can use within the workflow.

    Alan McCollough supported this idea  · 
  3. 264 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    This feature is now available from the latest versions outline below

    Nintex Workflow for SharePoint 2013 v3.5.2.0
    Nintex for SharePoint 2016 v4.5.2.0
    Nintex for SharePoint 2019 v5.1.2.0

    An error occurred while saving the comment
    Alan McCollough commented  · 

    YES, it would be excellent if there was a "Remove unused variables" checkbox on the Workflow Settings form. I have a lot of snippets that I use, and they've got variables in there which get grafted in. Now these snippets, sometimes I'm just using 20% of it, and delete the remainder; but still get all the variables, be they used in the final workflow or not.

    Alan McCollough supported this idea  · 
  4. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Alan McCollough shared this idea  · 
  5. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Alan McCollough commented  · 

    Splitting workflows is a Good Thing. You should consider yourself lucky that huge workflow works at all.

  6. 94 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Alan McCollough supported this idea  · 

Feedback and Knowledge Base