5 - Nintex Workflow Cloud

← Customer Feedback for Nintex

How can we improve Nintex Workflow Cloud?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • 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.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    Under Review  ·  0 comments  ·  Xtensions  ·  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)
    Close
    Close

  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)
    Close
    Close
    You have left! (?) (thinking…)
    Under Review  ·  1 comment  ·  Xtensions  ·  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)
    Close
    Close

  3. 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).

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Xtensions  ·  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)
    Close
    Close
  • Don't see your idea?

5 - Nintex Workflow Cloud

Categories

Feedback and Knowledge Base

(thinking…)