website logo


In This Section



SPONSORS

Integration Discovery: Read

Information

During this call, we will cover the business requirements for the product line that will be launching first. Then, we will set up additional discovery calls for each product line in order to ensure each business rule and use case has been covered. 

Note: If you are contracted for multiple product lines and are integrating SSO and/or a web service search/read for multiple products, please fill out a survey for Each product line (as the information read may be different per product).
This is the date the public will start submitting registrations, purchasing booths, submitting abstracts, etc...

Note: Integration should not hold up submission forms from going live. If integration is not ready by your live date, individual and company records will be imported into eShow's CRM. The submission forms will read from our CRM until integration is ready.

Once integration is ready, tested and approved, we will activate integration on your form(s). If we are updating records in your AMS for contact information updates made through the submission form, we can do a batch update to your AMS when the integration is completed as well. To be able to do this, simply include your member number in their record as such and as their sync id.


Integration Entry Point
Implementing SSO will require the first individual submitting the form to login to your Association member website using their member login credentials. 

Web service search:
For additional individuals being added to the submission form (additional registrants, authors, ect....), they will be searched using the web service search. These fields will also be used by your staff when registering attendees through admin. We'll identify those search fields shortly. 

Important: If we are your onsite registration provider, we DO NOT use SSO for onsite registration. We incorporate the web service search for the onsite registration form.  

Note: Not all AMS systems have out of the box standardized SSO.  If they do not, you will need to contact them or another AMS contractor to create one for you.
Select the search fields that will be used for the web service search. These fields will be used for:
  • First person search (when SSO is not implemented)
  • Additional person searches
  • Admin submissions (your staff registering people through our admin system)
  • Onsite registration (when we are the onsite registration provider)
Note: Last name, email address and company name are best practice options because of their uniqueness. 

Member ID is not advised because when you add additional submissions, the primary submitter most likely will not know their colleagues' member id or number.
Please enter the endpoint URLs' below for the following, based on what is applicable for your integration. Also, include login credentials for eShow to access the ULRs'.

Endpoint URLs' needed:
  • getPersonInfo
    • accepts: member Id 
    • returns: basic person info, member status, membership types, company name etc.
  • SearchIndividual
    • accepts: firstname, lastname or  email
    • returns: search results that matches one or more of the above along with basic person info, member status
  • SearchCompany
    • accepts: company name or company id
    • returns: search results that matches one or more of the above along with basic company info, member status, membership types, company name etc.
       

Information to be Read
Member Status: This is used for member / non member pricing. 

Member types: These are not required to pull when you have member / non-member pricing. Member types are primarily used when different member types receive different pricing. An example would be if a Retired Member receives different rates than a Student Member. If this is applicable, then we can pull the member types and only display the applicable fees tied/mapped to the member registration fees.

Demographic/Survey questions: In order to populate responses from your AMS, these questions will need to be created in eShow and mapped accordingly. 
Use Cases
Methods needed:
Service Center Authentication
If yes, the individuals will use their Association login credentials to access eShow's service centers. If you do not want us to authenticate, eShow will assign the individual's a unique login and password to access the service centers with.

Note: Individual's that are in multiple products will be assigned 1 login and password and use it to access any service center they are associated with. An example would be a speaker would use the same login and password to login to the speaker service center as well as the attendee service center (to update their registration).

Service Centers: Attendee Service Center, Exhibitor Service Center, Abstract Service Center, Speaker Service Center, Meeting Service Center.
Additional Notes
Any additional information you feel is helpful, please enter it here. For example, list out any possible issues or unique processes that could cause delays with this project or are areas we should be aware of.