paulh
/
salesforce-appraiser-review-letter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
salesforce-appraiser-review.../docs/SALESFORCE_SETUP.md

2.4 KiB
Raw Blame History

Salesforce Setup — Appraiser Case + DocuSign CLM

What was added

Custom object: Appraiser_Case__c

  • Auto-number name field labeled Appraiser Case Number
  • Appraiser_Field_Review_Date__c (Date)
  • Property_Street__c (Text 255)
  • Property_City__c (Text 80)
  • Property_State_Province__c (Text 80)
  • Property_Postal_Code__c (Text 20)
  • Property_Country__c (Text 80)

Child custom object: Appraiser_Deficiency__c

  • Master-detail to Appraiser_Case__c
  • Deficiency_Number__c (Text 50)
  • Description__c (Long Text Area)
  • Resolution__c (Long Text Area)
  • Sort_Order__c (Number)

Layouts

  • Basic page layout for Appraiser Case
  • Basic page layout for Appraiser Deficiency
  • Related list on Appraiser Case for deficiencies
  • Basic list view on Appraiser Case

Tabs and permissions

  • Custom tabs for both objects
  • Permission set: Appraiser_Case_Admin

Apex

  • AppraiserCaseDocGenService.cls
  • AppraiserCaseDocGenServiceTest.cls

Sample data

  • Anonymous Apex script: scripts/apex/createSampleAppraiserCase.apex

Deploy

From the project root:

sf project deploy start --source-dir force-app

Or from elsewhere:

sf project deploy start --source-dir /home/paulh/.openclaw/workspace/projects/salesforce-appraiser-review-letter/force-app

Test Apex

sf apex run test --tests AppraiserCaseDocGenServiceTest --result-format human

Load sample data

sf apex run --file scripts/apex/createSampleAppraiserCase.apex

Assign permission set

sf org assign permset --name Appraiser_Case_Admin

Suggested next steps in Salesforce

  1. Deploy metadata.
  2. Assign permission set.
  3. Run the sample Apex script.
  4. Open the Appraiser Case tab and verify the record + related deficiencies.
  5. Validate the JSON payload in debug logs or by running the Apex methods directly.
  6. Wire the DocuSign CLM launch path based on the exact package capability in your org.

About the quick action

A placeholder quick action metadata file was added to mark the launch point, but DocuSign CLM launch mechanics vary by package/org. See docs/NEXT_STEPS_DOCGEN.md for the practical wiring options.

About “page layout” and “default setup”

You said “just do default.” In Salesforce terms that means I created the baseline metadata so records can be created and edited in a normal Lightning UI without custom polish yet.