Customizing standard Omnistudio components versus custom builds
Key Takeaway
Use the least code that meets the need. To change a standard Omniscript, create a new version of it and of the Flexcard that launches it, then point that Flexcard to the new Omniscript instead of building from scratch.
Agentforce Health ships standard Omnistudio components, such as the Omniscripts and Flexcards that run utilization management authorizations. When a customer's process doesn't fit them, you can configure them in the designers, customize or extend them, or build new custom components. Salesforce recommends the option with the least code that meets the need, because minimal-code apps run faster and are easier for admins to maintain.
Choose the option with the least code
Omnistudio is low-code. Salesforce recommends working through these choices in order:
- Use standard components. Define as much as you can in the Omniscript and Flexcard designers.
- Extend or customize a standard component, but only when it lacks a function you need.
- Build a new component, but only when you can't use or customize a standard one.
A new build should still use a hybrid design, so the app stays easy to maintain and upgrade. When you build something new, follow these habits:
- Write custom code in a generic way.
- Build new Lightning web components (LWCs) with global, reusable logic that serves many use cases.
- Use consistent naming conventions for all Omnistudio components.