I hope this won’t be a repetitive issue. It was necessary for me to use .NET nullable types in my workflows but there wasn’t any direct type matching and type selection for nullable ones. Therefor I had to do conversions just to resolve it. You can say it’s a very simple task but for a large quantity of use-cases it would be a redundant job. Please add support for intrinsic nullable types in the type selection (either for variable or argument).
That does it then. I didn’t know every nullable type is an instance of System.Nullable. Thank you @bcorrea