Modelling CFS vs CFS Service Actions
edited May 11, 2015 10:01AM in Order and Service Management (Communications Industry) (MOSC) 1 commentAnswered
Hi,
We are working through our first 7.2.4 changes and we have come across a strange limitation that I would like to confirm if it is either a bug or an intended feature. It appears that we cannot model a structure within a CFS but we can model a structure within the CFS Service Actions.
The team that has designed the SOM and the CFS has given CFS a complex structure that looks like the following:
- Voiceline_CFS
- Attributes
- AttributeSpecificationGroup
- Attributes
- FeatureSpeficationGroup
- Attributes
- AttributeSpecificationGroup
- CategorySpecificationGroup
- Attributes
- AttributeSpecificationGroup
- FeatureSpeficationGroup
We have noticed that the mapping rules look at the ServiceAction_Voiceline_CFS entity which does allow these structures, but how does this play out in the long run? The CFS model itself does not have these data elements since the ServiceAction extends the CFS. Will this drive duplication over time as more Service Actions are added against this CFS?
0