+1How do other companies using Nintex Forms + workflow handle other users outside of IT who would like to build a form? Or is that something that should be done at all? We are currently receiving requests from multiple users for forms and workflows. We are trying to determine if we should try to set up permissions to allow this, or if we should just handle them all within IT.
Recommend? or no?
Permission setup?
Any insight from someone who does or doesn't do this would be appreciated.
+7Hello Eric,
If your organization is too large, and you people are receiving a huge number of requests for implementation, then I suggest give working sessions/ training to users, slowly they can implement what they want. And any how if they are facing any issues they will reach out to IT. Atleast they can manage easy kind of work and they don't need to wait until IT people do it for them.
And at the end it is your organization people decision and users choice to follow.
I think Design permissions should be required for users to work on Nintex stuff. Here are more details: https://nicoleprestby.wordpress.com/2015/04/06/sharepoint-permissions-nintex-user-experience/
We have governance surrounding this. For Workflow, anyone wishing to use Nintex Workflow, must attend a training course. Once completed they are added to an AD group that gives them access to a limited number of actions. We don't want end users doing things like invoking web services, so it's generally the actions around approvals etc.
For Forms, we made a choice that InfoPath was a better option for end users than Nintex. They shouldn't be developing large, complicated business critical forms so the governance highlights the "shelf-life" of InfoPath and anything they develop. In theory this should drive them to us if they are in any danger of creating something that should be an app supported by IT. Therefore we block Nintex forms for end users. We made this choice because we feel that InfoPath can deliver a more familiar experience for our user base because of the Office UI. We don't pretend to have a workforce flourishing with IT-confident people so familiarity in this case is the better option. It seems to work ok for us as we get limited calls from people stuck creating forms.
+1Thank you! Do you know if it is possible to configure an approval workflow (weather this is SP out of box WF or Nintex) on Forms publishing? That way we could ensure the user doesn't have the form/workflow doing something we don't want it to. Is there a setting available in central admin - Nintex Forms configuration section by chance?
I'm not sure, I don't think OOTB that NIntex Forms has an approval process, Nintex Workflows certainly does.
_layouts/NintexWorkflow/ManageWorkflowModificationProcess.aspx?scope=web
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
