Vikrant Behal

My feedback

  1. 40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vikrant Behal shared this idea  · 
  3. 27 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  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Vikrant Behal shared this idea  · 
  4. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Vikrant Behal supported this idea  · 
    An error occurred while saving the comment
    Vikrant Behal commented  · 

    While Component workflows are available for re-usability but that doesn't serve the use-case of associating workflows with specific content-type.

    It'll be great if Nintex can enable content-type level forms and workflows on Nintex Online platform.

  5. 22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vikrant Behal shared this idea  · 
  6. 20 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 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Vikrant Behal shared this idea  · 
  7. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vikrant Behal shared this idea  · 
  8. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vikrant Behal supported this idea  · 
    Vikrant Behal shared this idea  · 
  9. 21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vikrant Behal shared this idea  · 
  10. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vikrant Behal shared this idea  · 
  11. 35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vikrant Behal shared this idea  · 
  12. 641 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    42 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Vikrant Behal supported this idea  · 
  13. 6 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  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Vikrant Behal shared this idea  · 
  14. 75 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
    Vikrant Behal commented  · 

    It'll be great if Nintex can enable it for Web Request as well.

    Vikrant Behal supported this idea  · 
  15. 377 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Vikrant Behal commented  · 

    This is a must. As we continue to learn about Nintex Online, we realize that most of the features are not same as their on-prem counterpart.

    Vikrant Behal supported this idea  · 
  16. 258 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

    Please have a look at the condition builder just released as part of conditional start. Is this the kind of condition builder that you need in “wait for field change in current item” ?

    An error occurred while saving the comment
    Vikrant Behal commented  · 

    *Wait for item update* action in Nintex on-prem enables developer to use different operator based on need. Please enable operators in Nintex online action *Wait for field change in current item action*

    e.g. Status != Submitted

    Vikrant Behal supported this idea  · 
  17. 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.

    Vikrant Behal supported this idea  · 
  18. 99 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Vikrant Behal supported this idea  · 
  19. 55 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vikrant Behal supported this idea  · 
  20. 286 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →

    Hi All,

    This is currently a SharePoint limitation, however we have made sure that our lazy approval feature only allows people who are assigned a task to specify an outcome.

    As a workaround a user is able to query the task list to see who was assigned the task and who modified the task. We are looking at how make the task querying process easier. Thanks.

    An error occurred while saving the comment
    Vikrant Behal commented  · 

    What is the use of assigning task if anyone with Contribute permission can approve it? Should I just get approval over email?

    It'll be great if Nintex can Fast-track the development of this issue.

    Vikrant Behal supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base