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. Workflow action to convert Nintex Form to pdf

    With the recently release Nintex Forms enterprise feature to print to PDF, it would be great to access this functionality via a Nintex Workflow.
    As an example a Nintex Workflow could take a Nintex Form and generate a PDF file to be created in a library.

    670 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  44 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  2. Inline Function or Action to Calculate Business Days/Hours

    There are many scenarios when you need to take into account business days/hours for a workflow. One example would be setting a due date for something, and only wanting to do it based on business days. There is currently not an easy way to do this. It would be great if there were either an inline function or a workflow action that allowed you to calculate a date and factor in business days/hours and even holidays.

    600 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    44 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →

    Hey all,
    There looks to be 2 requests here
    - Update Inline function to allow calculate date difference, factoring in only business days / hours
    - Update Calculate date action to factor in only business days / hours
    Can you please share which of the two you require and your use cases
    Thanks
    Lisa

  3. Populate task id as soon as the task is created

    All task actions can populate a task id variable but usually populate the variable only after the task is completed by the assigned user. I would like to recommend that this behavior be changed so that the task id variable is populated when the task item is created and assigned. This way I can query the task item even before it's task action is completed.

    Please see my post on the forums https://community.nintex.com/thread/1451

    476 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Hardy responded

    The task ID is populated once the task is completed. Before this the task list items can be locked by the task engine for processing and a workflow accessing this task may fail. There has been therefore a strong reservation form our Engineering group to implement this capability even if technically feasible.

    If one wishes to delegate the task then the delegation should be used.

    Should you have other use cases for accessing the task list before the task is completed then please let us know what they are. There may be an alternative way of meeting this need that will not introduce the possibility of workflow failure.

  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.

    400 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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. Document Nintex Workflow solutions.

    Please make a export function to Aris or Visio, so we can document the solutions.

    326 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Hardy responded

    We are currently at the early stages of evaluating the whole topic of workflow documentation.

  6. Autopurge history list and workflow data

    We would like to have scheduled purge of Nintex history lists and workflow data after specified amount of time( say 6 months) for better performance. Can we have this option in Nintex management to setup a schedule and purge the data with required filters.

    Thanks,
    Rajkumar

    320 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  7. Improve Web Request action to support new input methods such as JSON

    Hi there

    For a long time XML was the de facto standard input notation for web service calls but there have clearly been changes to, and developments in, the available notations.

    It would be really good to see some of these new input methods being supported in the web service actions in the workflow product such as JSON.

    Thanks 

    267 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  12 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  8. workflow cancelled : choose to send email notification

    It would be great to choose whether to send a notification or not when a workflow is cancelled. Indeed, sometimes we need to cancel a workflow by using the "Terminate workflow" action or via the Nintex seb service and it is part of the normal process, it isn't an error or an unexpected behavior. That's why it could be useful to not send a notification in this case.

    265 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Find and remove unused variables

    There should be a way to list and remove unused variables in the Workflow Designer.

    The current approach (trying to delete individual variables to find out if the system throws an error message) is not convenient.

    264 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →

    This feature is now available from the latest versions outline below

    Nintex Workflow for SharePoint 2013 v3.5.2.0
    Nintex for SharePoint 2016 v4.5.2.0
    Nintex for SharePoint 2019 v5.1.2.0

  10. Nintex Workflow action to move documents across SharePoint sites with the option to preserve version history

    Considering archiving scenarios in SharePoint it would be great to have a Nintex Workflow action to move a document from a library of one site/site collection to another library of a site/site collection which keeps the version history of the document. Regarding the configuration of this workflow action it would also be great to pass a variable to define the destination URL.

    242 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  11. Restore deleted workflows from site recycle bin

    Provide ability to restore a deleted workflow from the site recycle bin. You can do this with SharePoint native workflows, but not with Nintex workflows.

    225 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Read document contents as Base64 into a Text Variable

    From documents in document libraries, to documents that are attached to list items and other scenarios, the need to read the contents of a document into Base64 format seems to come up fairly regularly.

    The data could then be used to call the Lists.asmx web service, specifically, the AddAttachment and attach it to another item.

    It would also be used to send to any number of other Line of Business systems, as Base64 seems to be the standard.

    An action that does that in Nintex Workflow would be ideal for this.

    221 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow administrator to edit long term delegation on behalf of other users

    Administrators can set a long term delegation on behalf of other users, but cannot modify or cancel them. Provide method for administrators to do this.

    210 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to Change a Managed Metadata column using Workflow Action

    Need an action that allows the workflow to change a column that is using a managed metadata term.

    Since there is apparently a way to do this via web services, how about this as a Feature Request for a new Workflow action?

    “The ability to specify a current item column that is set up as Managed Metadata, provide a new (valid) term, query the HiddenTaxonomyList for that term, get the ID and GUID, then update the given current item column.”

    This would be a HUGE help to those of us who want to actually USE Managed Terms and provide more…

    208 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  11 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enable updating list of approvers at runtime

    OOTB SharePoint approval workflows allow the initiator to "Add or update assignees of Approval", "Cancel all Approval tasks" and "Update active tasks of Approval". Can you add similar changes possible for Nintex users?

    191 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. More Advanced Conditions in RunIf Action

    Can we get more advanced options for conditions in a "Run IF" action? We need to be able to use parenthesis or indents that allows for grouping:

    Example of behavior:

    value1 = true

    (OR)

    value2 = true

    (AND)

    value3 = false

    The whole statement currently results in false. Logically, because the first statement is "True" and is followed by an "OR" so the whole statement should return true.

    II would expect it to evaluate to the following

    (value) OR ( value2 AND value3) = should result in true, if the first value is true no matter what the second grouping…

    167 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  17. Call web service with the credentials of the initiator

    It would be awesome to be able to call a web service with the credentials of the initiator. In the web request action, there could be an option to execute the request with the credentials of the initiator and there would be no need to populate crendentials manually or via a workflow constant.

    164 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add ability to store "Action ID" into a variable in a Flexi Task

    Currently available in a Request Approval action but not in a Flexi Task.

    163 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  8 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  19. Update hidden fields

    It would be AWESOME to be able to fill out field values for list items, even when they are hidden.

    This is really annoying not being able to do so.

    In a lot of workflows I want to set some fields automatically, to then use in my views, but I don't want to user to see those fields when creating/editing an item. The fields are supposed to be filled automatically, so it doesn't make sense to show them to the user, it is even confusing.

    Now, I resort to writing another webservice function and calling my function, which is of…

    143 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add "URL encode" and "URL decode" Action

    We meet situations quite often when need to create customized URL which is saved and used later for redirecting within or outside SP. For this purpose we need to encode input text to valid URL and save it.

    Opposite situation is for reading existing URL (decode) and parsing several elements for additional usage.

    While URL encode / decode is quite simple for programmer (few lines of code) but very difficult (or impossible) to perform with current tools such as "Build String" for WF designer.

    Existing/known workaround:
    http://www.vadimtabakman.com/nintex-workflow-url-encoding-user-defined-action.aspx
    Multiple embedded "fn-Replace" functions are not a good solution because there can be…

    137 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 33 34
  • Don't see your idea?

1 - Nintex Workflow for SharePoint

Categories

Feedback and Knowledge Base