Lets say I want to change the name or date on a file on the MOS….
Here’s the process:
Why cant you just:
Click on the file that you need to change.
THREE Steps vs. SIX Steps
I'm getting confused here. Do you mean that when you send an item for approval, even if you set a value for your custom field Expiration date it is not saved? But when an approver goes and edits the already sent for approval document, the Expiration date is missing and must be reentered again?
I see what you mean now. Unfortunately PublicationDate and ExpirationDate are system fields that shouldn't be mapped to a custom field, as their values might change unexpectedly when you edit a content item. The ExpirationDate is set when you are logged in as an Administrator and you edit a Document, on the top toolbar there is a button More actions and under it there is a menu item named Publish/Unpublish on a Specific Date. These fields aren't visible for Authors. It is visible for Editors only if they created this specific Document (they are the owner).
As I mentioned these fields are accessible through the Publish/Unpublish on Specific Date menu command. You shouldn't expose them through custom fields as their values might be changed by Sitefinity at any given moment, even though you have exposed them.