On Friday, August 1, InteSolv released the newest version of its event management portal interface for Adobe Connect users, inteVISTA 3.2. The latest version boasts advanced security features and management for full control of event registration andaccess.
inteVISTA clients were automatically upgraded to version 3.2 on August 1, and can begin using the new features right away. Learning Objects will be available by mid-August. At that time, inteVISTA clients will be notified via email of availability and accessibility of the Learning Objects.
With inteVISTA 3.2 users have many options when setting up event security which include the following new features:
Require Email Address for Event Registration/Access
The email address is what the system will use for the Connect login. This is required by default and cannot be removed.
Validate Email Address
This feature will allow for the validation of the registrant's email address. Once the registrant registers, they will receive an email from the system containing a link and instructions. When the end user clicks the link, they will be directed to the inteVISTA system that will record that the email is valid and registration will continue. The registration is in a "hold" mode until the validation is completed.
Require Password
When opting to use this feature, the system will require that a user enter a valid password for registration. This is their current password in the Connect system. If an invalid password is found, the registration will not continue. Once the end-user has registered they will be required to enter the same password when entering the event. This is now optional. If not selected the person registering will not be required to enter a password at registration or entering the event.
Require PIN
This option will require the participant to enter a PIN when entering the event. There are two options for PIN assignments:
1. Default PIN
The event manager can enter a PIN for participants to enter when attending the event. The PIN that is saved for the event must be distributed by the event manager. There is no automated communication of this PIN to the participant. There is a macro keyword that should be used with the template or adhoc communications.
2. System Generated PIN
The event manager can opt to use a system generated pin which will generate a unique PIN for every participant of the event. The PIN that is generated for the event must be distributed by the event manager. There is no automated communication of this PIN to the participant. There is a macro keyword that should be used with the template or adhoc communications.