Process flows often requires you to create process flow variables. Currently you can select any process flow variable for the output/input parameter options of a process flow step. There are validations to check if a variable matches the required output format. I propose to limit the available process flow parameters to the allowed data types.
For example: you never want to set a bit data type to a file name field. So when choosing the process variable for file name I only want to see text related data types.
Page 1 / 1
Hi Erwin,
Whilst limiting seems like a good choice, the issue arises if the datatype of the process variable is changed after it was assigned. Or even if the domain itself was altered. If we would limit the options, you would not be able to see the assigned variable due to it being filtered out.
We technically could limit the option ánd append the currently assigned process variable to mitigate this. But, I do see Realtime validations as a better alternative solution: Replace validations where possible with just in time checks | Thinkwise Community
I feel like it’s more user friendly to NOT give the possibility to select wrong options. Personally i feel like this is the better solution: “We technically could limit the option ánd append the currently assigned process variable to mitigate this.”. You could add some conditional layout to showcase if there is a parameter chosen that is no longer valid.
Regarding datatype of the process variable(or the domain) is changed after it was assigned. For this the validations could still be used.
New→Open
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.