Connect the client’s system. Datafruit reads it and writes it down.

Documentation for the client’s system that writes itself and stays up to date. Ask it questions, or read it like a wiki, with every part linked back to where it lives in the system.

Book a demo

fairbanks.my.salesforce.com6,533 components

objects/AccountCustomer_Tier__cIs_Key_Account__cBroker__cNet_Terms__cLegacy_ID__cDSD_Flag__cOpportunityCommission_Rate__cDiscount_Approved__cRebate_Pct__cPromo_Group__cFiscal_Week__cShip_Window__cPlant_Code__cRoute_Code__cContactRenewal_Date__cLeadRegion_MatchQuote__cDiscount_CapSBQQ__Quote__cSBQQ__QuoteLine__cPlant__cShipment__cPallet_Count__cTerritory__cclasses/QuoteBuilder.clsQuoteBuilderExt.clsQuoteBuilderExtTest.clsQuoteRollup.clsOppCommissionTrigger.clsOppStageSync.clsRebateCalc.clsRebateCalcTest.clsPromoLoader.clsOrderSyncBatch.clsPlantLookupService.clsTerritoryRealign.clsCreateInvoice.clsProductShorting.clstriggers/OpportunityTrigger.triggerAccountTrigger.triggerQuoteLineTrigger.triggerpermissionsets/Sales_Account_ManagementCommission_ApprovalPlant_Ops_ReadBroker_PortalFinance_RebatesTrade_Promo_AdminRoute_Plannerprofiles/System_AdministratorSales_RepBroker_Communityflows/Opp_Close_Date_RequiredAccount_Tier_LockedOrder_Ship_Window_ValidPromo_ApprovalRebate_Accrualworkflows/Opportunity.workflowContract.workflowQuote__c.workflowlayouts/Opportunity-Sales LayoutAccount-Key Account Layoutreports/Pipeline_by_RegionRebates_Q3Broker_Commissions

fairbanks-salesforce

Overview

Fairbanks Foods’ production org. 312 objects, 118 of them custom. 4,860 fields, 3,102 of them custom. Opportunity412 fields and Account268 fields carry most of it. SBQQ is installed, but quoting still runs through a Visualforce page, QuoteBuilder3,914 lines, that predates the current team.

Security is the weak point. 14 users hold System_Administrator, 96 custom permission sets exist and most are assigned to one user each, and 41 Apex classes read or write records without checking what the running user may see.

See Data model for the objects and record types, Code for the Visualforce and Apex, and Security and access for what to change first.

Triggers

Several objects have more than one. One per object is the convention.

Object	Active triggers
Opportunity	4
Account	3
SBQQ__QuoteLine__c	3
Contact	2

Automation

61 flows, 38 active. 17 workflow rules still run, most of them on Opportunity, and are on Salesforce’s retirement path.

https://fairbanks.my.salesforce.comNext: link the metadata repo

Link the metadata repo

fairbanks-websitemain
fairbanks-salesforcemain
fairbanks-data-scriptsdevelop

BackConnect

Connect the client’s system

Paste any URL from it and link the metadata repo.

which triggers fire on Opportunity?

Four, all active: OpportunityTrigger, OppCommissionTrigger, OppStageSync, and QuoteRollup. The middle two both write Amount.

Ask the agent about it

Answers name the exact components, so you can check them.

Update a validation rule

Turn the consent rule back on. It was switched off outside Datafruit on Sep 11.

ApproveDecline

Let it make the change

Each change is explained before it runs, and nothing runs until you approve it.

The system, written up

One page per part of the business, read straight from the client’s system. The discovery you would do on day one, and the as-built you owe at go-live.

fairbanks-sapRead 1d ago

Overview
Orders
Pricing
Deliveries
Billing
Access

Orders

A sales order is a VBAK header with VBAP items, created through VA01 or by the EDI inbound on IDOC_INPUT_ORDERS. Order type ZOR is the standard order; ZRUSH skips the credit check.

ZSD_ORDER_CHECK runs on save through USEREXIT_SAVE_DOCUMENT_PREPARE and blocks any order whose plant is on ZPLANT_HOLD.

Access

23 users hold SAP_ALL. Order desk users are on Z_SD_ORDER_DESK, and plant managers see their own plant through Z_PP_PLANT_MGR with WERKS restricted in the authorization.

212 custom roles exist, and 140 of them are assigned to one user. 9 RFC users have dialog access, among them RFC_NETSUITE and RFC_EDI.

Pricing

Prices come from the procedure ZVAA01. PR00 is the list price from A305, ZK07 the customer discount, and ZREB the rebate accrual that ZSD_REBATE_CALC settles each month.

Discounts over 15% route to ZSD_DISCOUNT_APPROVAL before the order is released.

A health scan of the whole system

Security, code, automation, and data model, each scored, with every problem listed and counted. Bring it to the first call instead of spending a week finding it yourself.

Fairbanks Foods/Health scan

Health scan

54Security

71Code

82Automation

88Data model

Apex classes without sharing41
Users on System_Administrator14
Classes 9+ API versions behind96
Active workflow rules17
Custom fields with no description412

What changes, and what it touches

When someone changes the system underneath you, you hear about it in Slack, by name, and the page that mentions it is revised.

DatafruitAgent9:14 AM

Heads up on fairbanks-salesforce: someone turned off Consent_Signed_Before_Activation in Setup this morning, while the Contracts work is in progress. Contracts can activate without a signed consent until it is back on.

The Contracts page is revised to match. Reply in this thread if you want me to turn the rule back on.

2 repliesLast reply 12 minutes ago

Ask it where things stand

The agent answers from the client’s system, the plan, and your meetings, and shows you where each part of the answer came from.

where are we on quoting?

Two of the three pieces are built. Discount_Approval_L3 and QuoteBuilder are in production and match the plan. The approval email is still open: Fairbanks owns the template, and it was still with them at the last sync.

fairbanks-salesforcePlan, section 4.2Weekly sync

Connects with

See your client’s org written up

Every object, rule, and line of code, written up in pages the whole team can read.