5 - Nintex Workflow Cloud

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Create Object Variables in designer and from the Form

    It would be good if that would be possible. Especially in relation to to Xtensions. You could group a set variables to an object in WF designer or form designer. Also, you could create arrays of complex types then.

    If an API requires an array of objects or other arrays as property its not possible to integrate it through a Xtension.

    For us thats a annoying limitation, cause trivial request are not possible by custom connectors.

    If the API requires OAuth2, you also can not use call a webservice.

    I had multiple cases where I would have needed that.

    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  ·  Xtensions  ·  Flag idea as inappropriate…  ·  Admin →
  2. import workflows with missing custom actions

    ref:00D90q6Cb.5002v2sALNR:ref

    If a workflow contains a custom action from another environment, and then the workflow is imported into another environment, without that custom action. The import will fail.

    Please implement a mechanism to cope with missing actions, so that the workflow can be imported in and give the end user the option to remove the incompatible action.

    10 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  ·  1 comment  ·  Xtensions  ·  Flag idea as inappropriate…  ·  Admin →
  3. Google Sheets API - Collection Inside a collection

    I was working with Google Sheets API and found that I am not to get some actions to work such as append values.

    After further investigation, it appears that I need the format to be a collection inside a collection.

    [[A,B,C],[D,E,F]]

    I tested different ways but ultimately could not get that format.

    21 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  ·  Xtensions  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support non-OK status-code in xtensions

    Currently if a xtension responds with a code other than 2xx the call is considered to be a failure.

    However many APIs legitimately return a status-code other than 2xx. For example if you query a service and no results are found, many APIs return 404 - "Not Found". This is a valid response and I would like to react on this response within the workflow. Many times this would result in either creating a new record (if a query returns 404) or updating an existing record (if a query returns 200).

    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  ·  Xtensions  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

5 - Nintex Workflow Cloud

Categories

Feedback and Knowledge Base