@krishnamohan Pokala

the Salesforce extender doesn’t carry over Pega’s UI skin or colors, it only brings data, so you need to compute and render SLA colors in Salesforce (LWC/Aura) based on fields returned from the worklist API like pxUrgencyWork, goal/deadline times, and status; if your current D_pyMyWorkList response lacks what you need, expose those properties via a wrapper data page or switch to D_Worklist which the DX API documents for work queues/worklists. Use DX API v2 rather than v1; v2 is the current, model-driven API for Constellation and includes /data endpoints for worklists and assignments (for example GET /data/D_Worklist), which you can call from Salesforce and then map to row CSS classes for green/on-track, amber/at-risk, red/late, gray/resolved. In short: 1) adopt DX API v2, 2) include urgency/SLA fields in the payload, 3) map SLA status to colors client-side in Salesforce, 4) don’t expect Pega’s skin to render in Salesforce, 5) test pagination/filters in DX API for large lists, 6) secure with OAuth scopes/CORS. References: DX API v2 overview and worklist endpoints, and Process Extender for Salesforce Lightning docs.