BNI – BNI Connect
Release Notes 1.7.7/8
• 1.7.8 includes both Phase 2 and 3a Infrastructure Changes.
• Improved Experience in Portal Registration
• Marketo – Chapter Leadership Team fields
• Some additional Bugzilla fixes are also included.
o 2293 – Download My Data/TYFCB Change
o 2295 – Do not allow name change as part of registration
This release includes a combination of updated features and bug fixes.
The new features included in this release include:
• Changes in the Visitor Management area
o Including Bugzilla #2283
• Changes to the Yaadpay fields
• Changes to the LMS File Generation Process
• Addition Bugzilla fixes
o #2336 – Royalty Report Changes
o #2333 – Transmit Royalty Changes
o #2324 – Online Renewal Name Change Flow
o #2299 – Prospective Visitors with null in phone number fields
o #2332 – Mobile – API Change to ensure Expired Members that are renewed can login to the app
o #2320 – Invited by when marking Attendance of a PV sometimes not carried through
o #2338 – Translation for Phone Number on Event Calendar in CMS
UPDATED FEATURES IN THIS BUILD (1.7.7)
Extensive changes have been made in this area to address feedback from the support team. Full details can be found in the “1.7.7 Visitor Area Changes” specification.
Allowing a member to register themselves as a Prospective Visitor to any chapter in the world (Bugzilla#2283)
When a member accesses the ‘Add Prospective Visitor’ modal, via CMS or via Core, the same modal we have today will pop up.
When accessed via BNIConnect, it will continue to do what it does today i.e. pre-populate with the orgs that the user has access to and default to the orgs set in the org filter in the navigation bar that were selected on access to the screen.
When accessed via CMS, it will pre-populate with the orgs of the chapter they selected to visit on the website.
However, the form will now provide the ability to change the Country, Region or Chapter to any other Country, Region or Chapter in the world, regardless of RBAC. When they do that i.e. select an org that they do not have an active role in, the PII fields will be pre-filled with their own info and will be set to read only.
This will mean that a member can register other people as a Prospective Visitor to their own chapter, however they can register themselves as a Prospective Visitor to any Chapter in the world.
If a member/user holds multiple roles, they will be able to add other people as Prospective Visitors to the orgs they have roles in and register themselves as a Prospective Visitor to any other chapter in world.
When adding/editing a visitor, the PII fields will not be editable if there is an existing individual with any status of membership
When a member accesses the ‘Add or Edit Visitor’ modal, via any route, the same flow that we have today will be followed.
The user will first be prompted to search via email address and if not found with that, then search on name. If an existing individual is selected to add the visit to, then the form will be pre-populated with the PII information of the existing individual.
An additional check will be added, and if the individual associated with that email has had any form of membership past /present (meaning if there is at least one membership record (of any status) associated with that individual record) then the PII information will not be editable. All other fields, except the following, will be read only:
1. Chapter drop down – this will remain selectable based on the users RBAC
2. Visit date will be editable
3. Invited by will be selectable/searchable as it is today
4. Categories will be editable as they are today
Notes field will be editable as they are today.
Additionally, under these circumstances, a help text will be displayed right at the top of the modal to say "This record has a membership (past/present) hence certain fields cannot be edited on this page. Please contact your region if there are any edits needed to the PII fields"
If there is no past or present membership found, then the modal behaviour will be exactly as it is today, and the above changes will not be reflected on the modal.
The date picker on the Add Visitor form will now only allow a past or current date to be selected. Future dates are not be selectable (the PV flow should be used for this).
A member should not be able to add themselves as a Prospective Visitor of their own chapter
Like the approach taken for Bugzilla 2282, if a member attempts to submit a Prospective Visitor for their own chapter, using their own email address, a message will be displayed stating "You cannot invite yourself to your own chapter"
The following changes have been made to the information sent to Yaadpay:
New fields For all terminals transaction we have added 3 hidden inputs
<input type="hidden" name="UTF8" value="True"> <input type="hidden" name="UTF8out" value="True"> <input type="hidden" name="SendHesh" value="True">
Amended fields The following fields have been amended to change the data sent:
<input type="text" name="ClientName" value="Client Name"> This shows the name of the customer eg Fname + Lname (ie. Display Name) <input type="text" name="ClientLName" value="Company Name"> This shows the Company Name of the Member <input type="text" name="zip" value="000000000"> This shows the Member’s VAT Reference field.
On request, a number of changes have been made to the generation of the LMS File.
BNI/CC – Separate files
The generation of the file is now done by Brand Variant. Two sets of files are generated – one for requested BNI orgs and one of requested CC orgs.
At present, both follow the same logic of including the three specified national roles for all countries, and Executive Directors for all regions. Therefore there is data in both files even though we don’t have any specific CC orgs listed as yet.
Cascading Country Change
The original request for the file was on a region by region basis. However now the rollout has expanded we are in a position where full countries are on board. Therefore the file generation has been changed so that BNI can request:
All relevant region and chapter roles for a WHOLE country
All relevant region and chapter roles for SPECIFIC regions within a country
Only include Active Chapters
A change has been made to the file so that only Active Chapters are included in the Chapter List. Core Groups, Suspended Chapters and Planned Chapters (and the dropped variants of each) will not be included.
UPDATED FEATURES IN THIS BUILD (1.7.8)
Separate MySQL into a new VM (Move to Maria db)
Separate Mongo into a new VM (Upgrade mongo)
NB: Migration to SES has been postponed due to a significant change in scope
Introduce multiple nodes docker swarm cluster that will run all existing API microservices
Improved Experience in Portal Registration
Previously in the Portal during Registration process, the Next button would not be enabled until all mandatory fields had been completed. However due the nature of the screen, it was not always clear which fields were pending.
A change has been made so that the Next button is now available, and if selected, it will highlight which fields are not yet completed that are required. Focus will also be taken to the first missed field.
Chapter Leadership Details are now transferred to Marketo as part of the Chapter export.
These include the first name, last name and email fields for the following roles:
BUG FIXES DELIVERED IN THIS BUILD (1.7.7)
1 – 2336 - HQ Royalty Report - December only - not picking up correct year for exchange rate
2 – 2333 - Transmit royalty - applying late charge from incorrect date
3 – 2332 - Mobile - Expired members, if active again, can't log in to App
4 – 2324 - Online renewal updating Company Name AND Member Name with no approval/confirmation by Regional office
5 – 2299 - PV record - phone number can be set to Null in error
6 – 2283 - Visitor - GDPR changes mean members can no longer register to visit any other chapter
7 – 2320 – Invited By is submitted as null when PV is converted to V
8 – 2338 – Translation of Phone Number field level in Event Detail page
BUG FIXES DELIVERED IN THIS BUILD (1.7.8)
1 - 2293 – Download My Data/TYFCB Change
2 - 2295 – Do not allow name change as part of registration
Operations > Chapter > Visitor Registration: You cannot invite yourself to your own chapter
Operations > Region > Manage Visitors > Edit Visitor: This record has a membership(past/present) hence certain fields cannot be edited on this page. Please contact your region if there are any edits needed to the PII fields
Operations > Region > Manage Visitors > Add Visitor: This record has a membership(past/present) hence certain fields cannot be edited on this page. Please contact your region if there are any edits needed to the PII fields
Operations > Region > Manage Visitors > Add Visitor: You do not have permission to manage this individual.
Tools > Events > View event details > Phone No: