Custom Metadata Types vs Custom Settings vs Custom Labels 💬 In plain words: Three lookalikes: Custom Metadata = configuration that DEPLOYS with your code (best for app settings). Custom Settings = org/user-specific values, changeable at runtime (hierarchy type is great for bypass switches). Custom Labels = translatable text for the UI. 📌 Example: API endpoint URLs per environment → Custom Metadata (deploys with code, sandbox vs prod values). A 'Bypass_Automation__c' checkbox an admin flips during data load → hierarchy Custom Setting. The word 'Submit' translated to Hindi → Custom Label. 🎬 Real-Life Example: The Fee Table Trapped Inside Code Skyline charges a different delivery fee per city. Apex needs those rates on every booking. The Old/Bad Way: if (city == 'Delhi') fee = 50. Else if (city == 'Mumbai') fee = 65. … Every rate change is a code change, a test run, and a deployment. Why this is bad: Business data is trappe...
SLDS path is a graphical representation of the process. Here is a component for this. Just pass the status of the process in this component. SLDS Path Component: <apex:component > <apex:attribute name="Status" type="string" required="false" description="Status" default="Submit"/> <article class="slds-card"> <div class="slds-card__body slds-card__body_inner"> <div class="slds-path"> <div class="slds-grid slds-path__track"> <div class="slds-grid slds-path__scroller-container"> <div class="slds-path__scroller" role="application"> ...