@wxcc-desktop/sdk 2.0.2 → 2.0.4

package/README.md

@@ -306,6 +306,7 @@ Desktop.agentContact.addEventListener("eAgentMonitorStateChanged", msg => consol
 Desktop.agentContact.addEventListener("eAgentMonitoringEnded", msg => console.log(msg));
 Desktop.agentContact.addEventListener("eAgentOfferCampaignReserved", msg => console.log(msg));
 Desktop.agentContact.addEventListener("eAgentAddCampaignReserved", msg => console.log(msg));
+Desktop.agentContact.addEventListener("eAgentCampaignContactUpdated", msg => console.log(msg));
 
 // Module supports removing added listeners like:
 const listener = msg => console.log(msg);
@@ -399,9 +400,16 @@ import { Desktop } from "@wxcc-desktop/sdk";
 
 // List of available agent-contact aqm reqs:
 await Desktop.dialer.startOutdial({ ... });
+await Desktop.dialer.previewCampaignAccept({ ... });
+await Desktop.dialer.previewCampaignSkip({ ... });
+await Desktop.dialer.removePreviewContact({ ... });
 
 // List of available agent-contact aqm notifs events:
 Desktop.dialer.addEventListener("eOutdialFailed", msg => console.log(msg));
+Desktop.dialer.addEventListener("eCampaignPreviewAcceptFailed", msg => console.log(msg));
+Desktop.dialer.addEventListener("eCampaignPreviewSkipFailed", msg => console.log(msg));
+Desktop.dialer.addEventListener("eCampaignPreviewRemoveFailed", msg => console.log(msg));
+
 
 // Module supports removing added listeners like:
 const listener = msg => console.log(msg);
@@ -587,9 +595,25 @@ Desktop.webexMetricsInternal.trackBehavioralEvent(name: string, options?: EventP
 
 ```
 
-### Publishing the wxcc-desktop/js-api
+## Publish `@wxcc-desktop/sdk` to External npm Repository (e.g., npmjs.com)
+
+To publish the `@wxcc-desktop/sdk` package to an external npm repository like npmjs.com, follow these steps:
+
+1. **Verify Membership**  
+    Ensure you are a member of the `@wxcc-desktop` project on npmjs.com. If not, contact your lead to request access.
+
+2. **Update Version**  
+    > ⚠️ **Important Step: Update Version**  
+    > Increment the version number in the `package.json` file according to semantic versioning. Ensure the version changes are merged into the `main` branch before publishing. 🛠️📦
+
+3. **Run Publish Command**  
+    Execute the following command to publish the package:
+    ```bash
+    npm run publish:external
+    ```
 
-For publishing internally to Internal Cisco Repository: `yarn npm:publish:internal`
-For publishing to both Internal and public Repo : `yarn publish:external`
+4. **Login to npmjs**  
+    During the process, npm will prompt you to log in to npmjs via your browser. Complete the login process.
 
-`publish:all` responsible for publishing in both first internal repository and then to the external public repository npmjs
+5. **Verify Publication**  
+    After a successful login, the new version of the package will be published to npmjs.com.