2026 09 17 12 32 56 Heineken sesion control

Session Introduction and Objectives

Overview of the Meeting

• The session is recorded for future reference, focusing on validating the connection PI.

• The team from Sixpen, the supporting provider for the Xpils 2026 chatbot project, is present.

Technical Discussions

• Efraín shares technical inputs regarding WhatsApp development, emphasizing adherence to global security protocols.

• Discussion on viable connection options and technical topics related to service development begins.

Service Structure and Documentation Issues

Service Type and Compatibility

• The team reviews technical documentation, highlighting that GMS Cloud supports REST services.

• Comparison of response structure with presentation data reveals discrepancies in output data.

Documentation Completeness

• Noted gaps in documentation include missing fields like "unlock date," which are crucial for service updates.

• A request is made for assistance in updating both service functionality and documentation to align with Genesis requirements.

Adjustments and Communication Protocol

Service Adjustments

• Confirmation that the service can be adjusted to REST type; previous documentation may not reflect recent changes.

Security Requirements

• Emphasis on HTTPS communication through port 443 as a requirement due to cloud-based platform needs.

Infrastructure Support and Tunnel Setup

Network Infrastructure Considerations

• Discussion about web services being inaccessible outside PNIC network; reliance on infrastructure support for tunneling solutions.

Tunneling Details

• Importance of discussing how REST services will be accessed through a tunnel setup is highlighted.

API Accessibility and Testing Needs

API Public Access Requirement

• Clarification that Genesis requires public API access due to its cloud nature, necessitating secure connections via HTTPS.

Documentation Enhancements

• Suggestions made for improving documentation clarity regarding input/output values and field definitions needed for development testing.

Communication Setup Process

Tunnel Creation Steps

• Roberto seeks additional information necessary for establishing communication through the tunnel setup process.

Template Utilization

• Presentation of a template used by the team to facilitate tunnel creation; basic information required includes IP addresses and firewall configurations.

Finalizing Communication Parameters

Configuration Essentials

• Key parameters discussed include source/destination IP addresses, ports used, and ensuring proper configuration for successful communication establishment.

Discussion on API Integration with Heineken

Historical Context and Existing Services

• The conversation begins with a reference to historical data regarding services already established with Heineken, indicating prior integrations that may inform current discussions.

Implementation References

• Participants suggest using previous implementations as references for the current project, questioning if any existing flows in the Genesis platform utilize Heineken's APIs.

Configuration and Communication

• There is speculation about whether existing configurations can be replicated or adapted for new requirements, emphasizing the importance of understanding past setups.

• Acknowledgment that communication between applications within Genesis Cloud has been established previously, which could facilitate future integrations.

Technical Considerations for Tunnels

• Discussion arises about sharing an existing tunnel for API access versus requiring separate tunnels for each application, highlighting efficiency concerns.

• Clarification on how adding to an existing tunnel might simplify processes without needing extensive reconfiguration.

Fast Tracking Information Gathering

• Participants seek confirmation on the quickest path to gather necessary information regarding IP addresses and connections related to Genesis Cloud.

• Emphasis on identifying specific projects or interfaces that could provide context for ongoing integration efforts.

Locating API Origins

• The need to identify where APIs originate from is discussed, stressing the importance of locating the correct tunnel setup for including PI addresses.

Streamlining Processes

• Suggestions are made to avoid building new systems by simply adding required elements to existing configurations if possible.

Identifying Endpoints and Configurations

• The group discusses passing along URD addresses of used APIs configured in Genesis as a means of identification and troubleshooting.

Firewall Management Challenges

• Concerns are raised about firewall management complexities when trying to establish connections based solely on IP addresses provided by others.

Collaboration with Support Teams

• Plans are made to consult support teams or review past projects for additional insights into connection issues or configurations needed.

Consistency in IP Addresses

• It is noted that since this is a cloud service operating within the same region, it’s likely that IP ranges will remain consistent across implementations.

Contacting Previous Collaborators

• The importance of reaching out to previous contacts at Heineken who were involved in earlier implementations is highlighted as a potential resource for gathering technical details.

Documentation Needs

• Participants express hope that shared documentation from Heineken will clarify technical specifications relevant to their current project needs.

Importance of Shared Information

• Any information shared will be beneficial even if previous communications cannot be traced; it would assist in establishing new connections.

Next Steps and Action Items

Clarity on Information Sharing Timeline

• A request is made for clarity regarding when specific information such as IP addresses and API names can be shared among team members.

Internal Research Responsibilities

• Team members agree they will search internal records related to historical projects with Heineken while also looking into contact points.

Coordination Efforts

• One participant commits to finding relevant information by tomorrow due to tight timelines while ensuring alignment with other team members' findings.

Firewall Specifications Needed

• Discussions include specifying firewall types and ports required during configuration discussions, ensuring all parties have aligned expectations moving forward.

Checkpoint Planning Post Information Gathering

• Plans are proposed for another checkpoint meeting after receiving updates from Efraín and Jesús regarding gathered information.

Dependency on Existing Communications

• If REST API services already exist through Genesis Cloud, replicating those flows should streamline future work; otherwise more effort may be needed based on available data.

Discussion on Project Dependencies

Clarification of Work Plans

• The team discusses the need for a comprehensive work plan that includes all dependencies to avoid project delays.

• There is uncertainty regarding whether Diego has been informed about specific dependencies affecting development progress.

Organizational Structure and Confirmation

• A question arises about which organization will initiate the work, with an assumption that it will be the productive organization, pending confirmation.

• It is noted that another session may be necessary to clarify these points, as there are mapped activities that need to be initiated.

Integration and Configuration Issues

• The speaker mentions reviewing internal communications and confirms integration with View Social but highlights missing configuration for a new WhatsApp number for a bot.

• Emphasis is placed on documenting all dependencies in plans to prevent issues related to project volume discrepancies.

Timeline and Follow-Up Actions

• The timeline for addressing certain points was mentioned previously, indicating they could only be reviewed starting September.

• As September has arrived, there’s acknowledgment that some items are not yet mapped in the plan; further discussions are planned.

Final Points and Next Steps

• The conversation wraps up with a request to review conversational flow documents sent earlier and address any service-related queries.

• A suggestion is made to send questions via email instead of scheduling additional sessions due to time constraints previously expressed by Efra.