In version 22.01 we introduced a new data palette in the Oracle Visual Builder design editor. The data palette shows services and business objects that are part of your application and allows you to drag them onto the visual editor (or the code editor, or the structure pane) to create UI components that maps to them. This is a great way to accelerate creation of forms that interact with data. While in the past, unless you started with a table/list on a page, you needed to manually create the types, variables, UI components and actions and then connect them all together to create single record update/insert pages – this is achievable with a simple drag and drop. You are of course free to change the code that was created as you wish.
If you want to better understand the inner working of these forms that interact with POST/PUT/PATCH endpoint, you can review a past blog post that covered the manual steps for setting it up. As you'll see the new data palette indeed makes development much faster. But in the background, you get the same building blocks created for you. These simplify the way you pass the "body" to these endpoints.
Here is a quick video showing how to create various artifacts based on REST services
Note that while the demo uses REST services, the same approach of course works with business objects in VB (which are at the end of the day just REST services). In addition, note that while the demo uses basic Oracle JET components, you can also use the more advanced Oracle JET Dynamic Components with the same approach – just add those components from the component exchange, and then when you'll drag and drop endpoint's you'll be prompted to choose which type of components to use in the UI layer.
In the demo we are using the OpenAPI/Swagger meta-data approach of defining the endpoint to access a REST backends – this is another cool capability that can save you time when working with REST services. Many rest services today expose this type of meta-data (for example Oracle ORDS does) and Visual Builder knows how to leverage it.
On a side note, I'll mention that the data in the specific backend used here is shared among many users and doesn't seem to be backed by a relational DB – as a result it might have issues such as duplicate ids – so if you are trying to replicate the demo keep that in mind