Does anyone have history with omitting the attachment path setting so that the full UNC is stored in the database? We find it confusing to the user base when only part of the file name is displayed with the attachment.
The attachment setting for the application server is meant as a default starting point. Leaving this blank is ok. I think the big worry I can see for many users is if end-users have a history of linking files from their own computer (non-embedded), using the attachment default location as a network address will reduce the chances of this happening.
Most APM users that I work with are typically ok with having to manually navigate using the windows explorer defaulting to their own drive.
Note, it's different when talking about the remote service attachment as that is a tool used to reduce synchronization footprint.
When synchronizing with remote if you want some of those attachments or stored procedures offline then you should use the attachment path. Then on the remote it will resolve to a local folder and in enterprise it will resolve to the UNC path.