In this article in the Web Components Techniques series I’m going to look at a fairly specialised topic, that of creating components that can call into VBCS Service Endpoints (REST Services managed by Oracle Visual Builder Cloud Service).
Now as a matter of course we try and build components which are totally agnostic of where they will be used, I should be able to use that component both within JET or any JET based UI, including VBCS of course. As such we might define our component API with properties which work with generic data-types such as Array or the JET DataProvider interface. However, there are cases where this is really not sufficient. For example, you are building a complex CRUD (CReate Update Delete) screen as a re-usable component. This will need to keep communicating with the appropriate REST endpoints within the context of the component, rather than just manipulating a set of data and allowing the hosting application to take care of the REST part (Note: this is just apattern, not the pattern there are various ways for components to behave in these scenarios, there is no one-size fits all approach). Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.