Event Configuration

This is the complete configurations list, outlining all fields at all access levels. For configurations available at user access level, see Event Configuration article.

Feature Configurations should only be configured by your deployment team. If you do not have access to a feature included in your package, please contact your IM for additional assistance.

Products (10)
1. Use – This field was used to determine the navigation structure in older versions of the software.
  1. Value – Drop Down List [Show, FP, EZ]
  2. Default Value – Show
  3. Description - Configure the admin for Show, Floorplan or EZ (Values Accepted: show, fp, ez)
2. Consequences of change:
  1. N/A as this was only used in previous versions of the system.
Public Side URL (10)
1. Use – Content, Message, File, and Template management all utilize this field to determine the location of the public-facing event website. If this field is not set up properly, then information will not flow to functional pages on the event website, such as the Event Map. Additionally, merge fields that reference the event website will not work; Online Sponsorship Sales link builder, and File Management will not be functional [a Global Admin User will see the Page Not Found Error]. On the Event Website, Exhibitors and Attendees may not be able to utilize the functionality, and content from Content Management may not display.
  1. Value – text, formatted as a URL, https preferred beginning 9/27/2017.
  2. Default Value – When the public event site is created this value is automatically updated.
  3. Description - Complete URL to public side (e.g. http://dev4.a2zinc.net/ABC/ABC08)
2. Consequences of change:
  1. File management will not load/allow file uploads
  2. Relative URLs will not work as expected
Units (10)
1. Use – The Unit controls how the floor plan booth dimensions are displayed, as well as how the units display on the Event Map, Booth/Activity tab of the company record, and in reports/dashboards. When the unit is in Inches the booths will display in feet and inches [10’x10’], and the Move/Resize functions will accept feet and inches [10, 10’6”]. When it is in Meters the booth sizes will display in Meters [3m x 3m], and the Move/Resize features will accept meters [3, 3.5]. These units are also used to create the QUANTITY for booth space orders [9 for a 3mx3m booth; 100 for a 10’x10’ booth]
  1. Value – Drop Down List [Inches, Meters]
  2. Default Value - Inches
  3. Description - Display Dimensions on the Floor plan in Inches or Meters
2. Consequences of change:
  1. The unit of measure display on the Floor plan, as well as the Booth tab and reports will change.
  2. This will cause errors in the Orders if you change mid-cycle, as order quantity is based on booths dimensions [9 for a 3mx3m booth; 100 for a 10’x10’ booth].
Default Map (10)
1. Use – This controls which floor plan map shows when an end user on the public event site opens the event map. This is only applicable for shows with multiple floor plan maps
  1. Value – Drop Down List of the Maps that are set up for this event. If more than one map is present, "Thumbnail" setting is also available.
  2. Default Value – First Map in the list.
  3. Description - Default Map
2. Consequences of change:
  1. The map that shows when an end user opens the event map will change to be the map that is selected in the drop down.
Event Manager Email (9)
1. Use – Templates for exhibit and finance related emails [unless otherwise defined below] utilize this email address in the ‘From’ field. This is also where the replies will be sent, and any bounce-backs.
  1. Value - A single email address
  2. Default Value – projectmanagers@a2zinc.net
  3. Description - Serves as the From address for most exhibit and finance related template emails, unless otherwise defined below.
2. Consequences of change:
  1. The From address on most exhibit and finance related template emails [unless otherwise defined below] will change to the new email address entered, when emails are sent. This will also change who receives replies and bounce-backs.
Finance Manager Email (10)
1. Use – Templates for Statement and Invoice emails utilize this email address in the ‘From’ field. This is also where the replies will be sent, and any bounce-backs, and who receives notifications of online payment.
  1. Value - A single email address
  2. Default Value - [blank]
  3. Description - Serves as the From address for Statement and Invoice templates.
2. Consequences of change:
  1. The From address for Statement and Invoice template emails will change to the address entered, when emails are sent. This will also change who receives replies and bounce-backs, and who receives notifications of online payment.
Contracts Manager Email (10)
1. Use – Templates for all contract-related emails utilize this email address in the ‘From’ field. This is also where the replies will be sent, and any bounce-backs.
  1. Value -Text Box
  2. Default Value - [blank]
  3. Description - Serves as the From address for all contract-related template emails.
2. Consequences of change:
  1. The From address for all contract-related template emails will change to the address entered, when emails are sent. This will also change who receives replies and bounce-backs.
Event Exhibitor Marketing Contact (9)
1. Use – This sets the Contact type that will be used when Marketing Contact is selected in Templates To and CC hierarchies.
  1. Value – Drop down list of contact types whose Number of Contacts is 1
  2. Default Value – [select]
  3. Description - This field can be used to indicate the Contact Type that would receive the communications for this event that are directed to the Marketing contact
2. Consequences of change:
  1. The Contact type that is chosen when an email is sent to the Marketing Contact will change to the new Contact type.
Event Exhibitor Primary Contact (9)
1. Use – This sets the Contact type that will be used when Primary Contact is selected in Templates To and CC hierarchy.
  1. Value – Drop down list of contact types whose Number of Contacts is 1
  2. Default Value – [select]
  3. Description - This field can be used to indicate the Contact Type that would receive the majority of communications for this event.
2. Consequences of change:
  1. The Contact type that is chosen when an email is sent to the Primary Contact will change to the new Contact type.
Sponsorship Manager Contact (9)
1. Use – This sets the Contact type that will be used when sponsorship email are sent out via a2z.
  1. Value –
  2. Default Value – [blank]
  3. Description - What email address should be used as the 'From' address for the Sponsorship Confirmation?
2. Consequences of change:
  1. The From address for Sponsorship email template will change to the address entered, when emails are sent. This will also change who receives replies and bounce-backs.
Public Side View (10)
1. Use – This option is used to determine how much booth/exhibitor information is displayed on the Event Website (floorplan.aspx, eventmap.aspx, and floor plan displays in the Online Exhibitor Contract).
  1. Value – Drop Down List [View 1, View 2, View 3, View 4]
  2. Default Value – View 3
  3. Description - What booth information would you like to display on your public site floor plan? View 1: Booth Layout Only View 2: Color Coding for Booth, No Company Name View 3: Standard, default view. View 4: Full Information - In addition to view 3, this will provide Co Name for Reserved booths as well.
2. Consequences of change:
  1. When the view is changed the information that is displayed on the EventMap.aspx and Floorplan.aspx (this includes the display of the floorplan in the Online Exhibitor Contract) public facing pages will reflect the parameters of the new view.
Session Survey Link (10)
1. Use – Add a 3rd party survey URL to display in Sessions to collect attendee feedback about sessions.
  1. Value – Text Box
  2. Default Value – [blank]
  3. Description - Do you have a link to a survey you would like users to access from your sessions?
2. Consequences of change: Survey link displaying in sessions will be changed.
Masthead URL (9)
1. Use – The masthead on the Event Website will be hyperlinked to this website.
  1. Value – Text Box
  2. Default Value – http://www.a2zinc.net
  3. Description - What URL would you like users to access when clicking on your public site masthead?
2. Consequences of change:
  1. The masthead on the Event Website will be hyperlinked to the new URL.
Flag Exhibitors as Upgraded (10)
1. Use – a legacy feature. Exhibitor updates now handled via Online Booth Configuration screen.
  1. Value – Drop Down List [Yes/No]
  2. Default Value –No
  3. Description - Would you like to indicate which exhibitors have upgraded eBooth content on your public site?
2. Consequences of change: N/A as this was only used in previous versions of the system.
Navigation Display for PS (10)
1. Use – This controls where the navigation bar is located on the Event Website.
  1. Value – Drop Down List [Left Navigation, Top Navigation, Top-Left Navigation, Hybrid Navigation]
  2. Default Value – Left Navigation
  3. Description - Choose from the four, the required Navigation to be seen in your Public Site
2. Consequences of change: Website style changes (such as color, font, etc) may need to be updated to work with the new navigation style
Public Site Interface Configurations (10)
1. Use – Display and undisplay design elements on the website.
  1. Value – Check Box List [Left Bar, Util Bar, Google Mini, Right Bar, Masthead]
  2. Default Value – all checked except Masthead
  3. Description - Public Site Interface Configurations
2. Consequences of change: Left Bar: shows or hides the container for left navigation and messages above and below it. Affects main content area width. Util Bar: shows or hides a small toolbar below top menu line. Google Mini: a searchbox; legacy feature, no longer operational. Right Bar: shows or hides the container for messages on the right side of the page. Affects main content area width. Masthead: shows or hides masthead image container.
FP Upgrades (10)
1. Use – This feature tells the eventmap.aspx, and floorplan.aspx pages what to do when a booth is selected by clicking on it. Basic will do nothing, Hyperlinked will use setting in the Hyperlink Field and (if applicable) the Hyperlink URL text box in Event Configuration to link out to another site, Profile will open the Exhibitor Profile when an assigned booth is selected by clicking on it.
  1. Value – Check Box List [Basic, Hyperlinked, Profile]
  2. Default Value – Basic and Profile. Basic cannot be unchecked.
  3. Description - This will contain the information about the upgrades as a binary sum.
2. Consequences of change:
  1. If Profile is deselected the Exhibitor profile will not open when an assigned booth is clicked on.
  2. If Hyperlink Field is selected a new tab will open and direct the user to a website based on the setting in the Hyperlink Field and (if applicable) Hyperlink URL text box in Event Configuration.
Hyperlink Field (10)
1. Use – When the Hyperlinked option is selected as the FP Upgrades option in Event Configuration, the system chooses where the user will be directed to when an assigned booth is selected by clicking on it. If Company URL or Booth URL are selected, then nothing needs to be entered in to the Hyperlink URL field in Event Configuration. If Name, Booth Label, Company Number or CoID are selected, then a URL that ends with the parameter that should be filled in with the selected field (example below in the Hyperlink URL section) should be entered in to the Hyperlink URL text box in Event Configuration.
  1. Value – Drop Down List [Name, Company URL, Booth Label, Company Number, Booth URL]
  2. Default Value – Company URL
  3. Description - Identifies which field needs to be used if hyperlink is purchased.
2. Consequences of change:
  1. Changing the option changes which database field the system will use to select/create the URL that the end user is directed to when they click on an assigned booth.
Hyperlink URL (10)
1. Use – When the Hyperlinked option is selected as the FP Upgrades option in Event Configuration AND the Hyperlink field is set to Name, Booth Label, or Company Number then the system will use the URL entered in to this field AND the value from the Hyperlink field for the company whose booth was clicked on to create the URL that the end user will be directed to [in a new browser window]. The URL should be entered so that the parameter that utilizes the Hyperlink Field is last, as the system will append the URL will the value of the hyperlink field. Example – if the Hyperlink Field is ‘Name’, and the Hyperlink URL is ‘https://myurl.com/profile.aspx?coname=’ then the resulting URL when the booth for ‘ABC Company’ is clicked on will be ‘https://myurl.com/profile.aspx?coname=ABC%20Company’
  1. Value – Text Box
  2. Default Value – blank
  3. Description - Identifies what URL to use if hyperlink is other than company or booth URL.
2. Consequences of change:
  1. Changing the URL will change the web page that the end user is directed to when they select an assigned booth by clicking on it.
Booth Listing (10)
1. Use –This controls what the exhibitor list displays when an Exhibitor has purchased two different booth locations at the same event. Single Booth Listing will show one row for the Exhibitor with the booth numbers comma separated [ABC Company 123,701], Multiple booth listing will show a row for each booth location purchased [ABC Company 123; ABC Company 701]. This also affects how the Exhibitor Console will look, single listing has one unified console, while multiple listing will display one console per booth location. Additionally, when multiple listing is selected each booth location has a separate profile by default – however this can be forced in single listing mode by breaking the parent/child relationship on the booth configuration screen (accessible from the company’s booth tab in Global Admin), while maintaining the single listing style in the exhibitor list.
  1. Value – Drop Down Box [Single Booth Listing, Multiple Booth Listing]
  2. Default Value – Single Booth Listing
  3. Description - Multiple or Single booth listing
2. Consequences of change:
  1. Switching modes from Single to Multiple listing will affect the exhibitor list, by increasing the times an exhibitor with multiple booth locations is listed.
  2. Switching modes from Single to Multiple listing will affect the Exhibitor Console by increasing the number of console groups an exhibitor will have to fill out (one per booth location)
Confirmation Letter (10)
1. Use – This controls how Exhibitor Confirmation letters are sent out. Single will send out one letter per company, regardless of how many separate booth locations that they have. Multiple will send out one letter per booth location.
  1. Value – Drop Down list [Single, Multiple]
  2. Default Value – Single
  3. Description - This sets the configuration for Confirmation Letters. Single will send one confirmation letter per company. Multiple will send one confirmation letter per booth
2. Consequences of change:
  1. Switching modes from Single to Multiple letters will increase the number of confirmation letters that a company will receive based on the number of booth locations that they have at the event.
Show Guide Report Listing (10)
1. Use – This controls how many listing a company has in the Show Guide Report. Single will list only the parent company/booth information, regardless of how many separate booth locations that they have. Multiple will create one listing per booth location, with the specific information from each booth’s profile.
  1. Value – Drop Down list [Single, Multiple]
  2. Default Value – Single
  3. Description - One record per company or one Record per parent booth for a company to be displayed in Show Guide Report.
2. Consequences of change:
  1. Switching modes from Single to Multiple will increase the number of unique listings that a company will have in the Show Guide Report based on the number of booth locations that they have at the event.
Attendee Login Schema (10)
1. Use – Checking off the criteria (or criterion) that an attendee must use to log in to the public facing Event Website will update the attendee log in screen on Event Map as will as mybriefcase.aspx (this page is used for Registered Attendees, Speakers, Connect-Registered Attendees, as well as non-registered attendees if they are allowed to log in to save favorites, etc.). If a login schema requires an integration, then a drop down list (ddl) will be present underneath that option so that an integration can be associated with it, the drop down list will only become active when the checkbox is selected.
  1. Value – Check Box List [Using eCode; Using Email and eCode; Using Email; Using Member ID and Password; Using Email and Password; Using Badge Number{select integration ddl}; Using MemberID {select integration ddl}; Using Email Address and MemberID {select integration ddl}; Using Email Address and Badge Number {select integration ddl}]
  2. Default Value – Using Email and Password
  3. Description - This will be used for Attendee Login (Requires Public Side to be vX or above)
2. Consequences of change:
  1. Adding ways to log in will increase the options an attendee has to log in on each log in screen.
  2. Removing ways to log in will decrease the options an attendee has to log in on each log in screen.
  3. If an end user is not included in the selected integration for a schema, AND no non-integration schema is selected, the end user will not be able to log in at that time.
Exhibitor Login (10)
1. Use – Exhibitor Login controls which eCode needs to be entered to update booth information and access the exhibitor console. ‘Company’ utilizes the Company eCode, which is global to the company regardless of event or booth location, and can be reset from the ‘Company Info’ of the Company record. ‘Booth’ utilizes the Booth eCode, which is specific to a booth location at a specific event, meaning one company with multiple booth locations at a single event would have multiple passwords, and can be reset from the Booth Configuration screen for a booth location on the booth tab of the company record.
  1. Value – Drop Down List [Company, Booth]
  2. Default Value – Company
  3. Description - Configure Exhibitor login for public site (Company or Booth)
2. Consequences of change:
  1. NOTE – If you choose the Booth login option, the #30 Exhibitor confirmation Letters Template will need to be updated to reflect booth password instead of company password
  2. If Exhibitor Login is changed to Booth AND Confirmation Letters is set to Single exhibitors with multiple booth locations will not receive all their passwords, just the password to the first booth in their list of locations.
  3. This is an old feature, and may not be compatible with all email template options.
Booth Type (10)
1. Use – This controls whether booth type is required to be filled in when booths are assigned/reserved. ‘Yes’ indicates that booth type is to be filled in, ‘No’ indicates that it does not need to be filled in.
  1. Value – Drop Down List [Yes, No]
  2. Default Value – No
  3. Description - Enable/Disable Booth Type.
2. Consequences of change:
  1. Switching from No to Yes will force GlobalAdmin users to select a Booth Type from the Booth Type drop down on the Assign, Reserve, or Move Exhibitor functions on the floor plan if there is not already a booth type associated with that booth space.
  2. Switching from Yes to No will stop forcing the selection of Booth Type by Global Admin users on the Assign, Reserve, or Move Exhibitor functions of the floor plan. Disabling Booth Type may adversely effect pre-programmed online contract logic if pricing depends on booth types.
Minimum Access Level for Booth Type (9)
1. Use – Set the minimum access level that a Global Admin user can have to update booth types on the floorplan.
  1. Value – Text Field
  2. Default Value – 8
  3. Description -To set Minimum Access Level for Booth Type
2. Consequences of change:
  1. Increasing the Access Level will remove the ability to update booth type for lower access levels.
  2. Decreasing the Access Level will add the ability to update booth type for lower access levels.
Minimum access level for layout changes (Merge, Split, Delete, Revive) (9)
1. Use – Set the minimum access level that a Global Admin user can have to change the layout of the floor plan using the functions that manipulate booths within the Max view: Merge, Split, Delete, and Revive
  1. Value – Text Field
  2. Default Value – 6
  3. Description - To set the Minimum Access Level for Layout Changes (Merge, Split, Delete, Revive)
2. Consequences of change:
  1. Increasing the Level will remove the ability to make these changes from lower access levels
  2. Decreasing the Access Level will add the ability to make these changes for lower access levels.
Minimum access level for layout changes (Resize, Move, Adv Merge, Create Poly) (9)
1. Use – Set the minimum access level that a Global Admin user can have to change the layout of the floor plan using the functions that allow diverging from the max layout: Resize, Move, Advanced Merge, and Create Poly .
  1. Value – Text Field
  2. Default Value – 8
  3. Description - To set the Minimum Access Level for Layout Changes (Resize, Move, Adv Merge, Create Poly)
2. Consequences of change:
  1. Increasing the Level will remove the ability to make these changes from lower access levels
  2. Decreasing the Access Level will add the ability to make these changes for lower access levels.
Minimum access level for editing Booth Config (9)
1. Use – Set the minimum access level that a Global Admin user can have to access and edit the Booth Configuration screen. This gives access to custom booth fields, booth coordinates, booth upgrades, booth number, salesperson, and parent/child booth relationship.
  1. Value – Text Field
  2. Default Value – 8
  3. Description - To set Minimum Access Level for Editing Booth Configuration
2. Consequences of change:
  1. Increasing the Level will remove the ability to make these changes from lower access levels
  2. Decreasing the Access Level will add the ability to make these changes for lower access levels.
Minimum Access For Financial Transactions In FloorPlan Management (9)
1. Use – Set the minimum access level that a Global Admin user can have to access the Order and Payment Screens in a Company Record, as well as add new orders from the floor plan when assigning, reserving, or moving an exhibitor.
  1. Value – Text Field
  2. Default Value – 6
  3. Description - Minimum Access For Financial Transactions In FloorPlan Management
2. Consequences of change:
  1. Increasing the Level will remove the ability to make these changes from lower access levels
  2. Decreasing the Access Level will add the ability to make these changes for lower access levels.
Financial Contact (9)
1. Use – This allows you to set up the default financial contact type to send Statement and Invoice to.
  1. Value – Drop Down list [List of Contact Types whose Number of Contacts is 1]
  2. Default Value – Invoice Contact
  3. Description - Serves as the default recipient of Statement and Invoice template emails.
2. Consequences of change:
  1. If the contact type is changed, then templates that send to Financial Contact
Financial Mode (10)
1. Use – This will determine how invoicing is handled, manual multiple invoices or one consolidated statement. This affects how the system will handle incoming payments, and payment terms.
  1. Value – Drop Down list [Automatic, Manual]
  2. Default Value – Automatic
  3. Description - Automatic or Manual financials
2. Consequences of change:
  1. Should only be changed before any financial transactions have been processed in the given event.
  2. If the value of this field is changed from Automatic to Manual:
    1. All orders would need to be added to an invoice, and the amount due specified for that invoice.
      1. Example – a booth space order for $1000 that needs to be billed at 25%, then the next 50%, then the final 25% would require 3 invoices
        
        Invoices can be comprised of multiple orders
        
        Invoices can be created in bulk
    2. On the Payments tab of the company record, payments would be recorded against an order on an invoice.
    3. Users may need to switch (or possibly transfer) between invoices when large payments are received.
      1. Example – the above order for $1000 was paid in full, the user would need to apply $250 to the first invoice, $500 to the second, and $250 to the third, even if the payment was received as a single transaction.
    4. On the public facing Event Site
      1. page ‘My Account’ (e_myAccount.aspx), payments would have to be made against an invoice, the end user would need to make multiple payments to pay multiple invoices.
      2. Online Exhibitor Contract page (e_boothsales.aspx) would not be able to accept payment, as payments must be associated with an invoice and invoices are not created during this process.
    5. When booths are assigned/reserved, an option to generate an invoice will appear.
    6. On the Orders tab of the company record there will be an option to generate an invoice at the time the order is created.
  3. If the value of this field is changed from Automatic to Manual
    1. If Invoices have already been created, there will be errors that occur on both the GA and Event Site side. This is due to Automatic financials requiring a single invoice in the invoice table. Additionally, this may create an artificially inflated amount in the ‘Invoiced Amount’ field on the Orders and Financial Summary screens in a company record; on the Financial and Event dashboards; and in the Exhibitor Order, Financial Summary, and any Custom reports that utilize this field.
    2. On the orders tab, there will no longer be an option to generate an invoice at the time the order is created
    3. When booths are assigned/reserved, there will no longer be an option to generate an invoice.
    4. On the payment tab of a company record all the orders will display, and payment can be applied to any, or all, of these orders at once.
    5. On the public facing Event Site page “My Account“ payments are made against all orders, using the Item Type and Item priority set in the Financial settings in Global Admin.
    6. Online Exhibitor Contract page (e_boothsales.aspx) can collect payment.
Paypal/Payment Gateway User Name (9)
1. Use – When processing credit cards, this is the username that Global Admin and the Event Website use to log in to the payment processor.
  1. Value – text field
  2. Default Value – blank
  3. Description - Please specify Paypal User Name
2. Consequences of change:
  1. If the User name field is changed, AND the password field in NOT updated to the corresponding password then credit card processing will not be able to happen. If this is the case then the payment type Online Credit Card, and all Event Website credit card payments (available on pages like e_myaccount.aspx, e_boothsales.aspx, e_addonsales.aspx, and e_sponsorshipsales.aspx) would not work – an error would be returned. The payment in the credit card log would show an error like “Invalid Merchant Account” in the Status column.
  2. If the User name field is changed, AND the password field is update to the corresponding password then payments will be processed as expected in the account associated with this User Name.
Paypal/Payment Gateway Password (9)
1. Use – When processing credit cards, this is the password that Global Admin uses to log in to the payment processor. When the password is saved, an encrypted value is displayed.
  1. Value – Text field [encrypted on save]
  2. Default Value – KR2l9DpYyvVV22H/4rLqMns5zjNipi74Bub5gsXmi1U=
  3. Description - Please specify Paypal Password
2. Consequences of change:
  1. If the Password field is updated in the processing system (ex. Paypal) but not in Event Configuration, then credit card processing will not be able to happen. If this is the case then the payment type Online Credit Card, and all Event Website credit card payments (available on pages like e_myaccount.aspx, e_boothsales.aspx, e_addonsales.aspx, and e_sponsorshipsales.aspx) would not work – an error would be returned. The payment in the credit card log would show an error like “Invalid Merchant Account” in the Status column. Update Event Configuration Password field to resume credit card processing
  2. If the Password field in Event Configuration is updated BEFORE the Password field in the processing system, then credit card processing will not happen. (see 35.b.i above for more details) Update processing system password field to resume credit card processing.
  3. if the Password field in Event Configuration is updated AND matches the Password field in the processing system, credit card processing will happed as expected.
Paypal/Payment Gateway Merchant (9)
1. Use – This is merchant name or id from the processor. For Paypal this is the same as the User Name .
  1. Value – Text Field
  2. Default Value – blank
  3. Description - Please specify Paypal Merchant
2. Consequences of change:
  1. If a merchant name or id is required, then removing or changing will cause credit card processing to fail. If this is the case then the payment type Online Credit Card, and all Event Website credit card payments (available on pages like e_myaccount.aspx, e_boothsales.aspx, e_addonsales.aspx, and e_sponsorshipsales.aspx) would not work – an error would be returned. The payment in the credit card log would show an error like “Invalid Merchant Account” in the Status column. Update Event Configuration Paypal Merchant field to resume credit card processing
Paypal/Payment Gateway Partner (9)
1. Use – For most processors this is left blank, for PayPal the value should be entered as PayPal.
  1. Value – Text field
  2. Default Value – blank
  3. Description - Please specify PayPal Partner
2. Consequences of change:
  1. If the processor is PayPal, and the value listed is not PayPal, then credit card processing will not be able to happen. If this is the case then the payment type Online Credit Card, and all Event Website credit card payments (available on pages like e_myaccount.aspx, e_boothsales.aspx, e_addonsales.aspx, and e_sponsorshipsales.aspx) would not work – an error would be returned. The payment in the credit card log would show an error like “Invalid Merchant Account” in the Status column. Update Event Configuration Paypal Partner field to resume credit card processing
Paypal/Payment Gateway HostAddress (9)
1. Use – This is the URL for the processor, used by Global Admin and the Event Website to log in to process payments.
  1. Value – Text field
  2. Default Value – pilot-payflowpro.paypal.com
  3. Description - Please specify Paypal HostAddress
2. Consequences of change:
  1. If the host address is incorrect, then credit card processing will not be able to happen. If this is the case then the payment type Online Credit Card, and all Event Website credit card payments (available on pages like e_myaccount.aspx, e_boothsales.aspx, e_addonsales.aspx, and e_sponsorshipsales.aspx) would not work – an error would be returned. The payment in the credit card log would show an error like “Invalid Merchant Account” in the Status column. Update Event Configuration Paypal HostAddress field to resume credit card processing
  2. If the processor has a unique HostAddress for testing, this field must be update with the test address (ex. Pilot-payflowpro.paypal.com) when testing. Failure to do so will create live payments on any credit cards processed.
  3. If the processor has a unique HostAddress for testing, AND the test HostAddress is not removed after testing is complete, all credit card transactions will run as test transactions – no live credit card charges will be created.
Paypal/Payment Gateway Comment (9)
1. Use – This will be the first value in the transaction information that will appear on the credit card statement, as well as in the processors transaction records. [example – If Paypal Comment1 is ‘a2z’ and the payment is made for ‘ABC, Co.’ with Company ID ‘206’, the charge will have the information ‘a2z(206)-ABC, Co.’]
  1. Value – Text Field
  2. Default Value – a2z
  3. Description - This data is logged in the Verisign Log as VerisignComment1(CompanyID)-Company Name
2. Consequences of change:
  1. If this value is changed then the resulting information on the payment will reflect this change on the next credit card that is processed.
Paypal/Payment Gateway Comment2 (9)
1. Use – If an additional line is able to be read by the processor, and the same information is needed for every credit card payment processed, comment2 will appear as part of the payment info as well
  1. Value – Text field
  2. Default Value – blank
  3. Description - Paypal Comment2
2. Consequences of change:
  1. Adding text here will cause that text to show up in the processors record for this payment, and may result in the text also showing on the credit card statement for the card owner.
  2. Removing the text that is in this field will cause subsequent credit card payments to not include the information that was once here.
PayPal Currency Code (10)
1. Use – This value tells Global Admin and the Event Website what currency the payment is being made in, so that the right information goes to the payment processor. [Example – the payment is entered as 1000.25, the Currency Code is set to USD, this will go to PayPal as 1000.25 US Dollars. If the Currency Code were set to EUR, this would transmit to PayPal as 1000.25 Euros]. Currency code list is specified by ISO 4217, and can be found here: https://en.wikipedia.org/wiki/ISO_4217
  1. Value – Text Field
  2. Default Value – USD
  3. Description - Please specify PayPal Currency Code(3 characters)
2. Consequences of change:
  1. If the Currency Code is not updated, then the amount of money will not be correctly transmitted to the processor. For example, if the PayPal account is set to EUR, and the Currency Code in Event Configuration is set to USD, then PayPal would charge the card in the dollars converted to euros – dependent on the current conversion rate.
AffiniPay Payment Gateway (10)
Enable ACH on MyAccount (10)
Booth Personnel Registration Start Date (9)
1. Use – This is the date that the page where Exhibitors can enter their booth personnel becomes active.
  1. Value – Calendar Tool
  2. Default Value – 1/1/2010
  3. Description - Booth Personnel Registration Start Date (mm/dd/yyyy)
2. Consequences of change:
  1. If this date is changed to be in the future, exhibitors will not be able to access the page where booth personnel are entered until that date.
  2. If this date is blank, no exhibitors will be able to access the Booth Personnel registration page.
Booth Personnel Registration End Date (9)
1. Use – This is the date that the page where Exhibitors can enter their booth personnel is automatically deactivated.
  1. Value – Calendar Tool
  2. Default Value – 1/1/2010
  3. Description - Booth Personnel Registration End Date (mm/dd/yyyy)
2. Consequences of change:
  1. If this date is changed to be in the past, exhibitors will not be able to access the page where booth personnel are entered.
Number of complimentary/free exhibitor badges for per 100 sq ft (10)
1. Use – For Booth Personnel Registration, this tells the system how many registrations a company gets for free based on the square footage of their booth space.
  1. Value – Text field, numeric values only
  2. Default Value – 2
  3. Description - Sets the default number of badges an exhibitor may order at no charge for each booth, also called comp badges. Value must be >= 0 and <= Max Badges Per 100 sq ft
2. Consequences of change:
  1. Increasing the value of this field will allow the exhibiting company to add more free badge registrations
  2. Decreasing the value of this field will restrict the exhibiting company to less badges. If badges have already been entered at the higher value, AND the exhibiting company edit the list of badge registrations, then the exhibiting company will receive an error that they have exceeded the limit, and they will have to remove badges to bring their free registrations down to new value or , IF the maximum number of badges is higher than the number of free badges, pay an additional rate per booth [ this pulls from the Booth Personnel Badge item type in Financial Set Up]. To resolve this for ONE company, go to Companies>Company Record>Booths>Badges Column>Edit, check the Override Badge Limit box, and increase the number of complimentary badges to the previous limit.
Maximum number of exhibitor badges for per 100 sq ft (10)
1. Use – For Booth Personnel Badge Registration, this tells the system the maximum number of badges that an exhibitor can have per booth based on the square footage of their booth space. This number must be at least equal to the number of complimentary badges, and higher if exhibitors can purchase additional badge registrations.
  1. Value – Text field, numeric values only
  2. Default Value – 2
  3. Description - Sets the default maximum number of badges that an exhibitor may order for each booth. Value must be >=0 and >= Free Badges Per 100 sq ft
2. Consequences of change:
  1. Increasing the value of this field will allow the exhibiting company to buy more badge registrations.
  2. Decreasing the value of this field will restrict the number of additional badge registrations that this company can purchase. IF the company has already purchased the previous limit of badges, AND the exhibiting company edits their badges, they will receive an error and they will be prompted to remove badge registrations. To resolve this for ONE company, go to Companies>Company Record>Booths>Badges Column>Edit, check the Override Badge Limit box, and increase the maximum number of badges to the previous limit.
Conference Manager Email (8)
1. Use –This email is used as the sender address for all conference related email communications. This email address will also receive the ‘bounce backs’ for these emails. Additionally IF Conference Manager Email is selected in Send Mail on Proposal Submission (#54 below) then when a submitter completes and submits a proposal from callforpapers.aspx on the Event Website, an email will be sent to this email address.
  1. Value – Text field
  2. Default Value – projectmanager@a2zInc.net
  3. Description - This email address is used for all of the communications associated with Conference Module
2. Consequences of change:
  1. If the Conference Manager email address is changed, any conference related emails sent after the change has been saved, will reflect the new email address at the sender. This new email address will now receive any ‘bounce back’ notifications for the conference communications.
  2. If Conference Manager Email is selected in Send Mail on Proposal Submission (#54 below), AND this email address is changed then subsequent proposal submission emails will go to this email address.
Alternate Conference Manager Email (10)
1. Use – If Alternate Conference Manager Email is selected in Send Mail in Proposal Submission (#54 below), then when a submitter completes and submits a proposal on callforpapers.aspx on the Event Website an email notification will be sent to this email address.
  1. Value – Text field
  2. Default Value – projectmanager@a2zInc.net
  3. Description - Email to Alternate Conference Manager is sent to this address
2. Consequences of change:
  1. If this email address is changed AND Alternate Conference Manager Email is selected in Send Mail on Proposal Submission, then subsequent proposals submission emails will go to this email address.
Proposal Submission Start Date (8)
1. Use – This is the date that the proposal submission page on the Event Website (callforpapers.aspx) will be accessible to logged in submitters.
  1. Value – Calendar Tool
  2. Default Value – 1/1/2010
  3. Description - This sets Proposal Submission Start Date
2. Consequences of change:
  1. If the date is changed to a date in the future, submitters will not be able to access the proposal submission page until this future date, and will receive an error like “Proposal Submissions are not open at this time”
  2. If the date is changed to a date that has passed, AND the Proposal Submission End Date is in the future, then submitters will be able to log in, create, edit, and submit proposals.
Proposal Submission End Date (8)
1. Use – This is the last date that the proposal submission page on the Event Website (callforpapers.aspx) will be available to receive submissions. After this date, submitters will receive an error like “Proposal Submissions has ended”
  1. Value – Calendar Tool
  2. Default Value – 1/1/2010
  3. Description - This sets Proposal Submission End Date
2. Consequences of change:
  1. If the date is changed to a date the future, AND the Proposal Submission Start Date is in the past, then submitters would have access to log in, create, edit, and submit proposals.
  2. If the date is changed to a date that has passed, then submitters will receive an error like “Proposal Submission has ended"
Proposal Grading Start Date (8)
1. Use – If Proposal Grading is being utilized on the Event Website (gradeproposallist.aspx) then this date will be when the grading portal will be available to logged in graders.
  1. Value – Calendar Tool
  2. Default Value – 1/1/2010
  3. Description - This sets Proposal Grading Start Date
2. Consequences of change:
  1. If the date is changed to a date in the future, then logged in graders will not be able to access the grading portal (gradeproposallist.aspx) and will receive an error like “Proposal Grading is not open at this time”
  2. If this date is changed to a date that has passed, AND the Proposal Grading End Date is set to a date in the future, then logged in graders will be able to access the grading portal (gradeproposallist.aspx) to view and grade proposals.
Proposal Grading End Date (8)
1. Use – If Proposal Grading is being utilized on the Event Website, then this date is the last date that the grading portal will be open to logged in graders to view and grade proposals. After this date, logged in graders will receive an error like “Proposal Grading is not open at this time”
  1. Value – Calendar Tool
  2. Default Value – 1/1/2010
  3. Description - This sets Proposal Grading End Date
2. Consequences of change:
  1. If the date is changed to a date in the future, then logged in graders will be able to access the grading portal (gradeproposallist.aspx) to view and grade proposals.
  2. If the date is changed to a date that has passed, then logged in graders will receive an error like “Proposal Grading is not open at this time”
Reference required for CFP (8)
1. Use – If this is set to ‘Yes’, then at least one reference person would need to be associated with each presenter on every proposal. If this is set to ‘No’ then the option to add references on the Event Website submission form (callforpapers.aspx) will not appear.
  1. Value – Drop Down List [Yes, No]
  2. Default Value – No
  3. Description - Reference Required for CFP
2. Consequences of change:
  1. If the value is changed from ‘No’ to ‘Yes’, then all proposals submitted after the change would require at least one reference person for each presenter listed in that proposal
  2. If the value is changed from ‘Yes’ to ‘No’, then all proposals submitted after the change would NOT display the option to add a reference for presenters.
Allow Edit After Proposal Submit (8)
1. Use – If this is set to ‘Yes’, then submitters will be able to update proposal information after they have completed and submitted the proposal. If this is set to ‘No’, then submitters will not be able to update proposal information after they have completed and submitted the proposal.
  1. Value – Drop Down List [Yes, No]
  2. Default Value – No
  3. Description - Allow Edit After Proposal is Submitted
2. Consequences of change:
  1. If the value is changed from ‘Yes’ to ‘No’, a submitter who logs in and attempts to edit a completed and submitted proposal will not be able to make any edits.
  2. If the value is changed from ‘No’ to ‘Yes’, a submitter who logs in and attempts to edit a completed and submitted proposal will be able to edit the proposal.
Send mail on Proposal Submission (8)
1. Use – This determines who will receive the email acknowledgement that a proposal has been submitted. Any contact types that are checked will receive the email [template #57]
  1. Value – CheckBox List [Submitter, Conference Manager, Alternate Conference Manager, Alternate Event Manager]
  2. Default Value – Submitter, Alternate Conference Manager, Alternate Event Manager
  3. Description - Send mail on Proposal Submission
2. Consequences of change:
  1. If a contact type is unchecked, for any subsequent proposals completed and submitted, that contact type will not be sent the email.
  2. If a contact type is checked, for any subsequent proposals complete and submitted, that contact type will be sent the email.
Send mail on Speaker Details modification (8)
1. Use – This determines if template #84 will be sent to the speaker when their contact details are updated on the Event Website – this would be done by a speaker or a submitter.
  1. Value – Drop Down Box [Yes, No]
  2. Default Value – Yes
  3. Description - Send mail to Speaker on Speaker Details modification
2. Consequences of change:
  1. If this value is changed from ‘Yes’ to ‘No’, then the Speaker will not get a notification that their details have been updated via the Event Website.
  2. If this value is changed from ‘No’ to ‘Yes’, then any Speakers whose details are updated after the change, on the Event Website, will not receive an email notification.
Allow Edit After Proposal Grade (8)
1. Use – If the value is set to ‘Yes’, then submitters will be able to update a proposals information after a Grader has submitted a grade for it. If the value is ‘No’ then a submitter will not be able to update a proposals information after a Grader has submitted a grade for it.
  1. Value – Drop Down Box [yes, No]
  2. Default Value – No
  3. Description - Allow Edit After Proposal is Graded
2. Consequences of change:
  1. If the value is change from ‘No’ to ‘Yes’ AND the proposal submission end date is in the future, then the submitter will be able to edit the proposal.
  2. If the value is changed from ‘No’ to ‘Yes’ AND the proposal submission end date has passed, then the submitter will get an error like ‘Proposal Submission has ended.”
  3. If the value is changed from ‘Yes’ to ‘No’ and the proposal submission end date is in the future, then the submitter will not be able to edit the proposal.
  4. If the value is changed from ‘Yes’ to ‘No’ and the proposal submission end date has passed, then the submitter will get an error like ‘Proposal Submission has ended’
Sales Office for Exhibitor Floor Plan (10)
1. Use – *This feature is no longer utilized* This triggers the e_floorplan.aspx page to open the e_salesoffice.aspx page for booth sales when an available booth has been selected.
  1. Value – Drop Down List [Disabled, Enabled]
  2. Default Value – Disabled
  3. Description - Enable/Disable Sales Office module for Exhibitor Floor plan
2. Consequences of change:
  1. This feature is no longer utilized. Online Booth Sales are now done with the Online Exhibit Contract module, which utilizes the e_boothsales.aspx functional page.
Create Exhibitor Login in Sales Office (10)
1. Use – This controls whether a company can create a make their own profile/account from the e_login.aspx screen.
  1. Value – Drop Down List [Yes, No]
  2. Default Value – Yes
  3. Description - Enable Create Exhibitor Login on Public Side
2. Consequences of change:
  1. If the current value is ‘Yes’ and you change it to ‘No’, then a company will not be able to access the add new company page (e_addcompany.aspx) page from the exhibitor log in screen (e_login.aspx).
  2. If the current value is ‘No’ and it is changed to ‘Yes’, then a company will be able to access the add new company page (e_addcompany.aspx) page from the exhibitor log in screen (e_login.aspx) and create a new record in the company database table.
Booth Selection Mode in Sales Office(10)
1. Use – This feature is no longer utilized. Allow potential exhibitors to purchase booths multiple times
  1. Value – Drop Down List [Multiple, Single]
  2. Default Value – Multiple
  3. Description - Allow single or multiple booth selection in Sales Office
2. Consequences of change:
  1. If value is changed from Multiple to Single then a potential exhibitor can only buy one booth location online (e_boothsales.aspx), and an existing exhibitor will not be able to buy an additional location online. This will not affect exhibitors that have already purchased additional booth locations, nor will it prevent a GlobalAdmin user from assigning/reserving an additional booth location to an existing exhibitor.
  2. If value is changed from Single to Multiple then an existing exhibitor can buy an addition booth location online (e_boothsales.aspx).
Merge Booth in Sales Office (9)
1. Use – This feature is no longer utilized. This functionality is specified in file configurations.
2. Allow exhibitors reserving/buying a booth online to merge multiple booths into one booth location.
  1. Value – Drop Down List [Yes, No]
  2. Default Value – Yes
  3. Description - Can booths be merged in Sales Office
3. Consequences of change:
  1. If value is changed from Yes to No
  2. If value is changed from No to Yes
Amount for authorizing a credit card in Sales Office (10)
1. Use – This feature is no longer utilized. This functionality is specified in file configurations When credit card payment mode is set to ‘Authorize’ in the Booth Sales XML, e_boothsales.aspx will use this number as the amount that the processor will use to verify that the credit card is active and valid. This process does not charge the card or create a payment.
  1. Value – Text Box
  2. Default Value – 500
  3. Description - This is the amount for which Credit Card will be authorized in Sales Office
2. Consequences of change:
  1. If the default amount is changed, then the next time that a potential exhibitor submits a contract on the e_boothsales.aspx page that has payment type ‘credit card’, the payment processor will authorize the card for the new amount.
Payment Options in Sales Office (10)
1. Use –This feature is no longer utilized. This functionality is specified in file configurations
  1. Value – Check Box list [Credit Card, Check]
  2. Default Value – Both options are checked by default
  3. Description – Please specify the payment Option to be used in Sales Office
2. Consequences of change:
  1. If an option changes from checked to unchecked, then when a potential exhibitor is submitting an online contract, then the option that has been unchecked will not display in the payment method drop down.
Mail/Communication of auto generated emails in Sales Office (10)
1. Use - Determines who receives OnlineBoothReservation email (#47) upon successful completion of Online Booth Reservation of Consultative Exhibit Sales on the public site.
  1. Value – [Exhibitor, Show Manager ]
  2. Default Value – Both Exhibitor and Show Manager selected
  3. Description - Please specify to whom the mails should be sent on transaction completion in Sales Office
2. Consequences of change: If Exhibitor is checked on, Exhibitor receives a copy of the email. If Show Manager is checked on, the address specified in Event Manager Email receives the email. If they are unchecked, the email is no longer sent.
Max Area allowed for reserving in Sales Office (9)
1. Use –This feature is no longer utilized. This functionality is specified in file configurations
  1. Value – 10000
  2. Default Value –
  3. Description - Please specify the maximum area allowed for reserving of Booths in Sales Office
2. Consequences of change:
Login mode for booth selection for Sales Office (10)
1. Use –This feature is no longer utilized.
  1. Value –
  2. Default Value –
  3. Description - Please specify whether single or multiple logins are allowed for Booth Selection in Sales Office
2. Consequences of change:
To Set Google Analytics Tracking ID (10)
1. Use –
  1. Value – UA-107265548-1
  2. Default Value –
  3. Description - To Set Google AnalyticsID
2. Consequences of change: if blanked out or changed, a2z Google Analytics will no longer track the event.
To Set Custom Analytics ID 1 (9)
1. Use – To specify an additional Google Analytics account, such as one belonging to a client. Either Custom Analytics 1 or Custom Analytics 2 can be used, or both if there are two separate Google accounts.
  1. Value – UA-107275078-2
  2. Default Value – [blank]
  3. Description - To Set Custom AnalyticsID1
2. Consequences of change: Adding a Google Analytics UID will cause the public site to be tracked by Google. Removing the UID will make the tracking stop.
To Set Custom Analytics ID 2 (9)
1. Use –To specify an additional Google Analytics account, such as one belonging to a client. Either Custom Analytics 1 or Custom Analytics 2 can be used, or both if there are two separate Google accounts.
  1. Value –
  2. Default Value – [blank]
  3. Description - To Set Custom AnalyticsID2
2. Consequences of change: Adding a Google Analytics UID will cause the public site to be tracked by Google. Removing the UID will make the tracking stop.
Floorplan VX Google Analytics ID (10)
1. Use – For a2z to track analytics on EventMap activities
  1. Value – UA-107265548-1
  2. Default Value –
  3. Description - Floorplan VX Google Analytics ID
2. Consequences of change: if blanked out or changed, a2z Google Analytics will no longer track the eventmap activities.
VX Map Page (10)
1. Use – This feature is no longer utilized.
  1. Value –
  2. Default Value –
  3. Description - VX Map Page Description
2. Consequences of change:
VX Welcome (10)
1. Use – On EventMap, the contents of the pop-up when the Home button is clicked. This should be the standard page approved by the Product team.
  1. Value – URL
  2. Default Value – https://libs.a2zinc.net/resources/EventMap_Home.htm
  3. Description - VX Welcome Page
2. Consequences of change: Removing the URL will result in a broken page error inside the pop-up.
VX Help Page (10)
1. Use – On EventMap, the contents of the pop-up when the Help button is clicked. This should be the standard page approved by the Product team.
  1. Value – URL
  2. Default Value – https://libs.a2zinc.net/resources/EventMapHelp.htm
  3. Description - VX Help Page
2. Consequences of change: Removing the URL will result in a broken page error inside the pop-up.
VX Help Page – SL (10)
1. Use – This feature is no longer utilized.
  1. Value –
  2. Default Value – http://www.a2zinc.net/common/help/slEventMapHelp.htm
  3. Description - VX Help Page - Silverlight
2. Consequences of change:
Time Zone (10)
1. Use – To specify time zone for conference sessions and appointments as they are exported to
  1. Value –
  2. Default Value – -5
  3. Description - The time offset may be expressed as an integer (-5) to indicate days or in time format (-5:00) to indicate hours.
2. Consequences of change: Needs to be changed to -5:00 to reflect Eastern Standard Time, and Central Daylight Time, -6:00 for Central Standard and Mountain Daylight, -7:00 for Mountain Standard and Pacific Daylight, and -8:00 for Pacific Standard.
Default Event to compare in Dashboard (10)
1. Use – This feature is no longer utilized.
  1. Value – EventID
  2. Default Value – 2
  3. Description - If using the (legacy) Weekly Sales and Pacing Report (WSPR), against which other event should this event be compared?
2. Consequences of change:
Target Exhibitors (10)
1. Use – This feature is no longer utilized.
2. Value –
  1. Default Value – 0
  2. Description - If using the (legacy) Weekly Sales and Pacing Report (WSPR), what is the target number of exhibitors for this event?
3. Consequences of change:
Attendee Integration Type (10)
1. Use – Name of attendee integration.
  1. Value – Text field
  2. Default Value – [blank]
  3. Description - Attendee Integration Type
2. Consequences of change: populating the field is necessary to configure an attendee integration. Removing or changing the integration string will result in integration not working.
Attendee Integration URL (10)
1. Use – URL of registration company for attendee integration
  1. Value – Text field (URL)
  2. Default Value – [blank]
  3. Description - Attendee Integration URL
2. Consequences of change: Removing or changing this field will result in attendee integration not working.
Attendee Integration UserName (10)
1. Use – standard login for given attendee integration URL
  1. Value – Text Field
  2. Default Value – [blank]
  3. Description - User Name to access the external API
2. Consequences of change: removing or changing this field will result in integration not working.
Attendee Integration Password (10)
1. Use – Standard password for given attendee integration URL
  1. Value – Text Field
  2. Default Value – [blank]
  3. Description - Password to access the external API
2. Consequences of change: removing or changing this field will result in integration not working.
Attendee Integration Key
1. Use – If used or specified by the specific integration provider, decryption key for the integration.
  1. Value – Text Field
  2. Default Value – [blank]
  3. Description - Event Key used to access the event data from an external API.
2. Consequences of change: removing or changing this field will result in integration not working.
Attendee Integration SummaryEmail (10)
1. Use – Email of Personify resource to confirm attendee integration had run successfully
  1. Value – email address
  2. Default Value – [blank]
  3. Description - This is the email that receives the integration run confirmation
2. Consequences of change: Changes the recepient of confirmation email.
Attendee Integration ForceStartDate (10)
1. Use –
  1. Value –
  2. Default Value –
  3. Description - Will be used for integration scheduling in the future, but not currently active.
2. Consequences of change:
Attendee Integration ForceEndDate (10)
1. Use –
  1. Value –
  2. Default Value –
  3. Description - Will be used for integration scheduling in the future, but not currently active.
2. Consequences of change:
Attendee Integration Filter (10)
1. Use – Specify attendee types to be imported
  1. Value – Text field
  2. Default Value – [blank]
  3. Description -Filter used to filter out registration types if needed.
2. Consequences of change: Attendees of ineligible or undesired types may be imported.
External Event Code (10)
1. Use – passed to identify the event within the integrating system.
  1. Value – text field
  2. Default Value – EVENTCODE
  3. Description -By what event code is this event identified in the integrating system
2. Consequences of change: removing or changing this field will result in integration not working.
Copy Booth Info From Previous Event (10)
1. Use – Specify where booth information copies from for repeat exhibitor.
  1. Value – Yes/No
  2. Default Value – yes
  3. Description - When assigning a booth or confirming a reserved booth, would you like to copy the booth info from the last event (or the same event type)? (Yes/No - Default is Yes)
2. Consequences of change: Assuming Booth Space Application is not in use, if set to Yes, when a booth is assigned, their Booth Info (including product categories) is copied from the most recent previous event's booth info. If set to No, Booth Info copies from Company Info. This also impacts Exhibitor Import.
SSO Encryption Token (10)
1. Use – To share with partner organizations who will use it to decrypt the encrypted CoID to support single sign-on logic from a2z.
  1. Value – a text string
  2. Default Value – a2zInc
  3. Description -Specify SSO encryption token to be shared with 3rd party
2. Consequences of change: new encryption string must be shared with the 3rd party partner. Certain partners may expect standard keys across their events.
Floorplan Top Coordinate (10)
1. Use – Deprecated. Coordinate specified in Map Management now.
  1. Value –
  2. Default Value – 475px
  3. Description -Floorplan Top Coordinate
2. Consequences of change
Floorplan Left Coordinate (10)
1. Use – Deprecated. Coordinate specified in Map Management now.
  1. Value –
  2. Default Value – 200px
  3. Description - Floorplan Left Coordinate
2. Consequences of change
Second Language Collation (10)
1. Use – String that specifies second language file
  1. Value – text
  2. Default Value – [blank]
  3. Description - Specify language collation for this Event.
2. Consequences of change: set to operate second language features. Unsetting or changing the string will lose the language library.
Offer Second Language (10)
1. Use – Enable second language
  1. Value – [Globaladmin,Public Side]
  2. Default Value –
  3. Description -Specify if second language option is to be enable or not.
2. Consequences of change
Currency Locale String for Event (10)
1. Use – To pass the currency string to payment gateway
  1. Value – dropdown
  2. Default Value – English (United States)
  3. Description - Ui Culture String for this event's currency, use a value from the list found use a value from this list (ui-culture column)
2. Consequences of change: Global Admin and Public Site will display financial figures using the specified currency sign and delimiters.
Mobile App EventID (10)
1. Use – Set the EventID of the event in the mobile database when the event is configured to work for mobile app
  1. Value – number
  2. Default Value – blank
  3. Description - What is the Event ID used by the Mobile App?
2. Consequences of change: mobile app will pull incorrect event information.
Revenue split for Add-Ons (10)
1. Use – specify whether event participates in Revenue Acceleration Program
  1. Value – Yes/No
  2. Default Value – No
  3. Description - Is the client using Revenue split for Add-On items? (Yes/No)
2. Consequences of change: Revenue split for online credit card transactions not configured correctly, requiring manual reconciliation after the event.
a2z Verisign Comment 1 (10)
1. Use – Passing additional data to payment gateway. The text in this comment will be passed along with company ID in parentheses.
  1. Value – text
  2. Default Value – [blank]
  3. Description - This data is logged into a2z Verisign Log as VerisignComment1(CompanyID)
2. Consequences of change: Comment may appear in PayPal's reports
a2z Verisign Comment 2 (10)
1. Use – Passing additional data to payment gateway.
  1. Value – text
  2. Default Value – [blank]
  3. Description - a2z Verisign Comment2
2. Consequences of change: Comment may appear in PayPal's reports
Featured Exhibitor Count (10)
1. Use – for events participating in Revenue Acceleration Program, number of exhibitors featured at the top of the exhibitor list.
  1. Value – number
  2. Default Value – 0
  3. Description -Set Featured Exhibitor Count display at Public Site
2. Consequences of change: to be configured by a2z team per Revenue Acceleration Program agreement.
Show submitter name in Proposal Grading (10)
1. Use – in Call for Proposals Grading, is the name of the Submitter visible to the Reviewer?
  1. Value – Yes/No
  2. Default Value – Yes
  3. Description -Show submitter name in Proposal Grading
2. Consequences of change: Show or hide the name of the proposal submitter within the grading process.
Default to Next Gen Floorplan (10)* - this feature can only be accessed by A2Z Events team member
1. Use – Toggle floorplan in GlobalAdmin Floorplan Management between Classic and NextGen
  1. Value – Yes/No
  2. Default Value – Yes
  3. Description - Would you like to default to using Next Gen Floorplan Management in Global Admin?
2. Consequences of change: Switch floorplan management between NextGen and Classic user interfaces
Enable Universal Search UI (10)
1. Use – Add or remove a control for searching Exhibitors, Sessions and Products on the public site (in the Menu area of the page.)
  1. Value – Yes/No
  2. Default Value – No
  3. Description - Enable/Disable Universal Search UI elements i.e. search input, search results page
2. Consequences of change: Enable or disable the search interface on the public site

Feature Configuration

Feature Configuration should only be configured by TSC per the IM's direction in the System/Event Creation issue unless special considerations are discussed with them.

View and Edit Events - always auto checked
Event Configuration - always auto checked
User Permissions - always auto checked
Floor Plan Management - enabled for Core, Plus and Pro
Expo Management - enabled for Core, Plus and Pro
Conference Management - enabled for CMM or Mobile
Call For Papers - enabled for CFP
Application Management - enabled by the BSC if the application version of the OEC will be used by the client and no other version of OEC will be used.
EDC Management - enabled if the client will need the EDC tile in the exhibitor console
Priority Point Management - enabled if the client is Pro or has Enhanced Configuration and will use priority point calculation logic
Move-In/Out Management - enabled for Core, Plus and Pro
Floor Plan Import Wizard - enabled for Core, Plus and Pro
Matchmaking - enabled with Connect
Special Opportunity - NA
Contact Management - enabled for Plus and Pro
Financial Export - enabled for clients who need payment method GL codes, will have orders/payments locked down each not and are syncing financials via BI reports or custom reports to their financial software
Custom Fields - enabled for CMM, CFP, Pro or Enhanced Configuration
UDC Management - enabled for Core, Plus and Pro
Online Sponsorship Sales - enabled for Pro or the OSS add-on
Mobile App - enabled for Mobile
Financial Management - enabled for Plus and Pro
Design and Content Management - enabled for all products
Exhibitor Booth Personnel - enabled if the client will need the Booth Personnel tile in the exhibitor console or if they want the system to do badge allotment calculations
Online Exhibit Contract - enabled for Plus and Pro
Enhanced eBooth Management - enabled for EDC Buyout or EDC Sales
Custom Forms - enabled for Pro or Enhanced Configuration
AAW - NA
Hosted Buyer Program - enabled for Hosted Buyer
PeerConnect - NA
Attendee Engagement - NA
Premium Digital Packages - NA

Articles in this section

Event Configuration

Feature Configuration

Related articles