Configure Project Watch
This article explains how administrators set up Project Watch in Baucore Setup → Baucore Agents.
Prerequisites
- Assign the Baucore Admin permission set to administrators who will maintain the configuration.
- Ensure end users who review suggestions have access to the relevant project records, Watchlist objects, and components through the package permission model used in your org.
- Confirm the Watchlist Lightning App is available from the App Launcher.
Open the configuration area
- Open the Watchlist Lightning App.
- Open the Baucore Setup tab.
- In the left navigation, click Baucore Agents.
The Baucore Agents area contains the setup used by Project Watch, including provider connectivity, field mapping, and watchlist preferences.
Step 1 — Confirm provider connectivity
The Inbox-related setup in Baucore Agents is used by the Watchlist integration as well. Verify that:
- The required provider connectivity is configured and the org has the necessary provider credits for watch runs — check the credits display in the Baucore Agents area.
- The handler and provider-related setup is reviewed if your implementation depends on inbound provider processing.
- The provider value used by your watchlist mappings exists and is active.
Step 2 — Configure field mapping
The Field Mapping tab controls how provider fields map to Salesforce fields (see Set Up Baucore Agents Field Mapping for the full walkthrough). These mappings determine which values the watchlist compares, and therefore which suggestions can be generated.
Project Watch resolves its project field mappings from the same provider configuration used by the Baucore Inbox watchlist integration. In this package version, that provider value is baucoreInbox, so the relevant provider mappings must exist and be correct.
Object mapping tabs:
| Sub-tab | Maps provider data to |
|---|---|
| Project | Project fields |
| Main Project | Main Project fields |
| Project Lead | Project Lead fields |
| Role | Participant role values |
| Account | Account fields for company suggestions |
| Account (Lead) | Lead fields for company suggestions saved as Leads |
| Contact | Contact fields for person suggestions |
Mapping behavior flags:
| Setting | Effect |
|---|---|
| Automatic update on empty field | If the target Salesforce field is blank, the value can be auto-applied without manual review. |
| Always overwrite value on update | The provider value always replaces the current Salesforce value. Use this only when the provider is the authoritative source. |
| Notify on Chatter | A consolidated Chatter notification is created when suggestions are generated for the mapped field. |
After modifying, adding, or resetting mappings, always clear Platform Cache. Updated mappings are not picked up reliably until the cache is cleared.
Step 3 — Configure Watchlist preferences
The Baucore Watchlist preferences screen stores per-user defaults and exposes scheduler controls.
| Setting | Description |
|---|---|
| Project research frequency | Controls how often a watched project becomes eligible for a new research run. Values: Daily, Weekly, Biweekly, Monthly. |
| Automatic update on field if empty | Allows empty Salesforce fields to be filled automatically when supported by the watchlist logic. |
| Notify on Chatter for possible projects | Controls Chatter notifications for possible-project suggestions. |
| Scheduler Active | Turns the shared org-level Watchlist scheduler on or off. |
Scheduler Active controls a shared scheduled job for the whole org — it is not limited to the current user.
Step 4 — Understand the two timings
Project research frequency controls when new watch runs are created for watched records. Result delivery and notification behavior can additionally depend on internal digest processing settings used by the package runtime. When troubleshooting, keep these two timings separate — a project may be watched correctly and still appear to update later than expected, because creation of runs and follow-up delivery are distinct steps.
Scratch org developer options
In scratch orgs, the Watchlist preferences page exposes additional testing options:
- Bypass Digest Frequency — for testing follow-up processing without waiting for normal timing rules.
- Run Digest Scheduler — triggers the scheduler immediately.
Step 5 — Verify the setup
- Open a supported Project, Project Lead, or Main Project record.
- Confirm the Project Watch card is visible.
- Click Add to Watchlist on a test record.
- Confirm the card changes to the watched state.
- Check Watch Records and Watch Record Runs for activity.
- After a run completes, verify that suggestions, references, files, or further attributes appear when the provider returns data.
Troubleshooting
| Issue | What to check |
|---|---|
| No suggestions appear | Verify the scheduler is active, the project is watched, and the field mappings exist for the expected provider fields. |
| Mapping changes have no effect | Clear Platform Cache after the change. |
| The watch shows Failed | Review the latest Watch Record Run and retry after correcting the underlying issue. |
| Results arrive later than expected | Check both the Project research frequency and the package digest timing behavior. |
| Unexpected auto-applied updates | Review field mapping flags and the user preference for automatic update on empty fields. |