Skip to main content
Nintex Community Menu Bar

Hi,

 

I have my first solution that I have succesfully deployed to live, basically a new form that starts an approval process when the save button is clicked.

 

However, only myself as workflow author can succesfully submit the form, everyone else either gets a message saying the user does not have rights to to start the workflow or they get no message, but it just 'whirrs' and doesn;t progress (ie hangs).

 

I have set the workflow rights via the manament tool and everyone has the correct rights, but I have set this on our test server and have deployed the package from test to live.

 

Am I also supposed to add these rights to the workflow on the live server (if so this could be the problem), or should the packaged solution include the workflow rights I have applied on the test server?

 

Any thoughts, bit pointless if only I can use it lol

Hi  @JulieBird 

 

Will you please see the following links. I hope one will help you with the workaround.

 

Best,

Sunrise

 

Hello  @JulieBird ,

 

Hope you are well please run and install the product fixes listed below:

 

Code Fix: An intermittent error occurs when starting a K2 Workflow from a form

https://help.k2.com/kb003081

 

Code Fix: In the HTML5 designer, the sub workflow does not start when using a call sub workflow event on different SharePoint sites

https://help.k2.com/kb003084

 

Hotfix: Unable to configure start conditions in a K2 Workflow after re-adding the K2 App

https://help.k2.com/kb003069

 

Code Fix: Workflows do not start on configured schedule

https://help.k2.com/kb002907

 

Hotfix: When attempting to start a K2 Workflow using the REST API, an error occurs

https://help.k2.com/kb003010

 

Code Fix: A legacy K2 Workflow does not start when triggered with a SharePoint event

https://help.k2.com/kb002884

 

Code Fix: When editing a workflow that is set to start “When item is added”, an error occurs

https://help.k2.com/kb002782

 

All the best

 

Thanks to both for the replies,

 

This turned out to be simpler than having to run server fixes thankfully :-)  ... it turns out I needed to open the workflow in the K2 management tool on the 'Live server' and set the permissions there, rather than just on the test server k2 management tool where I had assumed the package and deploy would pick it up and deploy it to live.

 

Having only used the test server to date I didn't know there was an equivalent designer/management tool on the Live server aswell.

 

Doah! 

 

Thanks again for suggestions, much appreciated :-)

 

 

Reply


Sidebar Buttons
Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
Terms & ConditionsCookie Settings