Abhijith R Shastry

My feedback

  1. 72 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhijith R Shastry supported this idea  · 
  2. 24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    I support this idea as it would help organizations build powerful workflows, and begin to eliminate the dependency of using PowerShell (at least a bit)

    Abhijith R Shastry supported this idea  · 
  3. 137 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Abhijith R Shastry supported this idea  · 
  4. 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

    An error occurred while saving the comment
    Abhijith R Shastry commented  · 

    Hello Roanna,
    Below is one of the many scenarios - Think about you call the 'Create Site' action from the workflow after which, you need to perform all the listed actions.

    In my opinion, the order specified in the above list can be considered the order of priority.

    Best Regards,
    Abhijith

  5. 70 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhijith R Shastry supported this idea  · 
  6. 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.

    Abhijith R Shastry supported this idea  · 
  7. 51 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhijith R Shastry supported this idea  · 
    An error occurred while saving the comment
    Abhijith R Shastry commented  · 

    Thanks Santoshi for creating this post.

  8. 22 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
    Abhijith R Shastry commented  · 

    At least by now, Nintex should have provided ability to delete permanently. Since this is very much possible through Client-Object Model, it should be made available through workflows too.

    Abhijith R Shastry supported this idea  · 
  9. 28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhijith R Shastry supported this idea  · 
  10. 26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  3 - Nintex Workflow for Office 365 » Runtime  ·  Flag idea as inappropriate…  ·  Admin →
    Abhijith R Shastry shared this idea  · 
  11. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhijith R Shastry supported this idea  · 
    An error occurred while saving the comment
    Abhijith R Shastry commented  · 

    Please have this action in Site-Workflows, with configurable source and destination URLs. I do not know why it is still not there, after so many versions of Nintex Workflow being rolled-out.

  12. 32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhijith R Shastry supported this idea  · 
  13. 1 vote
    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 →
    Abhijith R Shastry shared this idea  · 
  14. 94 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhijith R Shastry supported this idea  · 
  15. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhijith R Shastry supported this idea  · 
  16. 14 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  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Abhijith R Shastry supported this idea  · 

Feedback and Knowledge Base