Override default behaviour

Mark Farrall

Are there any plans to allow overrides on default smart UI behaviours? Say something like the ability to register a mixin or behaviour against a particular component.

My current project is looking to move the behaviour of an appearance that made a number of attributes read only to the smart UI. From what I can see we'd need some way to change the behaviour in the csui-metadata components to achieve this.

Ferdinand Prantl

There have been discussions about making some attributes either read-only or hidden in metadata forms. This could be done as a part of the role-based configuration, which would choose a form field mask to apply to a particular category/scenario. However, such functionality has not been released yet.

If this scenario should run on a custom web page using CS UI Widgets, the goal could be achieved by different techniques, for example:

1. Intercept the CS REST API call by $.ajaxTransport or $.mockjax and make some fields read-only, before the response is passed through.
2. Inject a different implementation of the applied category model module by require.config (pkgs), which would make some fields read-only.
3. Replace the Properties command by a custom one, which would use a custom metadata form collection to make some fields read-only.
4. Implement a new (custom) command showing the form with the read-only attributes.