Native components implementation in business systems are a real problem when you try to compose with standard accounting management systems and Customer Relationship Management systems. Native datas resolution involve a user-friendly manipulation and this is why their "native", to avoid corruption of executable system commands or databases corruptions. Otherwise, as others suggest you, you could use a parallel system to manage lifecycle contracts, but be sure that linking that kind of different systems based API would require an expensive team of programmors, and even if this case, it is almost impossible to manage these sync system because of the non regularity of datas and codes writing over present computer sciences. But, in the case you still want to create a particular system for management of lifecycle contract, I can recommand you to create an entire parallel system for this type of costumers, involving that you will also requiring all accounting and CRM needing. You will soon understand that is costless to manage an other system of business datas than requiring to programmors skills (I don't think that lifecycle contracts are part of usual contracting way).
↧