Assumptions:

1. 3rd party vendor has been validated.

Implementation steps:

1. Signed contract/agreement from the mutual customer(s).
• Contract/agreement provides license and permission to share customer data with the 3rd party.
2. Identify and populate 3rd party vendor/client details. This will allow the 3rd party vendor to verify connectivity to our environment.
• This step is only required once per 3rd party vendor/client.
• Populate CLIENT_AUTH_OBJ_OWNER.OAUTH_CLIENT_DETAILS.
3. Identify and populate mutual customer details. Coordinate and communicate with the 3rd party vendor/client as this will enable access to community and customer information. We will also want to communicate to the mutual customer(s) since these steps involve user experience changes.
• Populate CLIENT_AUTH_OBJ_OWNER.CLIENT_COMMUNITY_ACCESS.
• Populate CLIENT_AUTH_OBJ_OWNER.CLIENT_CUSTOMER_ACCESS.
• Update FC_OBJ_OWNER.COMMUNITIES table to API_CONNECT_LICENSED = 'Y'.
• This step changes user experience via Backoffice so generally we want to communicate to the mutual customer(s) when this is completed.
1. An email is required for new customers.
2. A different message will appear upon saving of the new customer.
• Review logs on tomcatintegrationprod01 for activity from 3rd party vendor/client related to enabled customer.
4. IF USING OLD VERSION OF RESIDENT PORTAL - Confirm Resident Portal is properly enabled on FullCount side
• Add community_id and open production URL in browser to confirm RP has been properly enabled
• https://portal.fullcount.net/ResidentSelfServicePortal/login.htm?communityId=<add here>