Contract Attachments

[tinne]

Contracts shall have attachments.

Attachments are an ordered list of contract specific binary attachments, each with a name, unique by the Contract object.

This changes the current idea of one attachment only, as in the past contracts had to be amended, changing their date range or amount, and this changes are documented in separate files, where the historical order must be kept.

On dealing with existing data: An existing contract with a single file shall be migrated to have this one file as its only attachment. An existing contract without a file shall have no attachments.

It shall be possible to add attachments, reorder attachments, and remove attachments without any restriction. Attachment names shall default to the file name given, if accessible to the front end. Is should be possible to rename attachment names.

Destructive replacement shall not be provided for. Uploading a file with an existing name shall result in a copy with a different name, e.g. by attaching “ (i)” for the smallest positive index value i available.

If there are no attachments, obviously, none can be deleted. Any deletion must be accompanied by a confirmatory question.

Order is relative only, and no editable index numbers shall be used, maybe some sort of drag and drop plus move up/move down controls.

Provision shall be taken not to create unreachable attachments by attaching files to a draft contract and withdrawing the draft before save.

The visible appearance after successful upload must be identical to the appearance when re-editing a contract with an existing attachment.