Other Considerations for Visual Builder Studio

Important considerations for using VBS for HR Help Desk include:

1. IMPORTANT NOTE FOR ALL: You can't deploy changes from a Visual Builder instance into an environment that's on a different version. For instance, when your TEST environment is updated with the latest version of the product, you can't deploy your Visual Builder changes to the Production environment until Production is updated.
2. Oracle recommends doing a P2T on your environment before starting to implement.
3. You'll need Visual Builder to make any changes to your UI – including showing custom fields or attributes to your employees or agents.
4. Visual Builder will only recognize fields or attributes that are on the environment to which it's connected. For this reason, you've a few options:
   1. Do the development on the TEST environment (or whatever environment Visual Builder is associated with as confirmed in the section above).
   2. Re associate Visual Builder Studio to be associated with the environment on which you wish to do the development (not recommended unless you ALWAYS start development in the same alternate environment).
   3. Add new custom fields/attributes on both the environment to which your Visual Builder Studio is associated AND on the environment upon which the development will first be done so that VBS development can continue.