Summary of Vendor Portal event and publication setup

The table in this section provides a summary of workflow event handler and publication setup for event notifications. It also shows how messages are triggered and to whom they are sent.

For multi-site implementations, setup is required in all sites.

For more information, see back office online help topics, including "About Publications, Categories, Subscribers, and Key Values" and "About Workflow Event Handlers."

For notification of: Setup tasks/triggers Messages are sent to: Rich-HTML email is available
New item price requests from back office users Activate workflow event handler:

Alert on Item Price Request Creation

Subscribe portal users to publication:

ItemPriceRequestAlert

Triggered:

When a back office user creates an item price request for a vendor on the Item Price Requests form.

 Portal users* Yes
Item price request closed by back office users Activate workflow event handler:

N/A†

Uses item_price_request_mstIup.

Subscribe portal users to publication:

ItemPriceRequestAlert

Triggered:

When a back office user changes the status of an item price request to Closed on the Item Price Requests form.

Portal users* Yes
New item price responses from portal users Activate workflow event handler:

Alert on Item Price Response Creation

Subscribe back office users to publication:

ItemPriceResponseAlert

Triggered:

When a Vendor Portal user submits an item price response on the Item Price Requests page.

 Back office users No
Acceptance of item price responses by back office users Activate workflow event handler:

Alert when Price Response is Accepted

Subscribe portal users to publication:

ItemPriceResponseAcceptedAlert

Triggered:

When a back office user sets an item price response status to Accepted or copies an item price response to a purchase order or PO requisition. These actions are completed on or from the Item Price Requests form.

 Portal users* Yes
Purchase orders created from an accepted item price response in the back office Activate workflow event handler:

N/A†

Uses CreatePoAndOrPoitemRowSp.

Subscribe portal users to publication:

ItemPriceRequestAlert

Triggered:

When a back office user copies an item price response to a purchase order. This action is completed from the Item Price Requests form.

 Portal users* Yes
Purchase order requisitions created from an accepted item price response in the back office Activate workflow event handler:

N/A†

Uses UpdatePOReqLineSp.

Subscribe portal users to publication:

ItemPriceRequestAlert

Triggered:

When a back office user copies an item price response to a PO requisition. This action is completed from the Item Price Requests form.

 Portal users* Yes
Interactions from back office users to portal users Activate workflow event handler:

Alert V Portal Users of New Interaction

Subscribe portal users to publication:

VPCustomerInteractionAlert

Triggered:

When a back office user adds and saves a note on the Vendor Interactions form, Conversations tab, with the Alert Subscriber check box selected.

 Portal users* Yes
Interactions from portal users to back office users Activate workflow event handler:

Alert Back Office Users of V Interaction

Subscribe back office users to publication:

SLVendorInteractionAlert

(For multi-site, users must be subscribed in the site for which they are responsible and in the Primary Site.)

Triggered:

When a Vendor Portal user submits interactions on the Interactions page.

 Back office users No
New vendor documents added in the back office Activate workflow event handler:

Alert Users of a New Vendor Document

Subscribe back office and portal users to publication:

VendorDocumentUploadAlert

Triggered:

When a back office user adds a document on the Attached Documents form.

Back office and portal users* Yes
New vendor documents added on the portal Activate workflow event handler:

Alert Users of a New V-Portal Document

Subscribe back office users to publication:

VendorDocumentUploadAlert

Triggered:

When a Vendor Portal user adds a document on the Documents page.

 Back office users No
Address change requests from the portal Activate workflow event handler:

Approve V Portal Address Change**

Subscribe users to publication:

N/A†

Uses the VendorServiceRepID event global constant.

Uses the Retrieve Modified Property and Label helper event.

Triggered:

When a Vendor Portal user submits an address change on the My Company Profile page. The message prompts for a response.

Back office and portal users Yes
General information change requests from the portal Activate workflow event handler:

Approve V Portal Company General Change**

Subscribe users to publication:

N/A†

Uses the VendorServiceRepID event global constant.

Uses the Retrieve Modified Property and Label helper event.

Triggered:

