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. Flexi Task - ability to record all responses

    It would be great if there was the ability to record all responses, irrespective of the outcome within a Flexi Task

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  2. No way to identify workflow from history details screen

    When a user views the Workflow Details screen by itself (say in a screen capture) there is no reference to the name of the workflow for which those details have been captured.

    View Workflow History -> Workflow Name -> Click here to show detailed view -> Workflow Details

    Perhaps the workflow name could be added to this screen in a future release?

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Office365/SP2013 App Model Environment and Approach

    Nintex has predominately been focusing on the Office 365/SharePoint 2013 App Model environment and approach. They have not determined their strategy for on-premises other than to continue using the Full Trust Code in SharePoint 2013 and the deprecated SharePoint 2010 Workflow Engine at this time.

    They did say however, going forward, that they do not want to support multiple solutions, and since the App Model is the new Microsoft direction, that they will probably be moving in a Provider Hosted on-premises solution.

    A better understanding of the Nintex roadmap and migration approach is clearly needed.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Waiting or Watch task and continue Workflow on task creation

    A possibility to add a approver Task an let workflow continue without waiting for his input.
    The idea behind is to have a wating task that is diplayed in the my workflow tasks.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  5. The Calculate Date function should allow date formatting

    The Calculate Date function should allow date formatting as part of configuration options, without having to resort to ANOTHER action to format the output.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  6. Workflows on page level

    Would love capability to add workflow at a page level. For example, setting a workflow to kickoff when a page is created/modified to do various things such as approval, publishing, etc.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ability to not restart a workflow if the document is updated by the workflow

    i Am updating a document with version and document numbers in the footer but each time the version number are updated the workflow want to restart.

    It should be restarted if a user updates the document but not if it is saved and the version updates.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  8. Row Item Variable

    Hello,

    Often I have to work with multiple items at a time, which means I have to save each column of each item into a collection, and then loop through these collections get all the values from all the columns. This becomes a big task when there are a lot of items with a lot of columns.

    It would be really cool if you could create an "item variable" which essentially would contain all of the item's columns within it. This way we could easily loop through a single collection and do things with this "item variable" such as creating…

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  9. Workflow Tasks for Web Application

    I am using the Workflow Tasks web part to show all pending tasks for users, however in order for them to see all their task in the Web Application I have to choose "Farm" as an option, which also displays their tasks from the test system - same Farm, different Web Application. Although there are options for Site and Site Collection, there is no option for "Web Application".

    Is there any way to get this functionality, which seems like a strange omission.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Web Parts  ·  Flag idea as inappropriate…  ·  Admin →
  10. Action that would upload a video from a document library to YouTube

    Perhaps an action can be built that would allow a workflow built on a document library to automatically upload a video file to a users YouTube channel.

    Google has a publicly facing API that could be leveraged:
    https://developers.google.com/youtube/v3/

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Maintaining version numbers across environments for a workflow definition

    We never build workflows directly in the production environment, but rather in a test environment first and after testing then export our workflows to the production environment. Since versioning for the workflow definition is based on the number of times the workflow is published in a environment it is difficult to know if my test environment workflow or the production one is the latest version. It would be advantageous if a versioning number is tracked inside the workflow definition itself.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  12. Expand Logging Capabilities

    Expanding the amount of text that can be logged to the Nintex Workflow History would be very helpful. Right now the output seems very limited (I believe to 256 chars). Sometimes it is necessary to log what is in an XML file or other long pieces of text. If you could increase the amount of text able to be logged that would be fantastic.

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  13. Read and Write Property Bag items

    It would be great to be able to get SPWeb Property Bag values - and also SET the values within a web.

    These are often used to store "about a web" properties - but can only set via code (C#) - or CSOM (JS).

    Eg. When we use a Nintex Workflow to create an SPWEB, also add a property such as 'locale' - and then can use that to display an icon on the site home page.

    Many other uses - there is a custom action BLOG post about this - but would be good to have within the core…

    72 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  1 comment  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  14. Migration

    Since a Nintex workflow can become quite complex with lots of information coming from multiple locations it would be great to be able to define all the pieces and parts that are needed for that workflow to run (a report of some sort). Further, once a designer/developer has created a workflow with all it's part and has unit tested the hell out of it, allow them to perform a save that pulls together all of the components into one Migration package / file / folder etc... so that when moving a workflow to a QA server it doesn't take manual…

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  15. Disable custom javascript or provide more granular control.

    Business users will rarely ever need JavaScript. SharePoint can be locked down to restrict it's usage, it only makes sense that Nintex also allow for this because XSS using JavaScript is one of the top 10 most serious security threats as listed by OWASP.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Access to item history data within a workflow

    As start condition you can compare current and previous value of a field but not within the workflow.
    These would be useful in e.g. a mail action to inform users about specific changes on the list item or other use cases.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  17. Save and Continue option

    While it’s on my mind, one for the suggestion basket: Suggest adding an option to the Save dropdown menu that is in the vein of “Save and Continue” which would allow the user to save without having to go through the popup confirmation window and just return the user to the editing stage. Alternatively, it might work to allow one to set the behaviour of the Save button itself to that (presumably on a per-user or per-session basis).

    :)Ben

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

    Thanks for the feedback Ben. I am interested to know what the driver of the request is? Is it simply best practice saving every now and again, or is it due to the browser potentially crashing and losing your work? If it’s the latter, would some form of AutoSave assist?

  18. NWAdmin purge WorkflowHistoryList update

    Please consider adding the ability to permanently delete Workflow History List items (use List.delete() instead of List.Recycle() ) when using PurgeWorkflowHistoryList nwadmin command. The process of emptying the recycle bin after purging 100’s of thousands of history items is quite time consuming even via powershell.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Active Site or SiteColllection features with Nintex Workflow

    It would be great if an action exists that can activate features. This can be used in several provisioning workflows. After creating a new site / site collection some features can be activated with Nintex Workflow.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  20. Specify MIME type for file attachments

    When we attach PDFs to emails, the workflow uses an application/octet-stream MIME type. Most applications expect an application/pdf MIME type. It would be helpful to be able to specify the MIME type for file attachments.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Workflow Actions  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

1 - Nintex Workflow for SharePoint

Categories

Feedback and Knowledge Base