Hi Vance,
Thanks for your response. "makes a resource specification available to a catalog" that is what is little confusing me as resource catalog document (Attached) specifies relationship between resourcespecification and resourcecandidate is one to one. I am trying to understand what is the value this additional candidate object will add from use case standpoint.
Trying to relate your response with real use case. Lets say there areTwo Resource Catalogs
1) South Zone
- Network Equipments (Category)
- Devices (Category)
2) East Zone
- Network Equipments (Category)
- Devices (Category)
There are specifications available as follows
1) Netgear Router XT100
2) TP-Link Switch TI-SG1016
Can we say that we will have two candidates w.r.t each of the specifications above.
1) Netgear Router XT100 - Candidate X
2) TP-Link Switch TI-SG1016 - Candidate Y
And both X, Y will be available to catalog?
1) If this is the case why cant specification directly link to category? What business value is added by candidates X, Y?
2) If above example is not correct is there other use case fits in?
Thanks a ton in advance.
------------------------------
Ajinkya Vaze
Alepo USA
------------------------------
Original Message:
Sent: Aug 06, 2020 02:33
From: Vance Shipley
Subject: Resource Candidate
I find it easiest to reason about (Resource, Service) Candidate by looking at Product Catalog. They all follow the same pattern however in Product Catalog where you would find Candidate you have Product Offering. Product Specifications are used in design time to create Product Offerings with Product Offering Prices which may go into a Catalog and be made available in production to use in instantiating Product Inventory (subscriptions). Similarly a Resource Candidate "makes a resource specification available to a catalog". So Resource Candidates are created in design time and during production use only Resources made available by a Candidate should be used, through their Resource Specification, to instantiate Resource Inventory.
------------------------------
Vance Shipley
SigScale
Original Message:
Sent: Aug 05, 2020 07:02
From: Ajinkya Vaze
Subject: Resource Candidate
Hi All,
We are currently working for creating Resource Catalog Management piece under Resource Domain. We are referring to TMF634_Resource_Catalog_Management_API_User_Guide_v4.0.1. (Attached)
Can someone help me to explain what is the significance of resource candidate in this?
Document describes "ResourceCandidate is an entity that makes a resource specification available to a catalog. A ResourceCandidate and its associated resource specification may be published - made visible - in any number of resource catalogs, or in none."
But above statement is not clarifying the actual use case view of implementing resource candidate.
I have following concerns
1) How candidate fits from application (Front End standpoint)?
2) As mentioned in document, Specification and Candidate are one to one mapped then why this separate entity is required? Why directly specification can relate to category?
Thanks a ton in advance. Quick help really appreciated.
------------------------------
Ajinkya Vaze
Alepo USA
------------------------------