Implementation process

Client engagement

Existing clients

Key Account Executive:

  1. Conducts a high-level discovery with the client to determine business needs and required outcomes.

  2. Consults with the business (both the Client Team Lead and Integrations & Solutions Manager for FMS clients, and the latter for SaaS and supported clients).

  3. Meets with the client along with the relevant Affinity representatives.

  4. Asks the Integrations & Solutions Manager to prepare the work estimate by emailing helpdesk@affinityteam.com. This automatically creates a Zoho ticket.

  5. Continues to track the request (opportunity) in Salesforce.

Integrations & Solutions Manager:

  1. Prepares the work estimate.

  2. Asks the Key Account Executive to review it and give feedback.

  3. Refines the estimate based on feedback. This may be influenced by our relationship with the client, and other factors.

Key Account Executive:

  1. Finalises the work estimate and sends it to the client.

  2. Creates a Hive card on the Client Pipeline board.

  3. Once signed off, assigns the card to the Integrations & Solutions Manager to start development.

New clients

For new clients, integrations are managed within the onboarding project if in scope, and if out of scope they are managed via the change management process. The Affinity Lead Consultant for the project will engage the Integrations & Solutions Manager via a Hive card and assign the ticket to them signalling that development can begin.

Web API implementation steps

These steps are for clients wishing to utilise our API.

  1. The client requests API keys and authentication credentials from us.

  2. If the client requires web hooks to notify changes to employee objects in the Affinity system, we will provide them with a target URL (to send messages to), along with an HMAC secret (for message security).

  3. The client does the required setup on their end, using our API docs as a guide.

  4. The client audits their data (if relevant) based on data extracts provided by us.

  5. The client performs unit and end-to-end testing.

  6. The client is satisfied with their API integration and is now 'live'.

  7. Once live, the client monitors transaction volumes to ensure they comply with our fair use policy.

File-based transfer implementation steps

These steps are for clients wishing to transfer data via secure files.

  1. The client obtains SFTP credentials and standard file format information from us.

  2. The client works with us to configure secure file exchange processes.

  3. The client audits their data (if relevant) based on data extracts provided by us.

  4. The client tests data flows using production-like environments.

  5. The file is used in production and the integration is deemed 'live'.