Deanna Velasco

My feedback

  1. 18 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 » Formulas  ·  Flag idea as inappropriate…  ·  Admin →
    Deanna Velasco supported this idea  · 
  2. 17 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  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Deanna Velasco supported this idea  · 
  3. 213 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  ·  5 - Nintex Workflow Cloud » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Deanna Velasco supported this idea  · 
  4. 45 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  ·  4 - Nintex Forms for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Deanna Velasco supported this idea  · 
  5. 38 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  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Deanna Velasco commented  · 

    Yes. Hiding or disabling the submit button would prevent a lot of issues we see where someone opens the form just to look at it while at the same time someone else has the form open to edit it. The editing person submits the form and their changes get saved to the list item, but then the person that was just looking at the form, also hits submit which then submits all of the old information in the form back to the list, overwriting what the other person just added.

    If I could disable or hide the submit so that users can't click it unless they actually updated information (based on a rule I create) then it would prevent me from having to go in and fix these issues.

    Deanna Velasco supported this idea  · 
  6. 3 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 →
    Deanna Velasco supported this idea  · 
  7. 92 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Any updates on this? like the others, I am not understanding why this request is being ignored.

    Deanna Velasco supported this idea  · 
  8. 54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Deanna Velasco supported this idea  · 
  9. 201 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 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Deanna Velasco supported this idea  · 
  10. 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 →
    An error occurred while saving the comment
    Deanna Velasco commented  · 

    I appreciate the ability to track suspended workflows but we also need to be able to get notified about terminated workflows. We have had several system terminated workflows that we had no idea about until users complained the list item wasn't moving along as expected.

  11. 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 →
    Deanna Velasco supported this idea  · 
  12. 17 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
    Deanna Velasco commented  · 

    I am running into the same issue.
    If I assign a task without Lazy Approval, then the notification goes to our spam folder in GSuite. No one will ever see it.
    If I turn on Lazy Approval with email only, we can get the notification in our inbox but the subject contains the token code characters which makes it look like spam so users are hesitant to open the email.
    We don't really want Lazy Approval. I just need the task notifications to go directly to our inboxes in GSuite.

    Deanna Velasco supported this idea  · 
  13. 699 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    To support this requirement we’ve just release the following features

    - Specify a customizable sender display name for both email and task actions, we understand one of the main requests was to be able to supply a custom from email address however due to many of the limitations in the cloud we are currently unable to deliver this request and so hopefully being able to add a From display name will get you one step closer..

    - Add a customizable Reply To email address for the email action so you can control the email address when people hit reply.

    Hope you enjoy these features and be great to hear any feedback once you try them out.

    An error occurred while saving the comment
    Deanna Velasco commented  · 

    Changing the email address of the sender is what we need as well for all of the exact same reasons the others have posted. Why is it that Flow and other software vendors can do this?

    Deanna Velasco supported this idea  · 
  14. 147 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
    Deanna Velasco commented  · 

    This is greatly needed as we auto populate the senders of an email to our helpdesk so that the sender is the creator of the ticket and they can keep track of the status. We used to be able to do this in the previous workflow vendor we used, but now that we've migrated to Nintex, it is a problem we can't do this.

    Deanna Velasco supported this idea  · 
  15. 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” ?

    An error occurred while saving the comment
    Deanna Velasco commented  · 

    Bump on this. Waiting for a field to change is greatly needed with "Contains, Not Equal, Begins with, Ends With. At least Not Equal to so that we can compare if the Item is Modified" like the others have said.
    I am currently using "Wait for event in list item" but it's not working properly. Even though I have it to trigger when this list item's GUID is changed, It's actually triggering every time any item in the list gets updated, so my workflow is continuously looping, bogging down the environment.
    I can't use the current Wait for Field Change in Current Item because it requires only a "equals" a value, which is not helpful in my situation at all.

    Deanna Velasco supported this idea  · 
  16. 698 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
    Deanna Velasco commented  · 

    I am a new Nintex customer (using mainly NWC) and during my development I just realized we can't ever view a completed form and this honestly shocks me. We keep our completed forms for many years for auditing and legal archive requirements and most of our processes will require this. We should not have to pay extra money for such a simple requirement. With almost 700 votes, why isn't this made more of a priority with the development team?

    Deanna Velasco supported this idea  · 
  17. 9 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  ·  5 - Nintex Workflow Cloud » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Deanna Velasco shared this idea  · 
  18. 19 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  ·  5 - Nintex Workflow Cloud » Workflow Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Deanna Velasco commented  · 

    Yes this would be very helpful so that we could easily and efficiently reference those files throughout the workflow in forms without having to create so many steps to pull them back in from the list item and loop through each!

    Deanna Velasco supported this idea  · 
  19. 42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  3 comments  ·  5 - Nintex Workflow Cloud » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Deanna Velasco commented  · 

    The situation is this: A form routes to different people and those different people are allowed to make edits to those fields. If the field is a data lookup, it is not possible to 1) display the previously selected value at the same time as 2) allowing the options for the data lookup.
    I think if we can set a default value from a list or start event variable, then it should show that value first in the data lookup field but the user could click on that field and change it based on the other values returned from the data lookup connection.

    This situation is very common for many of my forms.
    I hope you will consider this.

    Deanna Velasco supported this idea  · 
  20. 55 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  ·  5 - Nintex Workflow Cloud » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Deanna Velasco supported this idea  · 
← Previous 1

Feedback and Knowledge Base