Hi All, There are some use cases that publisher UI need to be customized by adding new UI fields. Those fields can be used in the store for different use cases (eg; App Price). With the support of Enterprise Store, getting this done is very easy. It's just adding new field/s in the RXT and few modifications to .hbs file. We don't have to do anything additionally to POST/UPDATE/GET app info with these new fields trough the jaggery APIs.
Requirement is how are we going to do this with the new REST API model. We use pre-defined DTO classes for request/response generation with the swagger definition. Therefore publisher users could not add new custom fields easily and get them supported through the APIs as previously without modifying the code. One option is, pre-define "customFields" object inside AppDTO class and get the users to define custom fields in the RXT with new tag called "customFields". So that we could populate value inside the DTO class by looking at the fields marked as customFields in the RXT. But this requires capability to define some additional property to RXT field in addition to name/value. @Registry team, any ideas on whether this is possible ? Suggestions/feedback are appreciated. Regards, Dinusha. -- Dinusha Dilrukshi Associate Technical Lead WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
