sfdo-community / ombudsmancloudcare Goto Github PK

Getting error when loading the Dashboard of Zeros - Data. Caused due to Sailors Missing Rank or Email. Looks like report cannot load at all. Maybe due to Command Name change.

Logging this here as an issue because Mary, Shelley, and I think we should do this. We all kinda' hate the app being console at this point, plus have a couple of flexipage layout changes we want to make. If there's going to be an update to the package, it would be good to get these in sooner rather than later.

When running ci_master, on the deploy task, getting the following error:

Update of Report OmbudsmanCloudCare/Sailors_Missing_Rank_or_Email_8i0: Error: filterlanguage: Invalid value specified: 1.

Update of Report OmbudsmanCloudCare/Contacts_wo_Sailor_aRs: Error: filterlanguage: Invalid value specified: 1.

Update of Report OmbudsmanCloudCare/Cases_with_Unknown_Sailor_1Xa: Error: filterlanguage: Invalid value specified: 1.

Update of Report OmbudsmanCloudCare/Cases_Still_on_Unknown_Sailor_VU4: Error: filterlanguage: Invalid value specified: 1.

Update of Report OmbudsmanCloudCare/Cases_Reported_to_Command_oIW: Error: filterlanguage: Invalid value specified: 1.

Update of Dashboard OCCDashboards/mHfJLDlHOhliMWoCsoTRRJarAztLlm: Error: In field: report - no Report named OmbudsmanCloudCare/Contacts_wo_Sailor_aRs found

Appears to be because translation workbench is enabled.

Add a box on the Case lightning record page that is conditionally displayed and shows a warning if the Sailor field is empty.

Goal: To create documentation for optional community build. Rough draft notes offer a starting point:
https://ombudcare.com/sprint-documentation-for-optional-community
User Stories
Customer Journey Map
Sample Rollout Campaign
Global Action: Case Form
Global Action: New Family Form
Configure Guest User
Resources

With three global actions, it gets cumbersome adding in post install. Would be good to include in package or at minimum via MetaDeploy.

When installing the test package getting the following error: (OCC_Account_Record_Page) Your org doesn't have access to component cooper:companyInsightTeaserCard.

Likely due to data.com insights lightning component. Either understand how to turn on for orgs pre install or take off.

There are two account list views dependent on the Household and Organization Account Record Types. When trying to upload, getting an error:
This component depends on another component that is not included in this package - RecordTypeName

@davidmreed can the dependent list views exist in a package?

Also, noticed the contact record types were added as components in the package. Both have a global action and permission set dependencies. Guessing the dependencies need to move to a unmanaged post setting?

