...
From Product and RatePlan | The combination of Product and RatePlan currently assigned. |
To Product and RatePlan | The allowed Product and RatePlan which may be used as target for a rate plan change. |
Effective date | The logic for calculating the date of making the rate plan change effective. Different rules may be applied: 'Tomorrow', 'EndOfMonth', ... |
Start date | A number of hours relative to the effective date, which describe when the rate plan change process starts. When this has passed, the rate plan change cannot be stopped (i.e. point of no return). |
Allowed channel(s) | Indication of which channels (customer careCustomerCare, self careSelfcare, ...) allow ordering of this rate plan change. Still to be defined how this is to be represented. |
Key | A string that will be the dynamic key for hookpoint keys, but may also be used for identifying price elements. |
...
- Given a configuration matrix element, subscription and effective date, validate if the rate plan change is allowed according to the configuration matrix element.
- Given a configuration matrix element, subscription, effective date, silent indication, fee apply indication and list of chosen options, persist the requested rate plan change and invoke the hookpoint "RATEPLAN.CHANGE.ORDER" + key from the configuration matrix element. The silent indication will be transferred to the various workflows to allow external communication to be excluded. The fee apply indication will be transferred to the various workflows to indicate if fees should be added or not.
...
- .
Implementation Information
...