Configuring Connect to process subscriptions

Note: This article covers Vista Classic systems. If you use the Cloud system, contact Vista support for assistance with configuring Connect. 

Set up Connect to allow Subscriptions to work over remote sales channels. Connect processes subscriptions by linking data from Loyalty with third-party membership data from Cinema.

Note: This process uses Connect's third-party ticketing system and provides a better user experience on top. The third-party ticketing system is still available as an alternative option.

Before you begin

• Ensure Subscriptions have been set up in Loyalty.
• Ensure there's an entry in the Cinema database under tblMemberModuleConfig for each subscription you want Connect to process.

Steps

1. In SQL Server Management Studio, open the VISTAIT database.
2. For each subscription, insert a new row into tblThirdPartyMemberTicketScheme with appropriate values in the following fields:
    
   • ThirdPartyMemberTicketScheme_strCinemaCode: The VISTAIT cinema ID that can be looked up in tblCinema. A dash can be used instead as a wildcard for all cinemas.
   • ThirdPartyMemberTicketScheme_strId: The ID of the third-party scheme representing your subscription. This is found in the Cinema database, under MMC_strName in tblMemberModuleConfig.
   • ThirdPartyMemberTicketScheme_bitSupportsPartialApproval: A boolean that should be set to false.
   • ThirdPartyMemberTicketScheme_bitIsLoyalty: A boolean indicating whether the row represents a Loyalty third-party member scheme. Set to true.

   • ThirdPartyMemberTicketScheme_intTenantId: Set to 1, unless you're running a multi-tenanted Connect, in which case, this is the ID of the circuit that configured the subscription.

     Note: Other fields don't require specific values or are nullable.

3. For each subscription, insert a new row into tblThirdPartySchemeLoyaltySubscriptions with the appropriate value in the following field:
   • ThirdPartyMemberTicketScheme_intLoyaltySubscriptionId: The ID of the subscription, found in the Loyalty database, under subscription_id in tblSubscription.

See Selling subscriptions on a website for the next steps.