How To Populate Extended Attributes For ProductImpl Level With PIN_FLD_AAC_ACCESS
(Doc ID 2729606.1)
Last updated on NOVEMBER 22, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
To identify different AAC_ACCESS purchased with multiple services in the same PCM_OP_CUST_MODIFY_CUSTOMER opcode execution, a business requirement is to get the AAC_ACCESS from the service instead of the account using extensionContext.getProduct().getExtendedAttribute("AAC_ACCESS").
How to populate "extended attributes=null" with the value of PIN_FLD_AAC_ACCESS in the payloadconfig during the "/event/notification/service/pre_create" event?
Here is a snippet of a ProductImpl in the Customer cache:
3. Restart the enviroment
4. Create an account (The account creation process should fail.)
5. Rollback the step 1 and create the account (The account creation pass ok.)
6. Repeat step 1 and 2 and purchase a plan (The purchase plan process should fail.)
7. Rollback step 1 and purchase a plan (The purchase plan pass ok.)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document