How do you use the Services feature?

[Rune Rasmussen]

Hello

I really like the idea of the Services feature but find it severely limited with seemingly arbitrary restrictions.

But surely there must be some sense to it and use of it, so I'm wondering how other people/companies are using the Services feature.

How do you deal with not being able to create new attributes?
How do you deal with not being able to use other Schemas?
We would have to create a secondary Schema for all of our other data/information needs resulting in two Schemas to maintain.

Are there any other weirdness or restrictions that you or your company have had to work around?

[Marc -Devoteam-]

HI @Rune Rasmussen 

Don't use the services feature, instead create your own Assets schema, then setup custom fields of type assets to use the information from the schema.

The default locked schema has in my opinion no value, only if you simply keep this options as simple as is. On going more advanced and requiring more details you need to use your schema or add a schema and create attribute of type object.

Then you can reference information from the default services schema, but in my opinion this is just more effort.

Jus you can't use the default Services feature.

[Simon Pearce]

I'm having the same problem. Intuition and experience tells me that I want to build a relationship of Capabilities --> Business Services --> [Applications/Software Services] wholly within the Services schema in Assets.

I don't wish to present this data to "customers". I do want to present the data to Spaces - perhaps I will create workflows around software lifecycles.

The Services schema object-types contain attributes that allow Capabilities, Business Services, Applications, and Software Services to be linked to each other, but those attributes are not shown in the UI and can't be edited.

As you say, this entire schema looks like a dead-end.