Pre customization hook points for Product Delivery life cycle

Pre Customization hook points are required for Product Delivery life cycle status.

Already delivered Product delivery hook points are only for Post activity, eg:postProductDeliverySubmittedForApproval, postProductDeliveryApproved, postProductDeliveryActivation etc.,

Each Product delivery status is combination of both pre and post delivery actions, so postProductDelivery actions alone won't sufficient to get rid off the non complaint customisation.

Here are answers for previously asked questions from previous request.

1.What non-compliant customizations do you currently have in place in this area (i.e. to work around the fact that the pre customization hook points required for Product Delivery life cycle status do not currently exist in the OOTB product).

Ans: We have several activities like

Validate the client is not deceased,

Ensure an active bank account before activating PDC,

Prevent activation of PDC when the bank verification is outstanding and so on

2.What states are currently served by these non-compliant customizations (some are mentioned within the request which include when a case is activated, closed, submitted for approval, approved, reopened etc.). Is this the definitive list ?

Ans: List are:

Activate

reactivate

submit

approve

close

3.What are the business problems currently being solved by these non-compliant custimizations i.e. what is the customer trying to do that is not provided for by the OOTB product in this area?

Ans: Validations, Triggering task and other activities are being carried out prior to Product delivery life cycle events.

All these activities are implemented in a non complaint way in the current code, If we get Pre customization hook points all the code can be moved to respective handler class and get rid off the non complaint customization.