Philipp Hammer

← Customer Feedback for Nintex

My feedback

  1. Nintex Workflow action to move documents across SharePoint sites with the option to preserve version history

    248 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  1 - Nintex Workflow for SharePoint » Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Philipp Hammer supported this idea  · 

  2. Drag and drop support for adding attachments

    339 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    21 comments  ·  2 - Nintex Forms for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion.

    I will update this idea if there are any updates to share.

    Cheers,
    Euan

    Philipp Hammer supported this idea  · 

  3. Get previous field value in workflow

    410 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    13 comments  ·  1 - Nintex Workflow for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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.

    Philipp Hammer shared this idea  · 

Feedback and Knowledge Base

(thinking…)