(May not technically be an "issue.")
We had discussed that one of the steps of MetaDeploy would be to insert the Placeholder Sailor (see the installation instructions https://docs.google.com/document/d/1e2zoWwjPJv9DVSV4MG8rRX_dv4yxXHdLQWeDcJNNSLE/edit#) so that we wouldn't have to make that a manual step. At the moment, that step is not happening with the installer.

@Nickers3 - The dev org flow is hitting an error in activating record types at the moment. (Error message below.) Looks like it has to do with adding in the automatic namespacing.

020-07-11 08:24:07: Running task: deploy_dev_config
2020-07-11 08:24:07: ------------------------------------------------------------
2020-07-11 08:24:07:
2020-07-11 08:24:07: Options:
2020-07-11 08:24:07: path: unpackaged/config/dev
2020-07-11 08:24:07: Beginning task: Deploy
2020-07-11 08:24:07:
2020-07-11 08:24:07: Cleaning meta.xml files of packageVersion elements for deploy
2020-07-11 08:24:07: Payload size: 1188 bytes
2020-07-11 08:24:07: Pending
2020-07-11 08:24:08: [InProgress]: Processing Type: Profile
2020-07-11 08:24:09: [InProgress]: Processing Type: Profile
2020-07-11 08:24:11: [Done]
2020-07-11 08:24:12: [Failed]: Update of Profile Admin: Error on line 53, col 29: In field: recordType - no RecordType named Contact.%%%NAMESPACE%%%Family_Member found
2020-07-11 08:24:12: Exception in task config_dev.deploy_dev_config

Error: Could not process MDAPI response: Update of Profile Admin: Error on line 53, col 29: In field: recordType - no RecordType named Contact.%%%NAMESPACE%%%Family_Member found
Run this command for more information about debugging errors: cci error --help
Michaels-MacBook-Pro:OmbudsmanCloudCare michaelkolodner$

In forceignore, add ignore profiles to eliminate unneeded profiles to be pulled.

I propose adding a custom button or a Rich Text element to a few highly-trafficked pages in the app. Ideally, this button/element will link our new ombudsman directly to the community group, enabling them to have immediate access to the community if they have questions.

My initial idea was to add a custom button to our highly-used objects (Case, Contact, etc.) Michael proposed alternatives that involved a Rich Text element to the home page and help menu.

Work with forceignore file to exclude NPSP Metadata when pulling changes.

Can we change the Contact: Relationship to Sailor field to a picklist, please?
Values would be as follows:

• spouse
• partner
• parent
• other family
• friend
• other

It is also missing the field "Sailor's Ship Email"

Ombudsman have requested the following be added to the "Send Case to Command" template under the field "Individual/Case Contact Name":

Individual/Case Contact's email address
Individual/Case Contact's phone number

@Nickers3 I'm getting this warning today when using dx_push:
(node:17410) Warning: The .forceignore file doesn't adhere to .gitignore format which will be the default behavior starting in Spring '21 release. More information on .gitignore format here: https://git-scm.com/docs/gitignore. Fix the following lines in your .forceignore and add '# .forceignore v2' to your .forceignore file to switch to the new behavior.
(node:17410) Warning: .DS_Store

This is beyond something I can help with, sorry.

When running Send Case to Command Action, Command Contacted is not getting populated on package.

When a new field updates is created, it works so it may be due to the name space.

I'm about as sure as I can be that this didn't happen in a real install into a trial org.
But in a scratch org the sysadmin profile and the Ombudsman Standard User profile both end up with the OCC Help and Training Center tab set to Tab Hidden (Setup>Profiles>profile name>Profile Overview>Object Settings>OCC Help and Training Center), which means the help and training page does not show up in the OCC app nor is it available from the App Launcher.

@coriobriensfdo - I'm not sure how to transfer this repo to SFDO-Community-Sprints to make it officially part of Open Source Commons. ("Application" email coming in a moment.)

Because we are using the ensure_record_type CCI command on the contact object, we created duplicate Family Member record types. This didn't appear in scratch orgs due to not having namespaces.

Our options are to either create an OCC Master record type that can be deleted. OR to remove one of the record types from the package. I'd recommend the OCC Master as a post install step could be to deactivate or delete.

Thoughts @mkolodner?

The two resource contacts, when just deployed to a new scratch org, do not have their organization in Primary Affiliation. This was part of the dataset as recently as Friday. Not sure how that disappeared.

Scott Blumenthal and Thomas Helper both have them in my dev org (from which the dataset was pulled) but not in the most recent scratch org I spun up.

"Log a Call" appears on the following page layouts for both Ombudsman Standard User and Sys Admin profiles.

Sailor
Contact
Case
Lead

Oops! Need to fix that!

Add fields to break out Sailor Name into parts, and a template flow (record triggered, before save) that concatenates them for the Name field.

Goal: To improve video script for on-demand training series. Might be an option to create additional training topics if time permits.
How to Log an Interaction video, pw: team
How to Log Touchpoints Only video, pw: team
How to Log Professional Development & Admin Duties video, pw: team
Additional Topics: Lead process, Email templates, Automations, Chatter, Reports & Dashboards
Resources: https://ombudcare.com/publiclinks

When OCC is installed via MetaDeploy (https://install.salesforce.org/products/ombudsman-cloud-care/) the Command Name field (which is an unpackaged post step so that you can edit the default value) shows up with no profiles assigned field level security. Obviously my preference would be to assign it to all profiles (or at least sysadmin and the Ombudsman Standard User that we install). But if we can't do that, I just need to know so that I can indicate the change in the post install steps (https://docs.google.com/document/d/1e2zoWwjPJv9DVSV4MG8rRX_dv4yxXHdLQWeDcJNNSLE/edit#).

After creating a new developer org and running the ci_master command, I encounter an error (below)

It seems to be because standard components are included and cannot delete. @davidmreed, any ideas? Seems to be the standard quick actions that we run into issues with.

2020-06-03 10:51:48: Running task: uninstall_packaged_incremental
2020-06-03 10:51:48: ------------------------------------------------------------
2020-06-03 10:51:48:
2020-06-03 10:51:48: Options:
2020-06-03 10:51:48: path: src
2020-06-03 10:51:48: package: OmbudsmanCloudCare
2020-06-03 10:51:48: purge_on_delete: True
2020-06-03 10:51:48: ignore: {}
2020-06-03 10:51:48: ignore_types: ['RecordType']
2020-06-03 10:51:50: Org info updated, writing to keychain
2020-06-03 10:51:50: Beginning task: UninstallPackagedIncremental
2020-06-03 10:51:50:
2020-06-03 10:51:50: Retrieving metadata in package OmbudsmanCloudCare from target org
2020-06-03 10:51:50: Pending
2020-06-03 10:51:50: [Pending]: next check in 1 seconds
2020-06-03 10:51:52: [Pending]: next check in 1 seconds
2020-06-03 10:51:53: [Pending]: next check in 2 seconds
2020-06-03 10:51:55: [Pending]: next check in 2 seconds
2020-06-03 10:51:58: [Pending]: next check in 2 seconds
2020-06-03 10:52:00: [Done]
2020-06-03 10:52:04: Deleting metadata:
2020-06-03 10:52:04: QuickAction: Case.LogACall
2020-06-03 10:52:04: QuickAction: Case.SendEmail
2020-06-03 10:52:04: QuickAction: LogACall
2020-06-03 10:52:04: QuickAction: NewCase
2020-06-03 10:52:04: QuickAction: NewEvent
2020-06-03 10:52:04: QuickAction: NewTask
2020-06-03 10:52:04: QuickAction: SendEmail
2020-06-03 10:52:04: Deleting metadata in package OmbudsmanCloudCare from target org
2020-06-03 10:52:04: Pending
2020-06-03 10:52:04: [Pending]: next check in 1 seconds
2020-06-03 10:52:06: [Done]
2020-06-03 10:52:07: [Failed]: Update of QuickAction NewTask: Error: Cannot delete action NewTask. The following layout is referencing this. : Sailor
Layout. Cannot delete action NewTask. The following layout is referencing this. : Campaign Layout. Cannot delete action NewTask. The following layout
is referencing this. : Task Layout. Cannot delete action NewTask. The following layout is referencing this. : OCC Organization Account Layout. Cannot
delete action NewTask. The following layout is referencing this. : Contact (Marketing) Layout. Cannot delete action NewTask. The following layout is referencing this. : Lead Layout. Cannot delete action NewTask. The following layout is referencing this. : Opportunity Layout. Cannot delete action NewTask. The following layout is referencing this. : Opportunity (Suppor

Update of QuickAction Case.SendEmail: Error: Cannot delete action SendEmail. The following layout is referencing this. : Case (Marketing) Layout. Cannot delete action SendEmail. The following layout is referencing this. : Case (Sales) Layout. Cannot delete action SendEmail. The following layout is referencing this. : Case (Support) Layout. Cannot delete action SendEmail. The following layout is referencing this. : Case Layout.

Update of QuickAction Case.LogACall: Error: Cannot delete action LogACall. The following layout is referencing this. : Case Layout.

Update of QuickAction SendEmail: Error: Cannot delete action SendEmail. The following layout is referencing this. : OCC Household Account Layout. Cannot delete action SendEmail. The following layout is referencing this. : Campaign Layout. Cannot delete action SendEmail. The following layout is referencing this. : Household Lightning Layout. Cannot delete action SendEmail. The following layout is referencing this. : OCC Family Member. Cannot delete action SendEmail. The following layout is referencing this. : OCC Organization Account Layout. Cannot delete action SendEmail. The following layout
is referencing this. : Organization Lightning Layout. Cannot delete action SendEmail. The following layout is referencing this. : Contact (Marketing)
Layout. Cannot delete action SendEmail.

Update of QuickAction LogACall: Error: Cannot delete action LogACall. The following layout is referencing this. : Sailor Layout. Cannot delete action
LogACall. The following layout is referencing this. : Campaign Layout. Cannot delete action LogACall. The following layout is referencing this. : Task Layout. Cannot delete action LogACall. The following layout is referencing this. : OCC Organization Account Layout. Cannot delete action LogACall. The following layout is referencing this. : Contact (Marketing) Layout. Cannot delete action LogACall. The following layout is referencing this. : Lead
Layout. Cannot delete action LogACall. The following layout is referencing this. : Opportunity Layout. Cannot delete action LogACall. The following layout is referencing this. : Opportunity

Update of QuickAction NewEvent: Error: Cannot delete action NewEvent. The following layout is referencing this. : Campaign Layout. Cannot delete action NewEvent. The following layout is referencing this. : Task Layout. Cannot delete action NewEvent. The following layout is referencing this. : Household Lightning Layout. Cannot delete action NewEvent. The following layout is referencing this. : Organization Lightning Layout. Cannot delete action NewEvent. The following layout is referencing this. : Contact (Marketing) Layout. Cannot delete action NewEvent. The following layout is referencing this. : Lead Layout. Cannot delete action NewEvent. The following layout is referencing this. : Opportunity Layout. Cannot delete action NewEvent. The following layout is referencing this. :

Update of QuickAction NewCase: Error: Cannot delete action NewCase. The following layout is referencing this. : Sailor Layout. Cannot delete action NewCase. The following layout is referencing this. : Campaign Layout. Cannot delete action NewCase. The following layout is referencing this. : OCC Organization Account Layout. Cannot delete action NewCase. The following layout is referencing this. : Contact (Marketing) Layout. Cannot delete action NewCase. The following layout is referencing this. : Lead Layout. Cannot delete action NewCase. The following layout is referencing this. : Opportunity
Layout. Cannot delete action NewCase. The following layout is referencing this. : Opportunity (Support) Layout. Cannot delete action NewCase. The following layout is referencing this. : Le
2020-06-03 10:52:07: Exception in task deploy_packaging.uninstall_packaged_incremental

Error: Could not process MDAPI response: Update of QuickAction NewTask: Error: Cannot delete action NewTask. The following layout is referencing this. : Sailor Layout. Cannot delete action NewTask. The following layout is referencing this. : Campaign Layout. Cannot delete action NewTask. The following layout is referencing this. : Task Layout. Cannot delete action NewTask. The following layout is referencing this. : OCC Organization Account Layout. Cannot delete action NewTask. The following layout is referencing this. : Contact (Marketing) Layout. Cannot delete action NewTask. The following layout is referencing this. : Lead Layout. Cannot delete action NewTask. The following layout is referencing this. : Opportunity Layout. Cannot delete
action NewTask. The following layout is referencing this. : Opportunity (Suppor

Update of QuickAction Case.SendEmail: Error: Cannot delete action SendEmail. The following layout is referencing this. : Case (Marketing) Layout. Cannot delete action SendEmail. The following layout is referencing this. : Case (Sales) Layout. Cannot delete action SendEmail. The following layout is referencing this. : Case (Support) Layout. Cannot delete action SendEmail. The following layout is referencing this. : Case Layout.

Update of QuickAction Case.LogACall: Error: Cannot delete action LogACall. The following layout is referencing this. : Case Layout.

Update of QuickAction SendEmail: Error: Cannot delete action SendEmail. The following layout is referencing this. : OCC Household Account Layout. Cannot delete action SendEmail. The following layout is referencing this. : Campaign Layout. Cannot delete action SendEmail. The following layout is referencing this. : Household Lightning Layout. Cannot delete action SendEmail. The following layout is referencing this. : OCC Family Member. Cannot delete action SendEmail. The following layout is referencing this. : OCC Organization Account Layout. Cannot delete action SendEmail. The following layout
is referencing this. : Organization Lightning Layout. Cannot delete action SendEmail. The following layout is referencing this. : Contact (Marketing)
Layout. Cannot delete action SendEmail.
Update of QuickAction LogACall: Error: Cannot delete action LogACall. The following layout is referencing this. : Sailor Layout. Cannot delete action
LogACall. The following layout is referencing this. : Campaign Layout. Cannot delete action LogACall. The following layout is referencing this. : Taske following layout is referencing this. : Contact (Marketing) Layout. Cannot delete action LogACall. The following layout is referencing this. : Lead
Layout. Cannot delete action LogACall. The following layout is referencing this. : Opportunity Layout. Cannot delete action LogACall. The following layout is referencing this. : Opportunity

Update of QuickAction NewEvent: Error: Cannot delete action NewEvent. The following layout is referencing this. : Campaign Layout. Cannot delete action NewEvent. The following layout is referencing this. : Task Layout. Cannot delete action NewEvent. The following layout is referencing this. : Household Lightning Layout. Cannot delete action NewEvent. The following layout is referencing this. : Organization Lightning Layout. Cannot delete action NewEvent. The following layout is referencing this. : Contact (Marketing) Layout. Cannot delete action NewEvent. The following layout is referencing this. : Lead Layout. Cannot delete action NewEvent. The following layout is referencing this. : Opportunity Layout. Cannot delete action NewEvent. The following layout is referencing this. :

Update of QuickAction NewCase: Error: Cannot delete action NewCase. The following layout is referencing this. : Sailor Layout. Cannot delete action NewCase. The following layout is referencing this. : Campaign Layout. Cannot delete action NewCase. The following layout is referencing this. : OCC Organization Account Layout. Cannot delete action NewCase. The following layout is referencing this. : Contact (Marketing) Layout. Cannot delete action NewCase. The following layout is referencing this. : Lead Layout. Cannot delete action NewCase. The following layout is referencing this. : Opportunity
Layout. Cannot delete action NewCase. The following layout is referencing this. : Opportunity (Support) Layout. Cannot delete action NewCase. The following layout is referencing this. : Le

When a new case is created, there should be at least a single Interaction touchpoint created. In the TR's org there is a Process Builder that accomplishes this. (And possibly also creates a touchpoint when an email is sent.) We need to have a template PB in the package, with post-install instructions for admins to clone this PB.

Per discussion in Issue #123 it's clear that Red Cross should no longer be an available Case Reason.

Looks like when I added the New Case global action to the repo, somehow its field layout didn't show up.

Add a rich text component on the home page with a link to the OCC Help Desk on Trailblazer. See instructions in post install instructions for 1.2.

@Nickers3 - Just tried to spin up a dev org from the Master as it stands now and got an error:

Running command: sfdx force:source:push -u [email protected]
2020-05-19 10:04:11: Job ID | 0Af1h00000OoH4gCAF
2020-05-19 10:05:00: TYPE PROJECT PATH PROBLEM
2020-05-19 10:05:00: ───── ────────────────────────────────────────────────────── ────────────────────────────────────────────
2020-05-19 10:05:00: Error force-app/main/default/settings/Case.settings-meta.xml CaseSettings: Specify the default case user.
2020-05-19 10:05:01: Return code: 1
stderr: ERROR running force:source:push: Push failed.

2020-05-19 10:05:01: Exception in task deploy_unmanaged.dx_push

Error: Return code: 1
stderr: ERROR running force:source:push: Push failed.

When deploying metadata to packaging org, receive the following message:

No parser configuration found for subdirectory customHelpMenuSections

Is tied to a CCI error - SFDO-Tooling/CumulusCI#1832

I've been tracking some required changes to the dataset. These are nice-to-have, not critical.

1. Current order of adding Accounts and Contacts results in about a dozen Anonymous Household accounts.

2. The inserted Tasks are not connected to Cases because they have nothing in the polymorphic WhatId field. @davidmreed indicated that as long as our dataset only uses that field for one SObject (it would be Case), we should actually be able to populate that field. I can manually add the case lookups to a dataset for pulling back down, but am not clear on how to edit mapping.yml to make it work. (I tried one or two times and failed.)

Request that these Lead fields, record types, etc. be incorporated into the package.

Lead Fields:

• Relationship to Sailor- picklist (spouse,` partner, parent, other family, friend, other)
  

• Request Additional Information- checkbox
  

• Request Additional Information Date- Date/time
  

• Sailor's Command or Ship Email- Email
  

• Sailor's Full Name- Text (50)
  

• Status- Picklist- values below
  

1. New
2. New by Sailor
3. Working, Contacted
4. Other Commands
5. Requires Family Follow-up
6. Sailor Confirmation
7. Prospective Families
8. Closed- Converted
9. Closed- Not Converted

****In Object Manager > Lead > Fields & Relationships > Map fields > Contacts tab- Map Lead "Relationship to Sailor" to Contact "Relationship to Sailor"

Lead Record Type-

Family Member- Select when referring to a Household or family member

Lead Process- Default "New"

New by Sailor
New
Other Commands
Prospective Families
Working- Contacted
Requires Family Follow-up
Sailor Confirmation
Closed- Converted
Closed- Not Converted

When installing test package, received the following error message: (Case.SendEmail) Required fields are missing: [DefaultValueFormula].

To provide ombudsman users and sys admins data visualization of total # cases, cases by reason, leads, sailors, and contacts in org.

When installing the package, the Contact compact layout is assigned for resource contact, but not for Primary or for Family Member (which inherits from Primary)

dev_org flow currently hits an error due to some LeadSource values that aren't in the org.

2020-07-17 14:46:39: Running command: sfdx force:source:push -u [email protected]
2020-07-17 14:46:39: Options:
2020-07-17 14:46:39: command: sfdx force:source:push -u [email protected]
2020-07-17 14:46:39: Beginning task: SFDXOrgTask
2020-07-17 14:46:39:
2020-07-17 14:46:39: Running command: sfdx force:source:push -u [email protected]
2020-07-17 14:46:42: Job ID | 0Af63000019vp7uCAA
2020-07-17 14:47:33: TYPE PROJECT PATH PROBLEM
2020-07-17 14:47:33: ───── ─────────────────────────────────────────────────────────────────────────────────────── ───────────────────────────────────────────────────────────────────────────
2020-07-17 14:47:33: Error force-app/main/default/objects/Contact/recordTypes/Family_Member.recordType-meta.xml Picklist value: Partner Referral in picklist: LeadSource not found (394:18)
2020-07-17 14:47:33: Error force-app/main/default/objects/Contact/recordTypes/Resource_Contact.recordType-meta.xml Picklist value: Partner Referral in picklist: LeadSource not found (552:18)
2020-07-17 14:47:36: Return code: 1
stderr: ERROR running force:source:push: Push failed.

2020-07-17 14:47:36: Exception in task deploy_unmanaged.dx_push

Error: Return code: 1
stderr: ERROR running force:source:push: Push failed.

Just noticed that Case Reason in a new scratch org includes the original standard picklist values (Installation, Equipment Complexity) that we would like to disable. Plus Red Cross Message, a new value I am sure I added several days ago, is not there. I am obviously capable of adding Red Cross Message to the repo, but wanted to note it in case someone knows why it didn't stick.

@Nickers3 - I don't seem to be able to spin up a scratch org using dev_org. Error is below. Looks like the record type insert is hanging up on the Mx salutation. Not sure how that problem has crept back in.

2020-08-03 17:56:27: Running command: sfdx force:source:push -u [email protected]
2020-08-03 17:56:29: Job ID | 0Af1h00000SfFsoCAF
2020-08-03 17:57:07: TYPE PROJECT PATH PROBLEM
2020-08-03 17:57:07: ───── ─────────────────────────────────────────────────────────────────────────────────────── ──────────────────────────────────────────────────────────
2020-08-03 17:57:07: Error force-app/main/default/objects/Contact/recordTypes/Family_Member.recordType-meta.xml Picklist value: Mx%2E in picklist: Name not found (394:18)
2020-08-03 17:57:07: Error force-app/main/default/objects/Contact/recordTypes/Resource_Contact.recordType-meta.xml Picklist value: Mx%2E in picklist: Name not found (533:18)
2020-08-03 17:57:08: Return code: 1
stderr: ERROR running force:source:push: Push failed.

2020-08-03 17:57:08: Exception in task deploy_unmanaged.dx_push

Error: Return code: 1
stderr: ERROR running force:source:push: Push failed.

Goal: To improve video script for on-demand training series. Need to update screenshots with new OCC app (revised Dec 2020).
Quick Tour video
Create a Case video
Update a Case video
Send Case to Command video
Close a Case video
Resources: https://ombudcare.com/publiclinks

More data to follow once notes are obtained.

I see Red Cross Message in the CaseReason standard value set. But it does not show in the org.

The Sexual Assault fields are not on the Ombudsman Registry Activities report as packaged. Neither SAPR Incoming nor SAPR Outgoing.
Possible other fields are missing! We should check and fix!

Mary, Shelley, Brittany, and I are working feverishly to build out functionality for the USS TR to do their required reporting to the Navy for the Ombudsman Registry. Once solved for the TR, which probably involves updates to Log a Call, some page layouts, maybe even some automation, we should get this functionality into the package.

The OCC Help and Training Page link to the Hub and the Salesforce military community are no longer the preferred help areas. We should direct people to OCC Help Desk on Trailblazer (https://trailblazers.salesforce.com/_ui/core/chatter/groups/GroupProfilePage?g=0F94S000000GwW8)

Instructions state to update command name, however due to it being managed, it is not editable. Update package to make this field unpackaged.

When installing the test package getting the following error: (OCC_Contact_Record_Page) Your org doesn't have access to component runtime_sales_social:socialPanel.

Is due to Social Accounts, Contacts, and Leads Settings needing to be enabled. Either build enabling in pre install or take out.