My question is related to one of my earlier questions.
Basically, we need to expose the Contract object in our customer portal. But SF currently does not allow this. The solution I found here and elsewhere was that we could create a custom object by copying over Contract data.
Initially I thought I could create a custom object mimicking all Contract fields, do a one time copy from Contracts and then let our Contract team use the new object going forward. This was because our contracts have a lot of attachments and attachments cannot be shared between two records. So we would have the storage overhead of two sets of attachments.
But Contracts have built in functionality like "Activate" and possibly more that I am not aware of. Therefore can anybody tell me what functionality I would lose if we switch to the custom object?
It is very unfortunate that we need to perform these workarounds just to display records from a standard object in our customer portal.
There are currently sales force cases open for exposing contracts on the portal and enabling attachments to have more than 1 parent record.