Improved Address and Price handling about koalixcrm HOT 1 OPEN

It looks like there is the same problem with the prices.
It is recommended to make a short sketch of the planned implementation.
In general the problem is:

• Do we want to have redundant address data in the contact
• Do we want to have redundant price data in the contract and contractpositions
• If they are not redundant how do we make sure nobody is changing the prices and accidentally creates new contract versions.
• Possible solution could be to have complete version history of ProductPrices and Address. This would make it possible to update the price while the contract does still refer to the old price.
• It could be the case that the prices are never deleted but hidden and not visible anymore in the product. They should not be used for new pricerecalculation

from koalixcrm.