I'm trying to do the "right thing" and use the FeatureJoiner instead of the FeatureMerger where possible, however, there is a pattern which I commonly use which is not supported by the new FeatureJoiner.
In the FeatureMerger I can specify hard-coded values for the joins, so I quite often join on "1" = "1" (the actual values don't matter, as long as they are the same). I do this to validate that one path of my workspace has produced a result, before continuing with the rest of the translation, or if I want to join all attributes from features in one translation path with all features from another path.
The new FeatureJoiner requries me to specify an attribute for my join values so, in order to acheive the above, I would need to use an AttributeCreator to supply a dummy value to each translation path, before using the FeatureJoiner. This is possible but is an extra step that I don't need to do with the FeatureMerger.
Please allow the FeatureJoiner join fields to specify a value, rather than requiring an attribute.
