Exercise 4: Deploy to Your Salesforce Org

In this exercise, you'll deploy the Partner Command Center so it can run from your Salesforce org instead of only in Live Preview.

Step 1: Review What Will Deploy

1. Use this prompt to ask Vibes to review the app before deployment:

   Review the Partner Command Center project and summarize what needs to be deployed to my Salesforce org.
   
   Include:
   - The Multi-Framework React app files
   - Any Salesforce metadata or configuration needed for the app to run
   - A permission set that grants access to the deployed app
   - The command to assign that permission set to my user
   - The deployment command you recommend
   
   Do not deploy yet.

2. Review the response and confirm that Vibes is deploying the completed Partner Command Center app.

3. If anything looks unrelated, ask Vibes to narrow the deployment to the React app and required Salesforce metadata only.

Step 2: Deploy the App

1. Use this prompt to deploy the app:

   Deploy the Partner Command Center app to my Salesforce org.
   
   Use the deployment path for Salesforce Multi-Framework React apps in this project.
   
   Run the required build and deploy commands.
   
   If deployment fails, diagnose the error, make the smallest needed fix, and redeploy.

2. Approve the commands Vibes needs to run.

3. Wait for deployment to complete.

4. If Vibes reports an error, let it explain the cause before you approve a fix.

Step 3: Create App Access Metadata

1. Use this prompt to create and deploy the Salesforce metadata required to expose the app:

   Review the Partner Command Center project and create the Salesforce metadata required to expose this Multi-Framework React UI Bundle in the App Launcher.
   
   Specifically:
   - Create or update the CustomApplication metadata for the UI Bundle.
   - Associate it using the uiBundle field.
   - Create a matching permission set for end users.
   - Include app visibility plus only the object, field, Apex, and tab access actually required by the app.
   - Deploy both to my org.
   - Assign the permission set to my current user.
   
   Do not just create a permission set by itself. Include the required Custom Application and permission set flow for internal UI Bundle apps.

2. Confirm that Vibes reports the Custom Application deployment and permission set assignment succeeded.

Step 4: Open and Test the Deployed App

1. Click the Open Default Org in Browser button in the status bar.

2. Open the App Launcher.

3. Search for Partner Command Center, then select the app.

4. Confirm that the app loads with Salesforce partner data.

5. Test the main workflow:

   • Filter, search, sort, and paginate partners.
   • Open the partner detail modal.
   • Review Opportunities and recommended actions.
   • Create a follow-up Task.

Step 5: Ask Vibes to Fix Deployment or Runtime Issues

1. If something does not work in the deployed app, paste the error or describe what you see.

2. Use this prompt:

   The deployed Partner Command Center app has this issue:
   
   [Paste the error message or describe the behavior.]
   
   Diagnose the likely cause, explain the smallest safe fix, update the project, and redeploy.

3. Retest the deployed app after the fix.

Summary

• You reviewed the deployment scope before deploying.
• You deployed the Partner Command Center app to Salesforce.
• You created and assigned a permission set for the app.
• You opened and tested the app in your org.
• You used Vibes to diagnose and fix deployment or runtime issues.

You now have a deployed Salesforce Multi-Framework React app that supports partner analysis and follow-up workflow.