...
Order Overview
Ot At the date of the order, the order is placed which starts the ordering process. This process is ended by invoking the hookpoint "RATEPLAN.CHANGE.ORDER". After successful completion, the rate plan change enters a pending 'Pending' state.
Based on the given effective date, a start date is calculated. When this date is passed, the corresponding process begins and ends with invoking the hookpoint "RATEPLAN.CHANGE.START". After successful completion, the rate plan change enters into the 'startedStarted' state.
Immediately after the rate plan change has entered the 'startedStarted' state, the execute process begins by invoking the hookpoint "RATEPLAN.CHANGE.PRIOR" followed by applying the core business logic. Subsequently, the hookpoint "RATEPLAN.CHANGE.AFTER" is invoked. Upon successful completion the rate plan change enters the 'completedCompleted' state.
Please note that two different workflows are invoked in the 'startedStarted' state. The reason is to allow the customer to implement required logic in either workflow based on what is considered the most appropriate. We should discuss if both the "START" and the "PRIOR" workflows are needed.
Order Process
Configuration matrix must be defined:
...