Kazunori Matsuura

My feedback

  1. 49 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 » Workflow Designer  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for this suggestion.

    The way we are going to handle this is by creating two new actions, one for retrieving members of a SP Group and one for retrieving members of an AD group. Both these actions will output a object including a collection of users which can be used in the task action.

    An error occurred while saving the comment
    Kazunori Matsuura commented  · 

    Please consider lifting the upper limit of # of assignees for "Assign a task to multiple users" action. As of now, the max limit is 20. For example, a voting workflow application needs to involve more assignees in an enterprise group.

    Additionally, the action should be able to canceled by "Nintex Workflow Cloud - Complete a task". As I explained in another idea;

    https://nintex.uservoice.com/forums/430063-5-nintex-workflow-cloud/suggestions/44307258-enable-action-nintex-workflow-cloud-get-tasks 

    as of now, Nintex Workflow Cloud connector actions can't process any tasks generated by "Assign a task to multiple users" action. It could be a problem in a case where an operator wants to terminate unanswered tasks without stopping a workflow instance.

    --
    update Dec.21th

    By calling NWC API task v2 from Call Web Service action, I could query tasks generated by "Assign a task to multiple users".

    An error occurred while saving the comment
    Kazunori Matsuura commented  · 

    Due to the lack of SharePoint group support, I had to break down SharePoint group of approvers into group members by custom javascript of Nintex Forms classic form. But this workaround doesn't work for a group that contains more than 10 members now. This limitation is a severe problem for my customer who use workflow for technical review where the assignees are selected by a group of subject specific experts (>20 members). And my workflow design is complex and number of actions is over 200. These actions should be simplified by a single "Assign a task to multiple users".

    Kazunori Matsuura supported this idea  · 
  2. 186 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hi All,

    We are currently investigating options for this one. If anyone would like to discuss their specific requirements then I’d love to have a chat so please email me and we can setup a time to discuss further.

    Thanks, Rick

    Kazunori Matsuura supported this idea  · 
  3. 43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Under Review  ·  3 comments  ·  5 - Nintex Workflow Cloud » Connectors  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Kazunori Matsuura commented  · 

    "Get tasks" is an indispensable piece for transition from NWO365 to NWC. NWC does not offer "Workflow Tasks" list to SharePoint Online sites, so that the user must design workflows in order to write out ongoing task status to SharePoint custom list. Please refer to the attached screenshot of my custom solution. As of now, there is no way to indicate the ongoing tasks created by "Assign a task to multiple users" action.

    Kazunori Matsuura shared this idea  · 

Feedback and Knowledge Base