I'm using Add-on Mart apps on my current production system. Will they work with Dual Version?
If your system is using various Add-on Mart modules, our team will identify those during the pre-migration analysis stage, and we will create additional test scenarios to validate that those modules work properly in the Dual Version mode.
What are your recommendations on adapting existing or new apps to work with Dual Version?
Start by reviewing the API methods your application uses and grouping them according to the access type:
- Transparent – the method always includes i_customer or i_account. No changes needed.
- Semi-transparent – the method includes i_customer or i_account in some cases. For API calls where these parameters are absent, first set the context (whether the source or target system should handle the API request) using the dedicated API method Session.set_session_context.
- Explicit – the method never includes i_customer or i_account. Always set the context using Session.set_session_context before executing the request.
For detailed guidance and examples, see Adapting third-party applications to Dual Version PortaSwitch.
What should we do about external applications when the Dual Version migration is completed and the source system is turned off?
External applications built according to the guidelines in Adapting third-party applications to Dual Version PortaSwitch do not require any changes. Once the source system is decommissioned, all API requests are routed to the target system. During subsequent Dual Version migrations, the applications continue to work as expected.
