Mark Uden

My feedback

  1. 18 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
    Mark Uden commented  · 
    Mark Uden supported this idea  · 
  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…)
    Open for voting  ·  Lisa Tam responded

    Hi all, this is currently not on our near term roadmap but I have opened for voting and we will continue to monitor.

    An error occurred while saving the comment
    Mark Uden commented  · 

    If anyone is interested, I'll be hosting a 5th birthday party for this suggestion in 6 weeks time.

    Nintex probably won't make it to the party because they're still busy reviewing the request.

    An error occurred while saving the comment
    Mark Uden commented  · 

    @Andi: If you filter the requests by status=complete (currently 9 items, with 63 "under review), it looks like Nintex are prioritising the easier ones rather than those with the highest votes. I'm not convinced they are even looking at this site anymore.

    Mark Uden shared this idea  · 
  3. 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
    Mark Uden commented  · 

    I also find it hard to understand why this wouldn't be a feasible function. If a workflow can be initiated based on a change in a particular field, surely it must be possible to retain the previous values in some way at that stage and make them available to the workflow? Alternatively, for lists with versioning, it should be possible to create an action that would make it easier to extract values for a field at each version into a collection variable.

    Mark Uden supported this idea  · 
  4. 28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  5. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  6. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  7. 56 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
    Mark Uden commented  · 

    I'd love this change, but I suspect it's not possible. My understanding is that UDAs are embedded into the workflows that utilise them, a bit like an auto-updating chunk of reusable workflow. If your UDA called itself, you would have an indeterminate chain of UDAs and this would be impossible to embed within a workflow. What we really need is an alternative to a UDA which actually acts more like a function in JavaScript, where workflow and functions it called were entirely separate.

  8. 152 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  9. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  10. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  11. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  12. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  13. 89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hi All,

    With each of the requested actions could you please tell be what scenarios you are using each of them? From the list could you please order them in most important to each import?

    Cheers,
    Roanna

    Mark Uden supported this idea  · 
  14. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  15. 52 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  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Uden supported this idea  · 
  16. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  17. 18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  18. 15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  19. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
  20. 22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Uden supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base