FlexiTask outcome value (Decision) changes

Of course I could. But we want to manage the deployment automatically... we will have more than 30 flexi tasks in about 20 workflows at the end and the way to get the decision values is very annoying.

I can't understand why the outcome value cannot be set on the FlexiTask Decision field manually... and why this value has to change in another farm?

We also want to hide other fields depending on the decision but this will also be very tricky.

I think about a JS solution to dynamically gather and set the value on submit but where I can find the expected without showing the Decision Option buttons?

Thanks fpr any suggestions

Thanks for this hint - as all farms belongs to the same project (test-, integration and productive environment) this solution fits for our needs and the usability for the user is as it should: Only press one button instead of selecting the outcome and press the confirm button...

Hi Martin,

we decided to update Nintex database to get always the same values because our deployment shall be 100% automated using PS.

Here is our script:

USE DBNAME --                        <-- <INSERT DATABASE NAME HERE

SET IDENTITY_INSERT dbo.ConfiguredOutcomes ON
GO

-- Delete existing
DELETE FROM dbo.ConfiguredOutcomes
WHERE Id IN (1,2,4,5)--                <-- Insert new ID's here

-- Insert new
INSERT INTO dbo.ConfiguredOutcomes (Id,Name)
VALUES
(1,'Approve'),
(2,'Reject, cause of'),
(4,'Approved'),
(5,'Reject')
--                                   <-- Insert new Id's here

SET IDENTITY_INSERT dbo.ConfiguredOutcomes OFF
GO

Hi Martin - thanks for your warning.

> but I'd very strongly recommend against writing to the Nintex databases

I'm aware of tis behaviour and we will keep this in mind in future releases of our solution.

> ...You can then read the values in order to set up the Workflow constants...

Where to read the values? If this is from database we could run into the same issue when database schema changes in future...

Hi.I have the same issue, the task outcomes are switched when I deploy in test environment. Is there any other solutions yet. I dont want have the decisions as buttons, because the user had to click decision button and "OK" button to submit the form.

Please advise.

Thanks

Senthilselvi

If you want to know what the outcomes are listed as and their IDs you can use the below script to do so.

select * from ConfiguredOutcomes

Be sure you're connected to the server and the correct nintex workflow database before executing. These can be found in your central administration if you don't know them.

With that note however, we did make a change to this list on our server and while this database shows "Cancelled" as ID 4, when I use decision = 4 as integer it is not using the appropriate outcome. Does anyone know of a way to make the site re-read the list into memory? It seems to be still using our old list. We're trying to make sure this one matches our production envrionment list of outcomes for when sites are created. (I originally dropped the table and then re did the values based on the production server's list of outcomes and IDs since the ID value was auto numbering.) I just did one as ID 5 and it shows "delegated" where the DB table doesn't even have delegated on the list of rows...? 

I can't say this database accurately reflects what's in your decision list, but if you haven't changed the database table, then it SHOULD accurately reflect the decision IDs in your envrionment unlike mine.