Home › Forums › Developers › General developer's discussion ›

Archetype Changes and backward compatibility

Submitted by Ben_Charlton on Fri, 06/06/2014 - 12:52
in

Changing an Archetype and backward compatibility:

I want to change the estimate archetype to enforce expiry dates.  Simply having an estimate being valid from 2 years ago is crazy - prices have well and truly changed...

So I want to ensure when an estimate is created it has an expiry.

I assume I simply change the min cardinality on the endDate node to 1.

What implications does this have for existing estimates that dont have an endDate set.  Am I likely to get archetype errors.

 

‹ Call for aid - more complete set of demo data xml's Nesting Constraints in a query ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Archetype Changes and backward compatibility

Submitted by tanderson on Fri, 06/06/2014 - 13:14.

It will only be a problem if you try and save an existing estimate. E.g. if you invoice an estimate without an expiry date, the invoicing will fail as the estimate is now invalid.

Syndicate content