Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Add a new idea Subscribe
Status Planned
Workspace Nintex Automation Cloud (formerly Nintex Workflow Cloud)
Categories Other
Created by Guest
Created on Dec 9, 2020

RELATED IDEAS

Tenant-wide variables

It would be great to be able to configure tenant-wide variables (maybe as a tab in the settings section of the tenant). This would allow creating variables accessible in all forms/workflows that define legal disclaimers or even image urls, so that when updated in this one location chages would be automatically be reflected in all forms.

(Not sure how feesible this is as unsure if the workflows/forms would need to be republished to reflect the variable change).
  • ADMIN RESPONSE
    Sep 7, 2022
    We are looking at addressing this capability, please reach out if you like to find out more as I'd love to discuss how we are planning on approaching and be great for some feedback.
  • Attach files
  • Gavin Adams
    Reply
    |     Mar 3, 2025

    It would be great to get an update to this please?

    While we now have nintex tables.

    We still really need the tenant wide variables to replace the old workflow constants for Nintex WF for SharePoint on-prem.

    This also equates to the environment variables that are available within solutions as part of Power Automate.

  • Gavin Adams
    Reply
    |     Sep 7, 2022
    very similar to the nintex sharepoint on-premise workflow constants and is really needed.
  • Jordan Maynor
    Reply
    |     Sep 7, 2022
    This seems like something that could be useful for holding temporary authorization tokens that could be shared between workflows/instances. I.E.web services that require getting a bearer token before using further API calls. Could store that token as a tenant-wide variable instead of a workflow-level one and when the token expires you could refresh it only when needed regardless of which workflow the web service is being called from.

    We'd definitely get use out of such a thing. In addition to the probably more common uses of holding reused constants.