Vamsi

My feedback

  1. 373 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)
    Open for voting  ·  Euan Gamble responded

    Hi all,

    There is no movement on this feature at this time. If the status changes, I will update this ticket.

    Cheers,
    Euan

    Vamsi supported this idea  · 
  2. 379 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)
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion.

    I will update this idea if there are any updates to share.

    Cheers,
    Euan

    Vamsi supported this idea  · 
    An error occurred while saving the comment
    Vamsi commented  · 

    Attachment control in task forms has become a bottle-neck in recent project for me and below is why.

    One of the strong feature of Nintex workflow is the integration of Nintex Forms and the control workflow ( business process ) has over forms when compared to InfoPath forms being in sync with workflow step. I like the fact that the end user can update the List Item from task form and also finish the task at the same time ( Love Flexi task !! ) but the fact that Nintex doesn't allow the add an attachment to the list item using tasks forms puts me in a tough spot while designing solutions as I can provide just one form per task and set the new standards for all the applications except if they have a task to upload the attachment then the user has to attach the document and later finish updating the task.

    There are multiple solution over the internet ( UDAs , Copy Item to Library..etc) I personally think that these options are overkill. I would request Nintex product to fix this in the next release ( Christmas gift from Nintex )

    Nintex fundamental tag line is workflow for everyone and this makes it questionable as this is quite basic and reasonable to expect and I hope Nintex fixes this soon.

    Vamsi shared this idea  · 

Feedback and Knowledge Base