In the Paris release and beyond, the scoped vendor portal (svdp) will be installed by default but can be overridden in which System Property record to use the legacy/traditional vendor portal (vdp)?

The snvdrriskasmt.vendorportalendpoint system property is used to define the URL endpoint for the vendor portal. Since the Paris release, the default value for this property is svdp, which directs users to the modern, scoped Service Portal-based vendor portal. To revert to the legacy, non-scoped portal for backward compatibility, an administrator must override this property and change its value to vdp. This single property controls which of the two portal experiences is presented to vendors.

A. snvdrriskasmt.vendorportal: This is not the correct system property name. The correct property includes endpoint to signify it controls the URL path.
B. snvdrriskasmt.scoped.vendorportalendpoint: This property name is incorrect. The inclusion of .scoped. does not align with the official property used for this purpose.
D. snvdrriskasmt.scoped.vendorportal: This is an invalid property name. It incorrectly includes .scoped. and omits the required endpoint suffix.

1. ServiceNow Product Documentation (Vancouver Release): Vendor Risk Management > Administration > Configure Vendor Risk Management > Vendor portal. The documentation states, "The legacy vendor portal is available for backward compatibility. To use the legacy portal, set the snvdrriskasmt.vendorportalendpoint system property to vdp."

2. ServiceNow Product Documentation (Utah Release): Vendor Risk Management > Reference > Properties installed with Vendor Risk Management. This page lists the property snvdrriskasmt.vendorportalendpoint with the description, "Specifies the vendor portal suffix. The default is svdp." This confirms it is the controlling property.