+22It looks like the AttributeManager doesn't offer the ability to Expose attributes that exist on a feature as yet and then do something to them, like rename. This would extend its capability.
Merged Ideas:
Add "exposer" to AttributeManager by bakkermans on May 1, 2016
Is it possible to add the function of the AttributeExposer to the AttributeManager?
+22This is a really good idea and looking likely for FME 2017. If anyone really wants to do this now @1spatialdave and I discovered that you can actually expose attributes in the AttributeManager by typing @Value(hiddenAttribute) in the Attribute Value field. However the field doesn't validate so it looks a bit messy.
There is another way to expose an attribute by the AttributeManager using @CurrentAttribute() function, but I agree that it would be better if "Expose" action could be added to the transformer to simplify this.
'
+3Hello.
This should be useful, but something bothers me with this new functionality.
Supposing I want to delete an attribute before the AttributeManager (upstream), this attribute is automatically exposed in the AttributeManager. So it becomes very difficult to find any problem due to this attribute removing after the AttributeManager (downstream), because the attribute is still there, with nodata values. I wish this automatical use of the attribute exposer could be deactivated by default in the attributemanager.
+11FYI, Yesterday I spoke with Sanae M on the live chat about the comment of @paulblader. I heard that Safe has identified this behaviour as an issue/bug, and has plans to fix this in some future version. I understood that the internal ID for this issue is: FMEDESKTOP-11742
+4@thijsknapen thanks for the info! It looks like transformer version 4 has ability to distinguish between new "exposed" and old "non existing/invalid" attributes. I also find this feature in version 3 very very unfortune. I have a lot of workspaces where source files are getting updated and sometimes converted and the attributes' names are changing from Upper/Camel cases to lower cases... I'd like to be able to "clean" AtrManagers with one click... not review all the "exposed" attributes.
