sales force extender : display color coding in worklist at salesforce

General
, , , , ,
1

  1. We are using Salesforce extender to view user worklist in Salesforce. But we are not able to view the color (eg : workstatus : resolved, New) at salesforce where as in Pega color coding is displayed in myworklist. Actual requirement is to display SLA color coding at salesforce.

  2. For displaying worklist we are using v1 api as could not find related v2 api. Let me know if there is any v2 api for this

https://hpytmgmh.pegace.net/prweb/api/v1/data/D_pyMyWorkList

2

@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.

3

@krishnamohan Pokala :

  1. The changes need to be done in Salesforce extender JS, CSS and HTML files to display color coding changes in extender. As this can be a common requirement for all clients, we are reaching out to Pega to check if they include these changes as part of next release in FY 2026.

2 options listed as below:

  • We can customize the code, but will add to maintainence overhead as we need to retrofit our code for every Pega SF extender release.

  • Create a new component with the changes and use it.

  1. Though we point to v2 url in SF extender, in the backend it will call the v1 url and displays the assignment list