1 - Nintex Workflow for SharePoint

This forum is open to any ideas and feedback for all of our on-premises Nintex Workflow products, including 2007, 2010 and 2013.

- The Nintex Workflow team

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Move Task form properties view setting to the task level

    Actually Task form properties view is a global setting defined at the farm level (in Global Settings in CA), could be very useful to set it at the task level, so each task, even in the same workflow, could have a different view

    14 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  2. Custom Text Color in Designer

    It would be great if there was a way to modify the text color inside the designer independent of the site text color. This way when changing the master page, or default site look, we can make sure that text inside Nintex is always visible.

    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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  3. Show the SMTP error that the mail was unable to send on View Workflow History page

    We request to add a function that is to show the SMTP error that the mail was unable to send on View Workflow History page

    We found the error was not showed if the mail is unable to send from “Send Notification” action causing by what the wrong mail address is registered on the user account.
    However this error is generated on the Nintex Workflow category of ULS log.
    Users are not able to note this issue that they are not able to receive the mail on time.

    30 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  ·  2 comments  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  4. Get previous field value in workflow

    As start workflow option to start a workflow you can set the "value differs from the old value" option. Nintex Workflow obviously has access to this information. Within the workflow you can not load the previous value into a variable or something else. That would be nice.

    Actually you have to use multiple hidden fields storing the previous value to use in for workflow porposes.

    410 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
    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.

  5. Yes/No column should return a Yes/No result - not a True/False

    When completing a form I'd like users to answer "yes" or "no" to particular questions. This information then get embedded in an email and gets sent out to multiple departments. But instead of the "Yes/No" field showing as "Yes" or "No" it instead shows as "True" for yes and "False" for no. This is not helpful, especially when emailing non-techie people within the company. Thank you.

    14 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  6. Option to cycle (disable then re-enable) Nintex workflow across a farm

    Several times over the last couple of years, after an update to the Sharepoint platform (2010) we've been left with Nintex WF running incredibly slowly on all the sites where it's in use.

    The recommendation from Nintex support, which often seems to work, is to disable and then re-enable the Nintex Workflow features at the site level. This is simple enough but a pain to do across a lot of sites.

    It woudl be very useful to have an option, or worst case even a powershell script for farm admins, that would look across all sites, store the current Nintex…

    5 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  7. Please list the default values on the workflow variable dialog that lists all of the workflow variables.

    Please list the default values on the workflow variable dialog that lists all of the workflow variables. Another nice feature would be able to assign a group and or comment. Variables could be sorted by group and or comment. A group might be Constants for example. Or Field Values. Whatever you wanted.

    7 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  8. Unpublish or disable a workflow

    It would be great to get a possiblility to disable or unpublish workflows. At the moment once the workflow is published, you cannot disable the workflow temporary. Sometimes that would be useful (eg. if you import a lot of data to a list, where you do not want to run the workflow).

    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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  9. Include ULS in Support Console

    Although the Support-Console already includes an extract of the ULS it would be more helpful if not the ULS from the time the Package is created would be included but instead from the time the error occured, because this is most likely the timeframe of most interest.

    15 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  10. Code Editor field

    For fields that are you to put in code (for example the Execute SQL action), it would be nice to have an editor that supported TAB indentations and used a monospaced font, so it was easier to get an overview of the code.

    7 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  11. Have a way to view hyperlinks in body of email for Send Notification

    When creating a "Send notification" and specifying a hyperlink inside the body of the email, there is no way to view what that link is set to. The only way to see that again is to view it using the HTML editor.

    There should be a way to click on the hyperlink text and see the actual URL behind it.

    36 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  12. Build the Workflow analyser directly into Nintex Workflow solutions

    The Nintex Workflow analyser is a great tool however it would be best placed being built directly into Nintex so that all end users can build workflows that align to the best practices.

    Updates to this should be delivered via a CU like install or definition upload for those SharePoint installs not internet accessible or via an auto update solution controlled within the Nintex area of SharePoint Central Administration for uploads etc

    Workflow analyser can be found at https://community.nintex.com/community/build-your-own/blog/2015/07/17/workflow-analyzer-version-14037-released?utm_source=Twitter&utm_medium=social-post&utm_campaign=July2015-Connect-WorkflowAnalyzerUpdate

    This would make sure that workflows are authored with best practises suggested and is a great sell point from IT to…

    12 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  13. Edit UDA in Central Administration

    Right now after promoting a UDA to farm level, it is not possible to edit it in Central Administration.

    84 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  14. Single function to maximize all action sets, switches, etc

    I would like to have a easy way (preferably a single click) to maximize all action sets, switches, loops, etc. This is especially useful for a large workflow when you want to search for a certain keywords which can't be found when in minimized mode.

    16 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  15. Undo and redo buttons

    At the moment, if a workflow action is deleted, there is no way to go back unless close the designer without saving it. Having the Undo and redo buttons would be very useful if a group of actions were deleted by accident. For example, I made lots of changes on a workflow and didn't save the change and then I deleted an action set action, but then realize I only need to delete the action set not all nested actions. The undo button would be very handy.

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  16. Promote Save Button to the Top Nav Bar

    Promote the save button to the same top level as the undo and redo buttons and tab headers so it can easily be accessed from any screen.

    4 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  17. Disable [BACKSPACE] key

    Would be good if the designers (forms and wf) both disabled the backspace key when a textbox is not in focus. If you accidentally hit that key, the browser picks it up as a history.go(-1) and you lose all your changes.

    4 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  18. NWAdmin or Web service for exporting all UDAs in farm

    We would like to have NWAdmin command or web service that can export all UDA in farm.

    Exporting UDAs manually is sometimes unrealistic.

    38 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  19. Setup cascading functionality with external content type

    How can I apply cascading filter on 2nd External Data Column using 1st External Data Column selected value

    7 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  20. Saving snippet- include only variabled used in the snippet

    When saving Action Set as a snippet, all variables currently used in a workflow are included. When adding this snippet to another workflow, all these variables are of course copied over- which ends up in adding significant number of variables that are not used.
    It would be much better if only variables used in the snippet were included and provisioned when adding snippet to a new workflow

    48 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  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

1 - Nintex Workflow for SharePoint

Categories

Feedback and Knowledge Base