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.

    698 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  ·  50 comments  ·  Workflow Actions  ·  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)
  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.

    674 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    48 comments  ·  Workflow Actions  ·  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)
    Under Review  ·  Lisa Tam responded

    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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Workflow Actions  ·  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)
    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. 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

    323 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Workflow Actions  ·  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)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  12 comments  ·  Workflow Actions  ·  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)
  6. 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.

    248 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  ·  Workflow Actions  ·  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)
  7. 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.

    235 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Workflow Actions  ·  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)
  8. 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…

    211 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  ·  11 comments  ·  Workflow Actions  ·  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)
  9. 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…

    188 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Workflow Actions  ·  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)
  10. 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.

    168 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Workflow Actions  ·  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)
  11. 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.

    166 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  ·  8 comments  ·  Workflow Actions  ·  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)
  12. 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…

    158 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  ·  Workflow Actions  ·  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)
  13. 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…

    146 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Workflow Actions  ·  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)
  14. Add Error Handling to UpdateItem

    Looping through many or all of the items in a library is a common development requirement. A typical workflow might be a Query List followed by a For Each loop that contains UpdateItem.

    Sometimes the UpdateItem might fail for reasons like the item is checked out.

    There should be a way for the workflow to continue to the next item if the update fails and not have the workflow fail.

    114 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  ·  Workflow Actions  ·  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)
  15. A fn-find() so that you can find the first position of a character or string.

    As far as I am aware currently there is no fn-find function for a string. So you can use a loop to check each character or maybe a regular expression but if you need to perform a mid, insert etc then it would be handy to do some sort of fn-find to result the position of particular text

    108 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  ·  Workflow Actions  ·  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)
  16. Voting Option for Flexi-Task

    Some of our document approvals require a group of people to vote on a number of options (if they disagree, it goes on to another level). It would be very useful to be able to assign people to a single task with a number of options, wait for them all to respond, then have the number of votes for each option assigned to a variable.

    102 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Workflow Actions  ·  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)
    Open for voting  ·  Lisa Tam responded

    Hi all, this is currently not on our near term roadmap but I have opened for voting and we will continue to monitor.

  17. Server-Side JavaScript and JSON support

    Should be able to complete all REST api actions in NWF and parse JSON. SharePoint is moving away from asmx.

    102 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Workflow Actions  ·  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)
  18. Disable Safe Loop on a per workflow basis.

    With Safe Loop enabled, each loop will take 5 minutes to run. So if you have a large amount of items to loop through this could be prohibitive. But the idea of safe looping is sound. It would be nice if you could disable safe looping on a per workflow basis. That way I'm acknowledging that this workflow has been OK'd to bypass the safe looping, but it doesn't disable it for the entire farm.

    94 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  ·  Workflow Actions  ·  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)
  19. Extend the Action Set action to include error handling

    It would be awesome to be able to handle unexpected errors in a workflow for a subset of actions. Since the Action Set action is already a container for other actions, it would be helpful to extend it so I have more granular control on unexpected errors that might occur in a workflow. Similar to the Try... Catch concept in C#.

    92 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  ·  Workflow Actions  ·  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)
  20. Provide Actions for some Basic SharePoint activities

    It would be helpful if you provide actions for some basic SharePoint scenarios that are currently missing the Nintex Workflow 2010 set of actions.

    A few are -
    1. Assign Site Permissions
    2. Assign List Permissions
    3. Add new Column(s) to a List
    4. Associate Content Type(s) to a List
    5. Create Site Content Type(s)
    6. Create Site Column(s)
    7. Create folder(s) in a Library

    I know all these activities are possible through the Web-Service action of Nintex. However, it would save lot of development time to have predefined actions in Nintex for them. Calling web-service makes sense for any…

    89 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  ·  Workflow Actions  ·  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)

    Hi All,

    With each of the requested actions could you please tell be what scenarios you are using each of them? From the list could you please order them in most important to each import?

    Cheers,
    Roanna

← Previous 1 3 4 5 17 18
  • Don't see your idea?

1 - Nintex Workflow for SharePoint

Categories

Feedback and Knowledge Base