When a Vendor Portal user submits a general information change on the My Company Profile page. The message prompts for a response.

Back office and portal users Yes
Contact change requests from the portal Activate workflow event handler:

Approve V Portal Contact Change**

Subscribe users to publication:

N/A†

Uses the VendorServiceRepID event global constant.

Uses the Retrieve Modified Property and Label helper event.

Triggered:

When a Vendor Portal user submits a contact change on the My Company Profile page. The message prompts for a response.

Back office and portal users Yes
Contract price requests from the portal. Also notifies portal users when their request is received. Activate workflow event handler:

Notify Portal Contract Price Created**

Subscribe user to publication:

N/A†

Uses the PortalVendorContractPriceCreatedManagerID event global constant.

Triggered:

When a Vendor Portal user submits a contract price request on the Product Price Contracts page.

 Back office and portal users Yes, for the message sent to portal users
Approved contract price request for portal users Activate workflow event handler:

N/A†

Uses CLM_ChangeVendorContractPriceStatusSp.

Subscribe user to publication:

N/A†

Triggered:

When a back office user changes the status to Approved for an individual contract price request on the Vendor Contract Prices form. This notification is also triggered for mass approvals when the status is changed using the Change Vendor Contract Price Status Utility form.

Portal users Yes
Rejected (deleted) contract price requests for portal users Activate workflow event handler:

Notify Portal Contract Price Rejected

Subscribe user to publication:

N/A†

Triggered:

When a back office user deletes a record from the Vendor Contract Prices form.

Portal users Yes
Planned orders firmed on the portal Activate workflow event handler:

N/A†

Uses FirmPlnSp.

A background task, PurchaseOrderReportLaser or PORequisitionReport, sends an email message with the printed report to the portal user.

Subscribe user to publication:

N/A†

Uses the PortalPOLineCreatedManagerID or PortalPORequisitionCreatedManagerID event global constant.

Triggered:

When a Vendor Portal user firms a planned order to PO requisition lines or PO lines.

Back office and portal users Yes
Approved or rejected PO requisition lines for portal users Activate workflow event handler:

Notify Portal PO Req Line Appr/Rejection

Subscribe user to publication:

N/A†

Uses ChgPoReqLineStatsp.

Triggered:

When a back office user changes the status to Approved or Disapproved for individual lines on the Purchase Order Requisition Lines form or for a range of lines using the Change PO Requisition Line Status form.

 Portal users Yes
Changes to PO line promise dates on the portal Activate workflow event handler:

Notify V Portal POLine Prom Date Change

Subscribe user to publication:

N/A†

Notification is sent to back office users assigned to the PortalPOLinePromiseDateChanged event global constant. Also notifies portal users when their change request is received.

Triggered:

When a Vendor Portal user submits a change request for a PO line promise date.

 Back office users No
Quantity on hand of a vendor consigned item has been reduced through consumption or return Activate workflow event handler:

N/A†

Uses Event_ConsignmentWhseOnHandUpdateSp.

Subscribe portal users to publication:

VPConsignedInvConsumptionAlert

Triggered:

When a back office user completes any action that causes the vendor’s quantity on hand to be reduced, such as entering an order shipment, a job material transaction, or a miscellaneous issue.

 Portal users* Yes
The quantity of a portal user’s consigned inventory has gone above or below the set limits Activate workflow event handler:

N/A†

Uses Event_ConsignmentWhseOnHandUpdateSp.

Subscribe portal users to publication:

VPConsignedInvLevelAlert

Triggered:

When a back office user completes any action that causes inventory to go above or below the vendor’s limit, such as entering an order shipment, a job material transaction, or a miscellaneous issue.

 Portal users* Yes

* Portal users can subscribe or unsubscribe using a check box on the portal My Profile page.

** These event handlers prompt for a Yes/No response to approve the change. Based on the response, an approval or rejection notification is sent to portal users if Send Email Notification is set and their email address is provided.

† No event handler and/or publication is associated with these events. C# classes, IDO methods, and global constants are used to send messages for some events. Notification is sent to portal users if Send Email Notification is set for them and their email address is provided.