Is there built in version control for attachments (project module)

[christina8]

I have been challenged that the OOB attachment functionality lag behind alternatives for a working documents repository. The inability to replace an attachment with a new file, while maintaining the ability to get to the original version is requested. Additional we have the desire to be able to open an attachment, make changes and by hitting save it auto saves it back to servicenow replacing the existing document, again maintaining the original version for reference. It is a PM group specially making the ask, but I'd be happy to hear if this has been broached anywhere in the application.

Has anyone else done this or come close?

[Brad Tilton]

Attachments themselves don't work like that, but you might be able to use managed documents for that.

Managed Documents - ServiceNow Wiki

[aliciamiller]

I would like to know if the option to save updates to an attachment could be supported.   I don't have the same requirement to manage previous versions but this would be very useful.

[Shane J]

I don't know of anyway to make changes directly to the attachment without downloading it from SN and reattaching it.

[Shane J]

Here is what I have been thinking in regard to the 'versioning' of attachments.   I'm not sure it's a good idea, but it's better than what seems to be available OOB.

1. Create a separate table to hold records for attachments.
2. On that table, have a field that references the parent record.
3. On that table, let you choose a 'type' like Communication Plan, maybe other things like 'Version' or whatever.
4. Attach the file to that specific record.
5. Show the Related List on Project.
6. Repeat adding 'attachment records' as needed, and be able to review them in the Related List.

What do you think?