Open APIs

Dears,

we are working on a project to standardise a CRM Siebel API with the tMF621 Trouble Ticket Management.

we are facing many customized attributes that are not specified on the standard of TMF621.

my question what should I do for those customized attributes :

scenario 1 : use the characteristic object and manage all the customized attributes there around 60 attributes).

scenario 2 : use the @schemaLocation techniques and specify a json where we will add all the specific attributes ?

Thanks.

Skander

Hi Skander

We tend to use both mechanisms plus a (3) ObjectCharacteristics.  If the fields apply to all trouble tickets we tend to make concrete extensions to the API using the polymorphism pattern (@schemaLocation, etc).  However, if they are merely fields relating to a group/handful of trouble tickets, we tend to use characteristics instead.  Either method has its pros and cons.

Good luck!