I think, we found a bug or did a fundamental mistake:
We created a very simple workflow that should just create an item in another list by starting the workflow on a list item.
The workflow action is wrapped inside an action set that should run as workflow owner.
This works fine as long as the form type in the workflow settings is set to Default.
If I try to change it to custom an remove the value in the start page field, the workflow fails with the following error: "The workflow could not update the item, possibly because one or more columns for the item require a different type of information." It doesn't matter, how starts the workflow. The error occurs regardless of whether started by a simple or an admin-user.
The requirement for removing the start page is that the workflow should immediatly start after clicking the action from the ECB instead of clicking "start" on the StartWorkflow.aspx-page.
On my local machine, I've got Nintex Workflow 2013 (188.8.131.52) - International installed.
I screenshoted the major settings in this workflow as following:
Is this a known bug or an expected behaviour? And if, how could this be fixed?
Greetings from Nuremberg
Nachricht geändert durch Ricky Mattischeck: corrected spelling mistake in subject
It seems that you've found a bug on the "start from the item menu" option.
If you try to start the workflow from the workflow page of the item, this should work fine.
I reproduce the case, have tried to find which "Start page" URL could be used to workaround it.. but no success...
I would advise you to Create a case via the option at the side of the topic.
Hmm, since the spaces have been merged, the possibility to watch the opened case for this bug has gone. Before the merge, there was a link on the right side of this thread for me...Can I see this somewhere in my profile?
Ah... A button we didn't think about prior to the merge. I'll see what I can do. Bear with, folks. Meantime, you can click "support" in the menu up top to start a ticket. Thank you!
It seems I have to get help from our platform provider, Jive, to get that button up. I've put in the ticket to have that done. Meantime, please visit the Support space to start a ticket if you need one. My apologies for the inconvenience and thanks for bearing with me as I tweak the site.
Thanks for raising a case with Nintex. After testing this issue I can confirm that it was resolved in version 184.108.40.206 of Nintex Workflow.
If you're in a scenario where you can't get Nintex upgraded to 220.127.116.11, I found a work around for this. You create a second workflow that uses the "Start Workflow" action to start the real workflow. You set this second workflow to show on the item menu with the custom form, and remove the real workflow. So users will start the second workflow, which will then start the real workflow. In this scenario, it won't error out.