12 Mar Getting a faster turn-around time for OCC development
Oracle Commerce Cloud developers are often challenged by how they can develop and test widgets locally instead of testing it in the design code of the admin console.
In our recently published Tech Guide, we give a step-by-step walk-through of how to set up DCU and CCPROPXY on a developer environment. The guide will help in making changes to widgets and testing it locally without actually making changes to the OCC environment widgets or pushing changes to OCC server.
In 2017, Oracle came up with this great utility, called the Design Code Utility or DCU. The DCU is meant for developers to download widgets and elements on to a local system and push selected changes to OCC.
In October 2017, Oracle released another update to DCU called CCPROXY, which enables users to test widget changes like JS and CSS locally on the developer machine. This utility, overrides the JS and CSS coming from the OCC site with the local copy of JS and CSS. So any updates that your local codebase has are updated on the JS and CSS copy loading from your store site.
Developers can do this without having to package and upload the widget, element, or other code changes in an extension. The tool downloads all the OOTB/Custom widgets to the local machines, allowing learning and POCs to be done without impacting the actual environment.
It avoids the need to publish test code, keeping the environment clean.
Code download allows building processes around code reviews and code management. Team members can check-in the changes to GIT and a designated owner can then publish the updated widgets to the environment after performing reviews. Building the code process also mitigates the risk of breaking the environment due to an incorrect code publish.
Reach out to as firstname.lastname@example.org for more information on our OCC capabilities.