Skip to main content

We have created a Nintex Workflow with a few flexitasks in it. In those flexitasks we've chosen to create a custom InfoPath form to let the end user choose from. They have to choose between 'Yes' and 'No' with a value behind it in InfoPath of '1' and '2'.

Flexitask:

InfoPath:

This works well in our quality environment, but when we automatically provision the workflow and the .xsn files behind the workflow, the values of the choises behind are turned around so 'Yes' has value '2' and 'No' has value '1'.

Does this sound familiar to anyone?

task outcome option values differ per content databse - see  

Thank you for that response. Now we know where the problem comes from, but we have another issue. The table 'dbo.ConfiguredOutcomes' has different values in our environments. In development there are 4 records, in quality the table is empty and in production we have 2 values.

Is there a way to synchronise these tables? Can it be done manually or can it evolve in corrupting the database?

I'm not sure, but I would say not.

as far as I know entries there are created dynamically once you create new outcome. but I do not know how does it identify whether an entry for a given outcome exists or not.

I haven't seen it documented anywhere.

if you do not want to depend on outcome numeric value, but rather want to base it on outcome text value you could use an approach nmarples‌ drawn here https://community.nintex.com/message/62687-re-understanding-validation?commentID=62687#comment-62687 

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings