Visual Builder Studio is the new name for Developer Cloud Service. It continues providing the whole functionalities offered so far with a couple of brand new interesting features: Designer and Environments
The environment section allows you to register your OIC instances that you can then use for the lifecycle of your applications.
First, create an environment giving it a name:
Then, add an instance to the environment:
Finally, select an instance from the list of your existing (OIC) instances:
Note that, once the instance is registered, you can start/stop/restart the instance from here:
Visual Builder Studio Designer
Behind the Designer section you can create Workspaces. The workspace is the connection between the application sources and the Environment instances.
You can create workspaces 4 ways:
- From an existing git repo
- Create a New Visual Application from an existing template
- Create an Application Extension
- Import from a file form a previous visual builder export
New Application Extension | Editing SaaS applications with Visual Builder
Today we are explaining New Visual Application, and will focus on the other options in future posts but, just mention that this new feature will provide the capability to modify existing SaaS pages or create new ones:
New Visual Application
When you create an application this way, you can select the template. The list of application templates will grow in the future and provides a way to reduce development costs.
Note you can work with the git repository behind directly from the IDE menu bar:
Here the option to navigate to other workspaces:
Here the options available from the list of existing workspaces:
A couple of build tasks and a pipeline are created automatically for packaging a deploy.
But, remember to edit the deploy job and put appropriate credentials:
And, finally, as the jobs created are assigned to a Software Template that gets created automatically also, don’t forget to create a Build VM based on that template.
Hope it helps! 🙂