Sunny Chan

My feedback

  1. 38 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)
    Sunny Chan supported this idea  · 
  2. 4 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  ·  1 comment  ·  5 - Nintex Workflow Cloud » Other  ·  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)
    An error occurred while saving the comment
    Sunny Chan commented  · 

    In my case, our own developed form in my application will start a workflow instance on Nintex and the workflow will deliver an approval task to our users. And our user will do approval on our own developed form, instead of using Nintex form.
    On Nintex Form, approver can have additional fields to input to the task upon approval.
    But if we choose not to use Nintex Form, the API has no way to feedback any additional values on approval to the workflow. (only outcome is allowed)
    Some values like "Confirm Amount", "Reject Reason", may be critical to the flow afterwards.'
    Thats why we think that if API can allow this, this would be a better coverage against the functionalities with Nintex Forms.
    I think it would also be a great idea if Nintex can provide a custom action that can wait for user to provide the input.

    Sunny Chan shared this idea  · 

Feedback and Knowledge Base