Can we migrate custom workflows and Groovy and server scripts using the Redwood migration accelerator?

Regarding scripts and triggers, should we continue using Groovy scripts in Application Composer or do we need to have them on Visual Builder (VB)? Can we change the code/HTML CSS of each page?

Groovy field triggers do run in Redwood, but they run when data is posted to the server.

Back-end server scripts (Groovy triggers and workflows) run in both the classic and UI context. Redwood uses the same web service back-end as the old CX Sales (SUI/FUSE) pages -- these don't need to be migrated except where you want to have client-side (for example, tab-out-of-field) interactive validations.

Client-side interactive validations are best done using Visual Builder Studio action chains. We don’t recommend converting Groovy to Visual Builder Studio JavaScript. The code translations generally aren't that great.

Note: Client-side validations need to be in VB and all other triggers in Application Composer. The Redwood pages are further customizable, but be sure you're following Oracle’s best practices.