Open APIs

Hi,

we have multiple mobile plans as product offers. Each has its own conditions to be checked when customer chooses. Some of the conditions are:

Is age over 18?

Is msisdn status active?

Is there any package change within last 30 days?

Is there any commutment like 12 months or 24 months? so on.

TMF679 can provide limited conditions checks based on offer characteristics, product inventory and segments. So, I think we have 3 options.

1. Should we add the mentioned checks to TMF679?
2. Should product catalog includes check information? Then tmf679 checks the conditions? 3. Should we have dedicated check apis that can be called from TMF679? 

1. TMF679 has no limitation on qualification rules. The productofferingQualificationItem in the API has a 1 to many relationship. It's not specific to segment or product inventory...

2. with the V5, TMF620 gets a new resource called "policy" for complex business rules.
you should be able to declare or reference all your qualifications rules. For instance, declare product relationships or reference a external policy Id, which is then authored and executed by a BRMS.

3. that's up to you. but it makes sense. We have embedded service qualification into product qualification.

Hi,

we have multiple mobile plans as product offers. Each has its own conditions to be checked when customer chooses. Some of the conditions are:

Is age over 18?

Is msisdn status active?

Is there any package change within last 30 days?

Is there any commutment like 12 months or 24 months? so on.

TMF679 can provide limited conditions checks based on offer characteristics, product inventory and segments. So, I think we have 3 options.

1. Should we add the mentioned checks to TMF679?
2. Should product catalog includes check information? Then tmf679 checks the conditions? 3. Should we have dedicated check apis that can be called from TMF679?