Baucore

Set Up Submission Process

Taskadmin

The Tender Submission Process — also called the Project Decision process — is how Baucore captures which companies actually won a Project, across three supply-chain roles: Producer, Dealer/Distributor, and Processor/Contractor. Getting this configuration right matters beyond the Project record itself: every Loyalty and Performance indicator, and the entire Supply Chain view, is derived from the submission data captured here.

How a submission is recorded

A Sales Rep marks winners either interactively, using the Project Decision component on the Project record, or by simply setting Marked as winner to true on a Participant record — which triggers the same logic automatically, in the background, with no UI interaction required. See Trigger Project Decision Process without User Interaction.

Once winners are saved:

  • Project Status is set to Closed-Won if a “My Company” Producer won, otherwise Closed-Lost.
  • Every Participant’s Status is set to Won, Won for Competitor, or Lost, based on the project outcome and that Participant’s role — Architects, Planners, and Building Owners automatically get Won/Won for Competitor regardless of whether they were explicitly selected as a winner.
  • Loyalty and Performance indicators recalculate on the involved Accounts.

Add the Project Decision component

  1. Add the Project Decision (participantManagement) component to the Project Lightning Record Page via Lightning App Builder — typically in its own tab or section. See Show Submission Result Component on the Page.
  2. Configure which list-view panels appear (Producer, Dealer, Processor, and any custom panels) by editing Project_Decision_LV_Settings__mdt records — each panel needs a Filter Field (the boolean on Participant that classifies a record into that panel), a Label, a display Order, and a Primary Participant Role (the role assigned when “New” creates a participant from that panel).
  3. Map which Role picklist values count as Competitor, Dealer, and Processor for this org — see Setting Roles in the Submission Process.
  4. Decide which fields appear on Participant and Account records feeding the process — see Participant Fields for Submission Process and Account Fields for Submission Process.
  5. If you need a fully custom panel (e.g. a “Heating Engineer” role group), see Customizing Project Decision component.

Excluding a participant from Project Decision

Set NoProjectDecision__c = true on a Participant record to exclude it from all Project Decision processing — useful for internal or placeholder participants that shouldn’t affect win/loss outcomes.

Still need help?

Our support team is happy to help with anything not covered here.

Contact support