New features
Tables – integrated data storage to streamline workflow automation: Introducing the Beta release of Nintex Automation Cloud Tables, providing a centralized, scalable way to store, manage, and connect process-related data across business-critical applications. This new Nintex data storage capability reduces application complexity, improves reliability, and accelerates time to market for application developers building end-user workflow applications on the Nintex platform. For more information, see this blog post, video and the Tables help topic.
Start form permissions: After publishing a workflow, designers can control access to start forms based on the user or user groups defined in Nintex Automation Cloud. This way, only authorized users will have access to the start form, which will be visible in their My Nintex and Mobile App. For more information, see the Form access help topic.
Choice – Multiple form control
Participants can now add a custom option to their response.
Designers can now enable the option to add range validation. This will enable them to control the number of options a user can select.
Designers now have the option to filter out duplicate options.
For more information, see the Choice – Multiple help topic.
Let’s discuss some of these new features real quick - which I should say are a game changer!
Start form permissions:
- Need ability to use groups in Azure Active Directory for tenants that use SSO AD.
- Confirmed via community that this feature is in the cards but no release date yet. Permissions for Start Forms | Community (nintex.com)
- Need ability to allow business owners to assign form permissions just the same, not just workflow owners. Typically, the “business” or the “customer” is the one that would own this activity - not a designer, developer or global admin.
- The “business owner” ability/functionality was expressed already to Nintex if it was to be rolled out on the following idea. Security trim a form so only users who have permissions | Nintex Ideas
Multiple choice form control:
- The range validation and new “filter out duplicate options” feature are not available to single choice field. These two actions almost go hand in hand. Whatever feature(s) is made available to one, should also be applied to the other and vice versa, when possible.
- I created an idea back in March however single choice was not mentioned on my part - my bad. NAC Start Event Form - Cascading Dropdowns (Data | Nintex Ideas. If we can have both single and multiple, we are one step closer to doing a lot of our forms in NAC vs Nintex Forms for Office 365.
Is any of the missing functionality, listed above, on the roadmap to be implemented?
