annoyednintexuser

My feedback

  1. 359 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    over 3.5 years ago and still nothing. also one of the top voted on ideas. this is the reason we are switching to flow and/or building apps our selves because we cant get a simple length function in a workflow.

    annoyednintexuser supported this idea  · 
  2. 73 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  ·  Flag idea as inappropriate…  ·  Admin →
    annoyednintexuser supported this idea  · 
  3. 255 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” ?

    annoyednintexuser supported this idea  · 
  4. 70 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 » Runtime  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the great suggestion guys, I’ve added this backlog and will keep you updated on a time frame on when we can deliver this feature update. Would love to hear any other thoughts/suggestions on how we can make component workflows even better..?

    annoyednintexuser supported this idea  · 
  5. 86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hi Sridhar,

    The issue we currently have is the workflow engine does not send us any kind of event to indicate that the component workflow (or any workflow) has suspended meaning we can’t send any notification back to the parent workflow. We are currently talking with Microsoft to see if they can provide us the info we need, will update you once we know more..

    Cheers, Rick

    An error occurred while saving the comment
    annoyednintexuser commented  · 

    been under review for over a year now.. are you all making any progress on this feature?

    annoyednintexuser supported this idea  · 
  6. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

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

    Our client side scripting works without hiccup within our Online environment but nintex takes forever. Flow even works more quickly, has better action support and inline functions, these issues are not a microsoft issue.

    annoyednintexuser supported this idea  · 

Feedback and Knowledge Base