Custom Attribute in SmartUI

Tobias Müller

Hello,

for previous versions of Content Server (classic UI), we have implemented a custom attribute. The functionality is similar to a "Table Key Lookup" attribute. We added a button next to the attribute value field in the category tab. Once a user presses these button a additional windows opens up and the user has the possibility to select a attribute value (retrieved by an webservice call from an external system). Once the value is selected the window is closed and the attribute value is taken over .

This logic needs to be upgraded to CS 16.2 and this customisation has to be available in the smartUI.

Has anyone had a similar customisation, is there an example available? What needs to be done in the smartUI sdk to display the button next to an attribute and to call a specific URL.

Thanks for your help in advance.

Tobias

Ferdinand Prantl

I am afraid, that there is no example about implementing a custom field. You can inspect sources of existing fields in CS UI SDK. There is no difference between a custom and a built-in field - just the explanation is missing...

REST API

Fields are registered for unique field types. For example, "otcs_node_picker". You can follow the convention "{module prefix}_{anything}". This type has to be returned by the server in the form schema, which describes the category form. You can inspect existing CSNODE FormCallbacks in Oclipse to find out, how to format schema for you custom attribute in the REST API response of "GET .../api/v1/forms/nodes/categories/update?id={node id}&category_id={category id}".

UI

Alpaca Field Wrapper - registers for the field type, creates a field view and places is into the Alpaca container.
Field View - inherits from FormFieldView, implements both read and write states of the field.

I recommend you looking at a simple field at first, CsuiTextField/TextFieldView, for example, and then at CsuiTKLField/TKLFieldView.