XAM retentions with ALFRESCO and future use by Centera SDK

Hello,

a customer is testing Alfresco application that uses the XAM API for Centera.

Customer has run tests about retention in setting default pool retention and retention trough ALFRESCO. Through XAM, the default pool retention is stored in "retention.base.duration" and the applicative retention is stored in "retention.event.duration".

When the default pool retention is greater that the ALFRESCO retention, the data deleted between the two periods are deleted from ALFRESCO but a XAM error is returned because of "retention.base.duration" not expired.

Is it the normal behaviour ?

Is it an ALFRESCO bug that should take in account the two retentions ? As ShXam (by customer tests) can only delete a Xset if the two retentions have expired, should ALFRESCO follow the same behaviour ?

The customer also tested deletions with JCASScript, and figured out that only the "retention.base.duration" is taken in account ; as the application only sets the other retention, what happens if in the future ALFRESCO switches to the Centera SDK ? Does it mean that no data will have retention (if as usually the default pool retention is left to 0) ?

Thanks for your help