Open APIs

Team,

What's the most idiomatic way to define an information dependency in the catalog between product specifications.

We have a scenario where we have two specifications require a WAN IP address and ideally I would prefer the primary specification / offer to 'own' the IP address and the secondary specification / offer to 'use' the primary specifications characteristic. The thinking here is that if a change is made to the primary values (housed in the product inventory) via change order, the information dependency would allow the ordering process know that a change must be issued for any linked secondary specifications / offers.

Without this information dependency, it would seem that we would need to duplicate information and somehow update both locations somehow.

Any thoughts on the best approach for this?

------------------------------
Ryan Ruckley
Principal Architect
Singtel Optus Pty Limited
------------------------------

Hi,

You can create relationships between productSpec or productofferings. Each relationship has a type with a discrete list of values (concern, depends on, require...).

you can also read:
 IG1228, it has several examples of product models showing relationships between productSpec from a catalogue and order capture perspectives
GB922 - Product, you have the full course on productSpec relationships.
TMF620 - Product Catalogue API, you can also see relationships between productSpec.
Aiva does a good job, sometimes
I believe we've discussed your question in the past in the API or ODA Engage communities, you can search them (Aiva also pulls responses from Engage website)

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS
------------------------------