Situation
Attachments in deals and tickets
A product stops storing files itself and keeps only bindings. One attachment can serve several entities at once.
How it runs
- 1The product uploads a file through the contract and receives a permanent file_id and a version number
- 2It creates a binding to its entity and passes a link back into the card
- 3Deleting the card removes only its bindings, the remaining holders stay
Features this scenario relies on
Other scenarios
Shall we look at your scenario?
Describe where the files sit today and which entities should hold them. We will propose a binding scheme and the order of adopting the contract.