Patch 22.5.1 - Module: Vendor/Client Collaboration Gateway

Optional Add-On Module used to extend the functionality and collaboration scope of Contract Insight by providing a dedicated gateway portal for your vendors, suppliers, providers, clients, customers, respondents, etc. to view and interact with the contracts, solicitations, etc. you have with them.

VENDOR/CLIENT COLLABORATION GATEWAY
ENHANCEMENTS

ENHANCEMENT:  Dynamic Translation of Field Groups and Field Names
Reference #: 250804.1203.15760

Translations on the Vendor/Client Gateway have been enhanced to include translation of Field Groups and Field Names. The preferred language can be selected by clicking the globe icon in the header or by setting the Customer Contact's Regional Setting value.

How will this affect users?
Users of the Vendor/Client Gateway will now see Field Groups and Field Names translated when choosing a preferred language.

ENHANCEMENT: Updated Secure Email Page Design
Reference #: 250804.1203.16469

The design of the Secure Email page has been updated to match the design changes throughout the Vendor/Client Gateway.

How will this affect users?
Users of the Vendor/Client Gateway will see and updated design for Secure Email

VENDOR/CLIENT COLLABORATION GATEWAY
RESOLUTIONS

RESOLUTION:  Unable to create Request from Contract
Reference #: 250804.1203.15545

Users were previously unable to submit Requests directly from the Vendor Collaboration Gateway (VCG). This fix enables seamless Request creation from within the VCG interface, improving usability and contract management workflows.

RESOLUTION:  Sign In field order flipped
Reference #: 250804.1288.15548

On the Vendor/Client Gateway (VCG) Welcome page, the Company ID field was incorrectly appearing before the Password field, disrupting the expected login flow. The field order on the VCG Welcome page has been corrected to follow the intended sequence:

• Username
• Password
• Company ID

RESOLUTION:  Long titles on dropdowns causes overlapping
Reference #: 250804.1203.15553

Dropdown fields with long field names were overlapping the values for the field. This has been resolved by truncating the name of long fields and showing the full name in the tooltip.

RESOLUTION:  All surveys show on E-Sourcing records
Reference #: 250804.1203.15554

All surveys were displaying on the E-Sourcing records whether it was assigned to the specific record or not. This has been fixed so that only the appropriately assigned surveys show as expected.

RESOLUTION: Horizontal scroll aligned right
Reference #: 250804.1203.15615

When the Vertical Scroll position in the Core system is set to left, the horizontal scroll for grids on the Vendor/Client Gateway are starting aligned/scrolled to the right. This has been adjusted so the grid is aligned left as expected.

RESOLUTION:  Internal files appearing on a the Contract Search grid
Reference #: 250804.1203.15633

Files/Attachments on a Contract that were marked as an Internal file type in the Core system were showing on the Contract Search grid on the Vendor/Client Gateway. This has been resolved so only files with a type of Gateway or Public are available on the Vendor/Client Gateway as expected.

RESOLUTION:  Contract and E-Sourcing grids defaulting to show Public records for logged in users
Reference #: 250804.1203.15827

After logging in and going to either Contracts or E-Sourcing, users were directed to the list of public records for the specified area. This has been updated to initially direct a logged in user to the My Contracts or My E-Sourcing list.

RESOLUTION:  VCG Note and Rich Text control overlaps input
Reference #: 250804.1203.15829

The Note and Rich Text field formatting section of the field was overlapping the data input area, making it difficult to read the first line of entered text. This has been adjusted to allow for additional space between the field formatting section and data input area of the field.

RESOLUTION:  Submit Request only showing public Request Type option
Reference #: 250804.1203.15882

Users logged into the Vendor/Client Gateway were only presented with public Request Types when clicking on the Submit Request button. This has been fixed so the configured Request Types for logged in users appear.