Recommendation Configuration
Referenceadmin
Processor Recommendation and Dealer Recommendation run on the same underlying engine — one flow template, one recommendation object, one email-merge mechanism — configured twice with different app-setting prefixes (PRec_* for Processor, DRec_* for Dealer). This page covers the shared configuration surface: flow parameters, the fields available on a Recommendation, and email templates.
Parameters for the recommendation flow
Both flows read their map and candidate-account settings from Baucore Setup → Recommendations at runtime (via AppSettings_LoadSettings_API):
| Key (Processor / Dealer) | Purpose |
|---|---|
PRec_AC / DRec_AC | Additional SOQL filter condition appended to the candidate-account query (e.g. Type = 'Dealer' AND Active__c = true) |
PRec_MR / DRec_MR | Map search radius, in km |
PRec_PMC / DRec_PMC | Primary map-marker colour (hex) |
PRec_PMF / DRec_PMF | Marker formatting class |
PRec_PML / DRec_PML | Marker label field |
PRec_PMLC / DRec_PMLC | Marker label colour |
Bet_Rolle | Default Participant role assigned when a recommended Account isn’t yet a Participant |
Flow_Name_Contractor_Recommendation | Overrides which flow launches — point this at a cloned/customised flow instead of the standard Recommendation flow |
Recommendation fields (Empfehlung__c)
The header record for one recommendation event — one per email sent:
| Field | Purpose |
|---|---|
| Project / Project Lead | Which record the recommendation was made on |
| Contact | The recipient of the recommendation email |
| Subject / Email Message | The subject and the rendered body, stored after sending |
| CC / BCC | Optional CC/BCC contact on the email |
| Sent | true once the email has actually gone out |
Recommendation Participant fields (Empfehlung_Beteiligte__c)
One record per recommended Account on a given Recommendation — the junction between the Recommendation and each company being introduced:
| Field | Purpose |
|---|---|
| Participant | The recommended Account’s Participant record on the project |
| Information | Free-text note about this recommended party, shown in the email if referenced |
| Account Name / Billing Address / Contact Email / Contact Name / Contact Phone | Formula fields resolved from the Participant, available as merge tokens |
| Project Name / Stage / City / Country / Street / Zip Code | Formula fields resolved from the parent Project, also available as merge tokens |
Setting up email templates
- Create or identify a Salesforce Email Template Folder containing HTML templates for the recommendation email.
- Set
Email_Tmpl_Foldin Baucore Setup to that folder’s Id — both Processor and Dealer Recommendation read from the same setting unless you configure separate folders. - In the template body, use square-bracket merge tokens rather than standard Salesforce curly braces:
[!Contact.FieldName],[!ibsbaucore__Empfehlung__c.FieldName],[!ibsbaucore__Bauobjekt__c.FieldName], or[!User.FieldName]. The recommendation email composer converts these into live values (and safely displays the literal token text in the LWC editor beforehand). - The template picker in the recommendation email screen (
vaRecommendation_Email) lists every template found in the configured folder.