Install

Security review is not required for a scratch org or a sandbox install. Review is required before an AgentExchange install button works. This repository is not listed yet. The managed package does not run a post-install script.

Prerequisites

• A Salesforce org with Cases.
• Salesforce CLI (sf) on the machine that runs the install.
• Permission to install a managed package and to assign permission sets.
• A Casefork token for this org. The package never ships a live token. You paste the token in the setup wizard.
• An existing queue that can own a Case. Casefork does not create queues. That queue is the review queue.

Install the package

sf package install --package 04ta500000E4aBJAAZ --target-org <alias> --wait 20

Version	Subscriber package id	Type
0.1.0.1	04ta500000E4aBJAAZ	Managed

The managed package namespace is casefork.

Setup wizard

Open the Casefork Setup Wizard, paste the Casefork token, name an existing review queue, then activate Casefork On Case Insert.

1. Install with the command above, or deploy force-app to a scratch org (scripts/scratch-create.sh).
2. Assign permission set Casefork_Admin to yourself. New Casefork fields stay hidden until this permission set is assigned.
3. Assign permission set Casefork_Integration to the Email-to-Case running user or the Default Workflow User.
4. Open the screen flow Casefork Setup Wizard. Paste the Casefork token. Enter queue API names, one per line, and each description as ApiName: description. Leave the confidence floor at 0.80 unless you mean to change it.
5. In the setup wizard, enter the API name of a review queue that already exists and can own a Case. The wizard does not save the name until that queue is found. Casefork does not create queues. If that queue is missing when a Case is routed, the Case keeps its current owner and Casefork_Raw_Json__c records missing_review_queue.

The package ships an External Credential Casefork_Gateway (Custom protocol, Named Principal Casefork_Gateway_Principal) and a Named Credential Casefork_Gateway. The packaged URL is https://casefork-gateway.samudrala153.workers.dev. The secret parameter name is token. The wizard writes that parameter with ConnectApi.NamedCredentials.createCredential into the subscriber secret store. If that call fails, the wizard tells you to set the same parameter in Setup and does not save the token anywhere else.

Apex calls callout:Casefork_Gateway/v1/decide. There is no Remote Site Setting and no Connected App.

Turn the flow on

6. Activate the flow Casefork On Case Insert. It ships inactive.
7. Create one Case with a paragraph in the description. A confident match is owned by the named queue. A low-confidence Case is owned by the review queue you named. The Needs Review list view shows Casefork choices below that org’s confidence floor and does not name a queue.

The admin settings for the floor, feedback, export, and uninstall are in the Admin guide.