Loading
Communications Cloud
Índice de materias
Seleccionar filtros

          No hay resultados
          No hay resultados
          Estas son algunas sugerencias de búsqueda

          Compruebe la ortografía de sus palabras clave.
          Utilice términos de búsqueda más generales.
          Seleccione menos filtros para ampliar su búsqueda.

          Buscar en toda la Ayuda de Salesforce
          Best Practices for Customizing Enterprise Sales Management (Managed Package)

          Best Practices for Customizing Enterprise Sales Management (Managed Package)

          Avoid upgrade issues and improve maintainability by customizing your UI components by using slots. With slots, you can make changes to HTML files and reduce the time needed to retrofit customizations during each upgrade.

          Managed Package Icon This feature is part of the Communications Cloud managed package.

          REQUIRED EDITIONS
          Available in: Lightning Experience
          Available in: Enterprise, Developer, and Unlimited Editions

          Push upgrades automatically deliver the latest managed package features, but you need to manually deploy unmanaged content such as Data Mappers, Integration Procedures, Flexcards, and Omniscripts to your Salesforce org. If you’ve extended the Enterprise Sales Management Lightning web components (LWCs), then you have to manually retrofit the LWCs.

          To make sure that Enterprise Sales Management components aren’t changed after the push upgrade, follow these guidelines while extending the LWCs.

          • HTML Files:
            • To modify the HTML files, use slots. This improves maintainability and requires less time to retrofit customization. Any elements added to HTML files are available after a push upgrade.
            • If slots don't cover your use case, submit a Voice of the Customer (VoC) for an out-of-the-box slot.
            • If slots and VoC don’t cover your use case, create a custom LWC and paste the entire content of an out-of-the-box HTML file. Make the necessary changes and update the managed package tags to contain the org’s namespace. For example, change <c-menu> to <vlocity_cmt_menu>.

              This method prevents future updates from breaking customizations but requires manual retrofitting to incorporate new features. Reduce the retrofit time required for each release by automating the diff-checking and merging process for customized HTML files.

          • JavaScript Files:
            • To override any LWCs method in JavaScript file, such as the checkServiceability() method in b2bCartSummary.js, invoke super.checkServiceability() when you want to execute out-of-the-box logic. Then add the custom logic required.
            • To override an LWC method without calling the out-of-the-box method, you can update the method with the latest release logic during the retrofit process.
            • To prevent UI breaks at run-time because of changes to variables, make sure that any LWC variables that are accessed have null, undefined, or other run-time error checks.
          • Styling Files:
           
          Cargando
          Salesforce Help | Article