Release Notes Visit 5.12
Visit Status Page
We have implemented a 3rd party monitoring system – Visit Status Page – to provide real-time status information on components of the Visit platform (Register, Create, Connect, Discover, API). You also have the option to subscribe for updates via email, text message, Slack, or Atom/RSS Feeds, so you can be notified each time Visit creates, updates, or resolves an incident.
Visit Create
Organisation Setup
We’ve renamed the SPF Diagnostics tab to Email Domain Status, which now includes SPF, DKIM, and DMARC domain validation.
SPF, or Sender Policy Framework, is an email authentication standard that helps protect senders and recipients from spam, spoofing, and phishing. It defines all the senders that are authenticated to send emails on behalf of your domain. It’s the first step in email authentication. Along with DKIM and DMARC, SPF works to fully protect your domain infrastructure.
DKIM (DomainKeys Identified Mail) is a standard email authentication method that adds a digital signature to outgoing messages. Receiving mail servers that get messages signed with DKIM can verify messages actually came from the sender, and not someone impersonating the sender. DKIM also checks to make sure message contents aren’t changed after the message has been sent.
When receiving servers can verify messages are from you, your messages are less likely to be marked as spam.
With DKIM authentication, you improve the likelihood that legitimate messages are delivered to recipients’ inboxes. Receiving servers can verify messages are actually from your domain, and aren’t forged.
Domain-based Message Authentication, Reporting, and Conformance (DMARC): Lets you tell receiving servers what to do with outgoing messages from your organization that don’t pass SPF or DKIM.
DMARC helps mail administrators prevent hackers and other attackers from spoofing their organization and domain. Spoofing is a type of attack in which the From address of an email message is forged. A spoofed message appears to be from the impersonated organization or domain.
DMARC also lets you request reports from email servers that get messages from your organization or domain. These reports have information to help you identify possible authentication issues and malicious activity for messages sent from your domain.
Improvements
Twitter was renamed to X and branding was updated in both Visit Create and Connect content editors.
JSON API V2
Tax class added to order information
We’ve introduced tax class information to each order item in the V2 JSON API. This simplifies tax reporting by providing direct access to tax classifications, eliminating the need for custom configurations and enabling easier reconciliation and tax breakdown creation.
Visit Engagement tools
Meetings
We’ve implemented a series of enhancements across various Meetings features aimed at improving user experience and expected behavior in the user interface.
Release Notes Visit 5.11
Visit Create
DTCM / Document designer
Physical badge
In order to make a clearer distinction between Visit’s own Visitor QR code and DTCM QR codes, we’ve made the DTCM code in the document editor significantly smaller. This is only valid for newly created documents. For documents created before Release 5.11, there is the option to delete the existing DTCM QR code and add it again to the document.
Digital badge
We have also made adjustments to have a small QR code that enlarges when clicked on for digital badges. However, please note that this isn’t applicable when visitors take a screenshot of their digital badge. In this case, the DTCM QR code logic does not work.
Visit Engagement tools
Sponsor tiers
Sponsors not linked to a tier are now also displayed on the sponsors page in Visit Discover. They are displayed underneath other tiers (if defined).
Product directory
The exhibitor name is now displayed in the Product directory, under each product’s name.