KokKoon.Gan

My feedback

  1. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  5 - Nintex Workflow Cloud » Connectors  ·  Flag idea as inappropriate…  ·  Admin →
    KokKoon.Gan shared this idea  · 
  2. 3 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  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    KokKoon.Gan shared this idea  · 
  3. 36 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    KokKoon.Gan supported this idea  · 
  4. 11 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  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    KokKoon.Gan shared this idea  · 
  5. 18 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  ·  Euan Gamble responded

    Thanks for your suggestion.

    I will update this idea if there are any updates to share.

    Cheers, Euan

    KokKoon.Gan supported this idea  · 
  6. 2 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  ·  5 - Nintex Workflow Cloud » Runtime  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    KokKoon.Gan commented  · 

    Hi mate,

    The concept/idea presented here is very different and with different opbjective than the External Start with "Output" variables. Let me try to provide more details here:

    We can now call/trigger Nintex Workflow Cloud's External Start workflow today with the following payload.

    {
    "startData":
    {
    "se_firstname_11": "John",
    "se_secondname_21": "Smith",
    },
    "options":
    {
    "callbackUrl": "https://callbackurl.com"
    }
    }

    This is great as the workflow once completed will be able to make a callback to the "callbackurl".

    Now, as the External Start workflow only understand the payload of above (i.e. with "startData"), we can only parse the payload to take passed parameters/values into the workflow's variable(s).

    If a External Start workflow besides parsing the mentioned payload, it also take the entire payload/request content into a variable. We can now make the External Start as a service endpoint for "call back" purpose. Meaning we can now parse the return of another workflow of the following content:

    {"returnData":
    {
    "c_status":"Review",
    "se_firstname_11":"John",
    "se_secondname_21":"Smith"
    },
    "workflow":{"id":"a58a5b90-eda6-41af-8acb-00fe299c68a6",
    "name":"",
    "publishedId":"3cace836-0323-4f79-b56f-5480bf79aab7"
    }
    }

    This External Start workflow is now handling the return/ reponse of the first External Start workflow, and process the returns the way we want it. Such as feeding that responded data to Sharepoint Online list item, etc.

    Support of "callbackurl" in the return is good, but it is not easy to implement, as we need to create endpoint to receive the response from the called "External Start" workflow. Now, with this idea, we can simple turn another "External Start" workflow as the endpoint for the callback.

    Hope that clarifies.

    KokKoon.Gan shared this idea  · 
  7. 3 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  ·  5 - Nintex Workflow Cloud » Runtime  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    KokKoon.Gan commented  · 

    I have another idea shared “Capture of Request Content in workflow variable” https://nintex.uservoice.com/forums/430063-5-nintex-workflow-cloud/suggestions/19736107-capture-of-request-content-in-workflow-variable
    This idea allows a workflow in Nintex Workflow to capture the request content/body, if this idea is supported, we can make Nintex Workflow Cloud’s workflow as a “callbackurl” once a workflow responded to this workflow, the final workflow can do something such as update external system with the initiated workflow’s result.

    An error occurred while saving the comment
    KokKoon.Gan commented  · 

    adding more details to the idea... basically this turns a Nintex Workflow Cloud into a RESTful Web Service method. It will be a challenge as a workflow might take days to be completed especially if it handles pending stage such as waiting for someone to approve a task.

    As such, setting criteria for this idea to work is critical. E.g. only if the workflow has no wait/pending stage/action(s) involved, or else it will return message such as "immediate response not supported".

    Expected return of value(s)/response could be identify by the "Output" variable as it supports today.

    KokKoon.Gan shared this idea  · 
  8. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    KokKoon.Gan commented  · 

    If the action is to return TRUE or FALSE, i will vote for TRUE
    or we can consider the action to return 1 for EXACT MATCH (content and order), 2 for content match, 0 for Not Match.

    The idea was based on one of my scenario where I really need to know if both collections have the same items (i.e. no order required).

    Thanks,

    KokKoon.Gan shared this idea  · 
  9. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    KokKoon.Gan commented  · 

    I think if we take that as a requirement or objective to achieve, your proposed "math type inline function" or extending of "Calculate a value" could be the solution to it. I think either option should be fine as long as mentioned type of math calculation could be supported. ;)

    KokKoon.Gan shared this idea  · 
  10. 10 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  ·  5 - Nintex Workflow Cloud » Connectors  ·  Flag idea as inappropriate…  ·  Admin →

    Hi KK, thanks for the suggestion. As we’ve recently released Nintex Xtensions, why not build a Connector using the Nintex Xtensions Framework?

    This makes the action much more reusable and easier to configure. Or is your request to do with something else?

    Thanks!

    KokKoon.Gan shared this idea  · 
  11. 15 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  ·  5 - Nintex Workflow Cloud » Connectors  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    KokKoon.Gan commented  · 

    Similar to Creating an Item in Sharepoint Online could be done via the "Call a Web Service" action to call Sharepoint REST endpoint for creating an item, we will need to get the "Access Token" for the "Authorization: Bearer" header for the endpoint call.

    With Sharepoint Online connector, the availability of Connector/Actions helps the hassles on getting the Access Token for the Web Service call, and/or helps the need to know how to call the REST API with complex body content to provide.

    Availability of Microsoft Graph API will help the same, with Microsoft Graph Connector and Actions.

    Optionally, a different version of "call a web service" actions with options of selecting a "Connection" to use in the "call a web service action" will minimize the efforts to have every single endpoint built as a workflow action in Nintex Workflow Cloud.

    KokKoon.Gan supported this idea  · 
  12. 46 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    KokKoon.Gan supported this idea  · 
  13. 35 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  ·  2 - Nintex Forms for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Under Review  ·  Euan Gamble responded

    Thanks for your suggestion Dan.

    We will certainly be considering how cascading lookups are configured when we rebuild the List Lookup control for Universal Forms.

    If you have specific feedback regarding your experience, please provide it in the comments section below.

    Thanks,
    Euan

    KokKoon.Gan supported this idea  · 
  14. 82 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  ·  Euan Gamble responded

    Thanks for your suggestion Raphael.

    This is a complex request as it would require caching (potentially) large amounts of information into the cloud. Once we ship Universal Forms for SharePoint, we will be revisiting our strategy around Live/External Forms.

    Cheers,
    Euan

    KokKoon.Gan supported this idea  · 
  15. 30 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  ·  2 - Nintex Forms for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion Dan. I can definitely see the value in this feature.

    We will consider this for future development when as we are building Universal Forms for SharePoint.

    Cheers,
    Euan

    KokKoon.Gan supported this idea  · 
  16. 33 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    KokKoon.Gan supported this idea  · 
    An error occurred while saving the comment
    KokKoon.Gan commented  · 

    support the comment where nintex mobile is not meant to support sharepoint on mobile, viewing list or/and list items on mobile could be heavy. But i would support the concept to selectively publish a list (i.e. default view with filtered or limited items) to mobile, list(s) that are published will be available to view from Nintex Mobile app.

  17. 301 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Open for voting  ·  Euan Gamble responded

    Hi all,

    Thank you for your interest in this idea. We have no plans to support the Event content type at this time. If our position changes, I will update this idea.

    Cheers, Euan

    KokKoon.Gan supported this idea  · 
  18. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    KokKoon.Gan supported this idea  · 
  19. 762 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    KokKoon.Gan supported this idea  · 
  20. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hi Ken,

    Thanks for the feedback. I am interested in understanding this requirement a little more. Can you give me some specific scenarios where the current approach is clunky

    KokKoon.Gan supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base