Roger

My feedback

  1. 410 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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.

    Roger supported this idea  · 
    An error occurred while saving the comment
    Roger commented  · 

    Agreed! In order to capture this previous value data I've had to create a whole separate list to be able to compare against. I know that I could extract the previous value from the xml with some javascript, but if I wanted to write code why would I be using Nintex? :)

  2. 102 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Roger supported this idea  · 
    An error occurred while saving the comment
    Roger commented  · 

    I was thinking that something along these lines would be great! I would add that it would be good to have any action be tagged Test or Production and with different color coding. Maybe red for Testing and green for production. Then when the production switch is on only those actions run.

  3. 119 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  1 - Nintex Workflow 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)
    Roger shared this idea  · 
  4. 76 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  2 - Nintex Forms 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)
    Under Review  ·  Euan Gamble responded

    Thanks for your suggestion Cassy. With Universal Forms, you will be able to set the value of any control. I just tested setting the People Picker control in a test environment.

    Would the person be hardcoded in the rule? Or would you expect a UserProfileLookup runtime function output to populate the field? Let me know in the comments below.

    Cheers,
    Euan

    Roger supported this idea  · 
  5. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Roger supported this idea  · 

Feedback and Knowledge Base