Hitachi Content Platform​

We have the following scenario involving HCP 8.1 & we want to manage the following customer lifecycle using the MAPI (ideally nothing done manually):

1. A prospective client's data needs to be held for 5 years then must be deleted

2. A prospect that becomes a client - data held indefinitely

3. A client that leaves becomes an ex-client - data held for a further 5 years then deleted

We intend to use the following solution:

1. HCP data initially ingested with 5 year offset

2. Client data has the hold setting enabled to avoid disposal

3. Each ex-client object has to have the retention date extended manually via a REST call to extend to 5 years

We wanted to use Retention Classes but we believe this wouldn't be helpful in the above scenario - is that correct?

We also believe that the MAPI cannot be used to change Retention Class properties - these have to be changed in the UI - is this correct?