Feature #215
openCAS-SF Integration Engg request
70%
Files
Updated by Stacy Kinkar 8 months ago
- Due date set to 02/28/2025
- Status changed from New to In Progress
- % Done changed from 0 to 20
dev- Sand
"02/11/25: Review all the documents needed
02/13/25: Setup Altice Salesforce Integration's AccessToken, ClientID, and ClientSecret
02/14/25: Setup CAS Dev locally"
Updated by Stacy Kinkar 8 months ago
- Due date changed from 02/28/2025 to 03/14/2025
- % Done changed from 20 to 70
- Justin informed Altice that dev testing is ongoing until the end of this week, and deployment to production will be early next week
3/7/25 - 3/10/25 - Compare database mapping between dev and prod
- Waiting for the Salesforce production login from Altice
Updated by Stacy Kinkar 7 months ago
Hereβs the latest status update for the ALTICE Salesforce-CAS Integration Project:
β Deployment to Production β Completed
The full deployment to production has been completed successfully as of March 24.
The process included:
Mapping data between Dev and Prod
Setting up test users and properties
Uploading and configuring the integration files
Resolving code coverage issues for deploying the webhook, triggers, and authentication logic
Final validation and logic adjustments for visibility across Altice properties
π New Task Post-Deployment β In Progress:
Change in Integration Logic
Instead of CAS looking up the Salesforce Property ID, the logic will now use the CAS HotelID in Salesforce for property matching.
This task has been added as a follow-up activity after deployment.