Is it possible to link default classifications to entities being created ? Say there is dedicated Spaces for different business domains of our company, and upon creating business capabilities via a particular business domain space, the right classification is automatically applied.
Looks like if the Business Space configuration doesn't allow to define default classifications, the configurable modifier doesn't seem to be an option either as it needs a trigger.
any ideas ?
Pinned topic Default classifications in Business Space
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-18T10:15:21Z at 2012-12-18T10:15:21Z by DavidSeager
DavidSeager 110000C5XS64 Posts
Re: Default classifications in Business Space2012-12-17T13:20:19ZThis is the accepted answer. This is the accepted answer.There is no way to do what you describe. The Business Space widgets do not have any settings to add anything to an object when creating it. The WSRR API does not know which business space the user was in when they created an object. The WSRR plugins cannot find out which role a user is in when they created an object.
Currently the best you can do is enable editing a classification on the object being created (by adding a classification taxonomy to the properties), and for each space, restrict the classification that can be added to the desired single class. This means the user still needs to add the classification themselves.
This would make a good requirement for the product. Requirements can be raised here:
NickLaqua 060000RSNW17 Posts
Re: Default classifications in Business Space2012-12-18T01:05:58ZThis is the accepted answer. This is the accepted answer.Yes, I guessed so much that Business Space and WSRR are to be kept loosely coupled.
I am struggling though with the work around you suggested. When adding a taxonomy to the properties tab of an entity, it will allow only to add a single item per "taxonomy" tree (regardless of level). So if adding a parent node, the children will be available to be added by the user. But if selecting a single child node (e.g. my particular business domain), this child node will become the property itself without any classifications to be shown on the right hand side.
Hope this is clear.
DavidSeager 110000C5XS64 Posts
Re: Default classifications in Business Space2012-12-18T10:15:21ZThis is the accepted answer. This is the accepted answer.
- NickLaqua 060000RSNW
So with the current code, it seems the Taxonomy chosen in the details configuration should be the class above the classes you want the user to choose. If you choose a class with no sub-classes as I suggested then you get no choice of what to add.
So the only approach is therefore to structure the ontology with a single child class of your business domains unfortunately. For example:
- HR Domain
- Finance Domain
Then you can choose the "HR Domain" class in the detail properties edit, and the user will only be given "HR" to add.
This is not ideal in my opinion and ideally we would have a requirement for doing this better.