Setup Options for Opportunity Management V2
This page walks through every setting under App Launcher → Baucore Admin → Baucore Setup → Opportunity Management. For the concepts behind what these settings drive, read Key Concepts of Opportunity Management V2 first.
Core settings
Enable Opportunity Management
This is the master setting that activates the entire Opportunity Management functionality.
- Setting: Go to App Launcher → Baucore Admin → Baucore Setup → Opportunity Management.
- Options: V2 – Multiple Opportunities for each Project enables the current version of Opportunity Management, supporting multiple Opportunities per Project with full synchronization.
- Impact: Enables data synchronization between Opportunities and Baucore Projects; activates all automation features described below; required for any of the other settings on this page to take effect.
Any change to the Enable Opportunity Management setting requires a cache reset, done through Baucore Setup → Platform Cache Management. This setting should typically be configured once during initial setup and rarely changed afterward.
Field synchronization settings
Opportunity Sync Settings
Controls which fields from an active Opportunity synchronize to the other related Opportunities on the same Project — a bi-directional sync that keeps data consistent across every Opportunity on a Project.
Project Sync Settings
Controls which fields sync from the Project down to its related Opportunities, so Project data and Opportunity data stay consistent without manual updates.
How to configure: find the Opportunity Sync Settings and Project Sync Settings sections, and toggle synchronization on or off per field.
Available field synchronizations:
- Project Potential — when enabled, changes to the Project’s potential value update the related Opportunities’ Amount.
- Probability — when enabled, the Project’s probability syncs to all related Opportunities.
- Closed on — when enabled, the Project’s end date syncs to the Opportunity’s Close Date. This only works if a field is mapped under Project End Date Field below — if the toggle is on but no field is mapped, nothing syncs.
A field-level sync, once enabled, propagates to every Opportunity on the Project — active and inactive alike.
Close date defaults
Default Days to Close
Determines the default timeframe (in days) used for an Opportunity’s Close Date when no Project end date is available. This default is used in two scenarios:
- There’s no Project End Date field mapping configured.
- The mapped Project End Date field contains a null value.
The system adds this number of days to the current date when setting an Opportunity’s Close Date.
Project-Specific Days to Close
Individual Projects can override the org-wide default with a Project-specific value — when a Project has a value in its own days-to-close field, that value takes precedence over the default above.
Project End Date Field Mapping
A dropdown that lets you select which Project field maps to the Opportunity’s CloseDate field. When a field is selected here and the Closed on toggle is enabled under Project Sync Settings, changes to that Project field automatically update CloseDate on related Opportunities. If no field is selected, or the Closed on toggle is off, no automatic sync happens for Close Date.
Role and phase configuration
Relevant Roles for Project Phases
Determines which participant Roles should be automatically activated for Opportunities in each Project Phase (this is what Key Concepts of Opportunity Management V2 describes as Opportunities going active/inactive as a Project moves through phases).
- Source of values: the available roles are sourced dynamically from the Role global value set — any change there is reflected in the dropdowns throughout this configuration screen.
- How to configure: go to App Launcher → Baucore Admin → Baucore Setup → Opportunity Management, and for each Project Phase, select the roles that should be active. An Opportunity whose Role is selected for a phase is set active when the Project enters that phase.
Project Phase to Opportunity Stage Mapping
Controls how Opportunity Stage automatically progresses when a Project’s Phase changes.
- Source of values: roles are sourced from the Role global value set; stages are sourced from the Opportunity Stage picklist field.
- How to configure: for each Project Phase, select the corresponding Opportunity Stage.
Choose roles for automatic Opportunity creation
Determines which participant Roles trigger automatic creation of an Opportunity when a matching Participant is added to a Project.
- Source of values: sourced from the Role global value set.
- How to configure: go to App Launcher → Baucore Admin → Baucore Setup → Opportunity Management, open Choose roles for which automatic opportunity creation need to be enabled, and select every Role that should trigger auto-creation.
Special Status to Opportunity Stage Settings
Controls how a Participant’s status maps to the Opportunity Stage of its related Opportunity.
- Source of values: stage values are sourced dynamically from the Opportunity Stage picklist field; any change there is reflected in these dropdowns.
- How to configure: go to App Launcher → Baucore Admin → Baucore Setup → Opportunity Management, locate Special Status to Opportunity Stage Settings, and for each status mapping (Closed Won, Indirect Closed Won, Closed Lost, Cancelled) select the appropriate Opportunity Stage.
| Mapping | When it applies | Behavior |
|---|---|---|
| Closed Won | Participant status is Won and the participant has the buyer flag checked | The account gets the job and the product is used; the Opportunity is included in the pipeline. |
| Indirect Closed Won | Participant status is Won but the participant does not have the buyer flag checked | The account gets the job and the product is used, but the Opportunity is excluded from the pipeline — relevant for indirect customers such as architects and building owners. |
| Closed Lost | Participant status is Won for competitor | A decision was made against our product. |
| Cancelled | Participant status is Lost | The account didn’t get the job — another account did. For example, of several bidding Contractors, only one wins; the rest go to Cancelled. |
Related
- Key Concepts of Opportunity Management V2
- Considerations for Opportunity Management
- V2 — Multiple Opportunities for each Project