Skip to main content
Nintex Community Menu Bar
Solved

Disable user access during upgrade

  • July 6, 2017
  • 2 replies
  • 5 views
  • Translate

Forum|alt.badge.img+10

We are planning to upgrade to 4.7. During the upgrade we don't want users to create new instances or take actions on open instances. Is there a way, we can disable user access to K2 workflow, forms etc.?

Thanks

Best answer by tin

Start Rights can be removed from the workflows in question.  When doing so, workflow will not be started  and users may be presented with an error indicating they do not have Start rights on workflow when they try to submit a form that would start a workflow:


 


https://help.k2.com/onlinehelp/k2blackpearl/UserGuide/4.7/default.htm#K2_Management_Site/Workflow_Server/WorkflowsTab.htm#ManageRights


 


 

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img+18
  • 555 replies
  • Answer
  • July 6, 2017

Start Rights can be removed from the workflows in question.  When doing so, workflow will not be started  and users may be presented with an error indicating they do not have Start rights on workflow when they try to submit a form that would start a workflow:


 


https://help.k2.com/onlinehelp/k2blackpearl/UserGuide/4.7/default.htm#K2_Management_Site/Workflow_Server/WorkflowsTab.htm#ManageRights


 


 

Translate

Forum|alt.badge.img+10
  • Author
  • 100 replies
  • August 17, 2017

Tin,

Disabling Start is a good option for new requests.

 

For our upgrade, we had extended downtime as we ran into errors. There were running instances, they started failing because we have escalations defined on them. Also, some users had email approval notifications they tried to approve requests.

 

I guess lesson learned is, do not leave any running instances before upgrade.. may be stop running instances before starting upgrade have users complete them.

 

Thanks

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings