Badge indicator showing whether an opportunity has an associated Service Request
This commit is contained in:
17
README.md
17
README.md
@@ -17,6 +17,23 @@ Browser extension that adds the "Opportunities Extension" shortcut to the permit
|
||||
- `dist/chromium/`: output for Google Chrome and Microsoft Edge.
|
||||
- `dist/firefox/`: output for Firefox.
|
||||
|
||||
## CRM Service Request Badges
|
||||
|
||||
Once per opening of the opportunities modal, `resquestCrmServiceRequest` fetches all pages of
|
||||
`CRMServiceRequest` records with `SVC_PENDING_DELIVERY` and `ORA_SVC_MY_SR_TEAM_SRS`,
|
||||
using the existing general tokenrelay Bearer. It uses the Fusion `searchResources/latest`
|
||||
query endpoint, independently of the opportunity query version. Calls appear in
|
||||
the Service Requests debug category with masked credentials.
|
||||
|
||||
Records are linked by `OpportunityName_Id_c.OptyNumber`. A green SR badge indicates
|
||||
one or more matches; its tooltip lists each SR number, title, reported hours, owner,
|
||||
email and contact flags. A red badge indicates no match within that query's scope.
|
||||
A failed lookup shows `SR ?`, not a false no-match result, and opportunities still load.
|
||||
Badges follow Ramp Months and do not wait for product downloads. SR results remain
|
||||
in memory only. Reference changes share the in-flight lookup and reuse its result
|
||||
(including failures) without another request. Closing resets this state; reopening
|
||||
starts a fresh lookup, and responses from previous openings are ignored.
|
||||
|
||||
## Build
|
||||
|
||||
Use Node.js:
|
||||
|
||||
Reference in New Issue
Block a user