Baucore

BauCore V10.12.00 Release Notes

Diese Seite ist noch nicht auf Deutsch verfügbar. Kontaktieren Sie uns unter support@baucore.app, wenn Sie Fragen haben.
Releaseadminuser

Features:

  • Baucore Inbox – Quote Intake & Inbox Overview: Added a Quote Intake flow for creating quotes from emailed attachments with AI-extracted line items, and a new expandable Inbox Overview card (outbound email display, reply modal, cloud-link acknowledgment).
    • CaseSummary/Inquiry records are consolidated into a single review experience; Case and Quote Intake related records are excluded from the Review Updates list so it only shows actionable suggestions.
    • The Review Updates tab opens on pending suggestions when there are any, otherwise on the history view.
  • Watchlist (Project Watch): New “BC - SignalHub” component (add it to Project/Main Project record pages) shows watchlist suggestions for the record across all providers, giving users one place to work through pending project/participant suggestions – sorted so the highest-priority opportunities surface first, with a badge showing which provider (ibau, Teleaktiv, Barbour ABI) each suggestion came from.
    • Duplicate company/person suggestions are now merged and resolved automatically instead of creating separate, conflicting records.
    • The manual sync participant filter (previously ABI-only) is now available for every provider, with dedicated filtering rules for Teleaktiv and Barbour ABI roles.
    • Admins can now mark fields required/editable on the Watch Record Run layout.
  • Quote Editor (QLE v2) – AI Assistant: Added an inline AI assistant to the Project Quote line-item editor that can answer questions and apply group/position changes, with asynchronous analysis of line-item edits and conversation history.
    • Grid usability improvements: free column resizing, clearer error messages for FLS-hidden/inaccessible fields, terminology updates (“position” → “line item”).
  • Opportunity Management V2: New admin setting (off by default) automatically closes a Project to Lost once all of its active Opportunities are Closed Lost, so stale projects no longer need manual cleanup. Existing Closed-Won projects are never affected, and you can limit which Project Phases the automation applies to.
    • New Split Pipeline Amount field on Opportunity shows each Opportunity’s fair share of the project’s total pipeline value, split evenly across all of the project’s active Opportunities – so pipeline reports aren’t inflated by every Opportunity showing the full project amount.
  • App Setup / Admin – One-Click Baucore API Setup: Admins can now provision the Baucore API connection (used by Baucore Inbox and other integrations) directly from App Setup with one click, instead of manually creating it in Setup.
    • The Provision button now disables itself once the connection already exists, preventing accidental duplicate setup, and the setup steps are reordered so admins complete them in the right order.

Bugfixes:

  • Watchlist Chatter & Display: Improved the ibau Watchlist Chatter post to clarify the notification source (ibau vs. Watchlist/Teleaktiv/Barbour ABI), fixed incorrect Project Volume and Project Type display, and dropped the time portion from date fields. Fixed an error when adding the Barbour ABI component to the Main Project page layout.
  • BC SpecifiQ: Fixed the participant role label in the “Select the Customer” screen showing the raw picklist API value instead of the user’s translated language label.
  • New Project Template: Fixed an issue where “Possible Projects” could incorrectly include regular Projects when it should only show Main Projects. Fixed the Project Details field in the New Project form to now be shown based on the user’s field-level access.
  • Page Layouts: Added the Project Details field to the Bauobjekt_Lead__c New Record page layout.

Required Steps for This Release:

If the package upgrade fails with the error below, it means your org has pre-existing metadata components with the same API names as components newly packaged in this release. Complete steps 1 and 2(a–d) below to remove/replace those pre-existing components, then re-run the upgrade. Step 2(e) is a separate follow-up to complete after the upgrade succeeds.

Duplicate Name Details: Can’t upgrade package version. This package version contains metadata components whose API names are identical with pre-existing components in this org. Delete these pre-existing metadata components: Project Quotes (CustomTabDefinition), Inbox Layout (Layout)

  1. Remove the Project Quotes Tab (if present). Go to Setup → Tabs. If the custom “Project Quotes” tab appears as shown below, manually delete it using the Del link next to it.

  2. Replace the Removed “Inbox Layout” Page Layout. The packaged “Inbox Layout” page layout on the Inbox object has been removed from the managed package and must be replaced with your own copy before it can be deleted:

    1. Go to Setup → Object Manager → Inbox → Page Layouts.

    2. Open “Inbox Layout”, then Save → Save As, and save it as a new layout (e.g. “Copy of Inbox Layout”).

    3. Back on the Page Layouts list, use the dropdown next to “Inbox Layout” and choose Delete.

    4. When prompted to replace it, select your new copy (e.g. “Copy of Inbox Layout”) and click Replace.

    5. After upgrading to v10.12.00, the package re-adds its own “Inbox Layout”. Go back to Setup → Object Manager → Inbox → Page Layouts, use the dropdown next to your “Copy of Inbox Layout” and choose Delete  , then replace it with the re-added “Inbox Layout” and click Replace.

  3. Repair Provider Mapping Picklists. After the upgrade, go to App Setup → Troubleshooting and click “Add Missing Picklist Values” to add any picklist values required by the upgrade to the Prov Field Mapping and Prov Picklist Mapping objects. Existing values are never changed, and it is safe to run multiple times.

  4. Add the BC - SignalHub Component to Project Page Layouts. The new BC - SignalHub component is not visible until added to a page. Add it to your Project/Main Project Lightning record pages via Lightning App Builder.

  5. Provision and Register the Baucore API External Client App. The Baucore API connection is provisioned per-org and cannot be packaged. Go to App Setup → Baucore API Connection, click Provision, then follow the on-screen instructions to retrieve the Consumer Key/Secret (identity verification required) and register them on the same screen.

Still need help?

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

Contact support