About Network Releases
Use the following information to understand the Network Customer Master releases and how to find out about upcoming releases.
- Major - Network produces major releases three times each year. The releases are named for the year and the release number; for example, "21R1" is the first release for 2021. Major releases are deployed to Sandbox and Production PODs two weeks apart from each other.
- Minor - There is one minor release between each major release. It is a "dot" release for the previous major release; for example, "21R1.1". A minor release is deployed to Sandbox and Production PODs two weeks apart from each other.
- Early - Release Notes and Data Governance documents are published two weeks ahead of a release to Sandbox PODs so customers can read about the new features and enhancements.
- Sandbox - Network PODs that contain non-production instances. Used for development, quality assurance (QA), and user acceptance tests (UAT). For more information, see Network instances.
- Production - Network PODs that contain customer production instances.
- Maintenance - These releases typically contain a small number of fixes for issues that are affecting customers. We communicate at least 24 hours prior to the release that we will be applying a change and that there will be a short service disruption. Maintenance releases are synonymous with hotfixes and patches.
|Minor Release||Major Release||Maintenance Release|
|Content||Significant feature enhancements and bug fixes||Significant feature enhancements and bug fixes||Typically small number of fixes for bugs affecting customers|
|Frequency||Every 4 weeks||Every 4 months||Not scheduled|
|Downtime||Up to 3 hours||Up to 3 hours||Up to 3 hours|
|Release Window||1AM – 4AM GMT||1AM – 4AM GMT||1AM – 4AM GMT|
|Communication||1 week in advance||1 week in advance||24hrs in advance|
|Communication Recipients||All subscribed customers||All subscribed customers||All subscribed customers|
|Documentation||Release Notes and Data Governance||Release Notes and Data Governance||Patch Release Notes|
Subscribe to release notifications
To receive release and maintenance notifications, go to trust.veeva.com and subscribe to the Network product. At the top of the page, click Subscribe to Veeva Trust Site.
You can subscribe to Veeva Network or to individual PODs for all scheduled downtime, release announcements, and outage notifications.
For more information, see https://support.veeva.com/hc/en-us/articles/115004142714-How-to-Opt-In-to-System-Availability-Notifications-.
If you have questions or require additional details, contact Veeva Support.
POD stands for “point of delivery”. In simple terms, think of it as the Network application server where your instance is hosted. PODs are located in data centers in the US, Ireland, and Germany (disaster recovery).
|POD||Type||AWS Region||Location||IP Range (Port 443)|
|Production||us-east-2||US - Ohio||184.108.40.206/27|
|Disaster Recovery||us-east-1||US - Virginia||220.127.116.11/27|
|Production||eu-west-1||Europe - Ireland||18.104.22.168/29|
|Disaster Recovery||eu-west-2||Europe - Germany||22.214.171.124/29|
|Sandbox||us-east-2||US - Ohio||126.96.36.199/27|
|Disaster Recovery||eu-west-1||US - Virginia||188.8.131.52/27|
|SANDBOX20||Sandbox||eu-west-1||Europe - Ireland||184.108.40.206/29|
|Disaster Recovery||eu-west-2||Europe - Germany||220.127.116.11/29|
|Login (AUTH)||Production||us-east-1||US - Ohio||18.104.22.168/27|
|Disaster Recovery||us-east-2||US - Virginia||22.214.171.124/27|
Note: Secure File Transfer ProtocolA network protocol used for secure file transfer. Network supports this protocol for accessing folders on your FTP server is used for accessing folders on your FTP server. You must allow the IP ranges for the POD.
Ports for FTPs:
Type=TCP Port Range: 56000 to 56100
Type=TCP Port Range: 21
Ports for SFTP:
Type=TCP Port Range: 56922
Administrators can see the POD information for their Network instance in the General Settings (Settings > General Settings). Using the trust site, trust.veeva.com, you can quickly see if you are impacted by an outage or planned downtime of a POD.
The Network community is live on Veeva Connect!
Veeva Connect is a customer community that you can join to collaborate with Veeva professionals and other customers. Use the platform to discuss industry trends, learn about best practices, and to ask questions.
Joining the community
Create a profile to begin collaborating with other community members.
Note: Use your life sciences company email address to create your account. Personal email domains are not accepted.
After you join, you will be notified by email when new items are posted to the Network Community.
To customize the frequency of your notifications:
In Veeva Connect, click your user profile in the top-right corner.
On the Email Frequency page, expand the list and select one of the options:
Click Save Preferences.
Veeva Network Release Notes .pdf files are published on the Veeva Support website: https://support.veeva.com/hc/en-us/sections/360007932514-Network-Release-Notes
Data Governance .pdf files are also included in each release version link. This document contains data model changes for the release ; for example, new fields and reference value changes.
To be notified when new Release Notes and Data Governance documents are published to this page, click the Follow button.
A What's New button displays when you log into Network at the beginning of each new release. Click the button to learn about the new features and enhancements in the release.
A red badge displays on the button to advise you that there are new features and enhancements to read about. The badge disappears after the button is clicked. When you end your Network session, the What's New button also disappears from the menu bar until the next release.
After the button disappears, to revisit the "What's New" topic, click the Help icon to access the Veeva Network Online Help.
Q. Who receives the release communications?
A. Release communications go to all customers who have subscribed to the Network product on the Veeva Trust Site (trust.veeva.com).
Q. What will happen if a user is logged in at the time the system goes down?
A. The next time the user performs an action that sends a request to the server, the user sees an error. This means unsaved work may be lost, so it is a good idea to save and log off before the release begins.
Q. Can users log in while the system is down?
A. No, log ins are disabled during releases. During a release deployment, PODs are unavailable.
Q. Are customers notified when a release is finished?
A. Yes. Customers who have subscribed to receive notifications on trust.veeva.com will receive an email when the release deployment is complete.
Q: What level of detail will we communicate regarding maintenance releases?
A. Maintenance release communications contain details about the customer-facing issues being resolved in the release.