I got the following situation and I would like to know if there is any possibility workaround.
We are invoking OWD from Siebel. One of the input data is a boolean attribute. This boolean attribute has the values 'Y' and blank on Siebel (for representing false...).
On OPA, the user should have the ability to modify this attribute and send it back to Siebel.
Now, I can easily map the blank value to false with the user properties on the Integration Object so the attribute don't get the uncertain value, but we don't want to store back in Siebel a "no" or "false" but a blank. In the same way, if the attribute is true and the user change it to false, how can I send back to Siebel a blank value on the boolean attribute if it's an input/output attribute?
I was thinking in trying using the uncertain value on the screen and change the label of it to False (so the user thinks he is inputting false, whereas it is actually an uncertain or unknown)
Do we have something better than this?
I might have misunderstood something as I didn't perform a test on this, so let me know if my assumptions are wrong.
On a side, we had the same issue with some numerical attributes, and we did solve it by using an intermediate attribute, using this intermediate on the calculations, taking 0 when is blank and leaving the user the ability to update the original value so it can be stored back with the new value (allowing the blank value,).
Other than the suggestions in your post, you could implement a "Policy Automation Save Session IO Pre" workflow to modify the values from false back to nothing before the Integration Object is saved/updated.