Merge main into feature/v3-staging

.a4drules/workflows/new-inds-org.md

@@ -0,0 +1,116 @@
+Use known or explicit CumulusCI (CCI) plans, flows, and tasks first, and if these are unclear then use the the Salesforce DX MCP server tools next and only fall back to `sf` if the MCP service is unavailable.
+
+<detailed_sequence_of_steps>
+
+# Setup a New Scratch Org - Detailed Sequence of Steps
+
+Perform the steps below independently in the following order.
+
+## 1. Confirm Org Alias
+
+    ```xml
+    <ask_followup_question>
+        <question>Enter the org alias.
+        <options>["dev", "demo", "beta", "feature"]</options>
+    </ask_followup_question>
+    ```
+
+## 2. Check for Existing Org
+
+    Check if the org already exists and is active.
+
+## 3. Create and Deploy
+
+    If the alias exists as a name of a Scratch Org that is NOT EXPIRED and IS ACTIVE or exists as a Connected Org, DO NOT create a new scratch org and skip to the next step.
+
+    If the alias exists as a name of a Scratch Org and is EXPIRED or NOT ACTIVE, then create the new scratch org.
+
+## 4. Open in Browser
+
+    Open the org in the browser.
+
+## 5. Set as Default
+
+    If the org already exists but it is not the default org or the org was just created, then set it as the default org.
+
+</detailed_sequence_of_steps>
+
+<common_commands>
+
+1. When you need to get the list of all configured Salesforce orgs or find out which org is the default or if a scratch org is expired.
+
+```bash
+cci org list
+```
+
+2. When checking if an org is active, review the output of `cci org list` 
+
+The output shows: 
+- A value with a "+" in the Default column indicates the org is the default. 
+- A bare integer (e.g., "1") indicates the lifespan in days and the org is not active. 
+- A fractional value (e.g., "16/30") indicates the org is on day 16 of a 30-day lifespan when it will expire.
+- A value with a "+" in the Expired column indicates the org is expired.
+- A value in the Domain further reinforces that a scratch org is active and assigned to that domain.
+
+- Explicitly treat bare interger in Days as NOT ACTIVE and require creating or recreating the scratch org.
+- Require Domain present to consider a scratch org ACTIVE.
+- If alias is default (+) but NOT ACTIVE, still create.
+
+3. Create a new scratch and deploy metadata from the CCI project. This command should not be run if an org is already active as it could cause conflicts. Confirm with user if it should be run.
+
+Running this command takes several minutes to fully execute and the subsequent steps should not be run until this is fully completed.
+
+Based on the alias, a different command should be run.
+
+For `dev` or `feature` use:
+
+```bash
+cci flow run dev_org --org <alias>
+```
+
+For `demo` use:
+
+```bash
+cci flow run config_demo --org <alias>
+```
+
+For `beta` use:
+
+```bash
+cci flow run install_beta --org <alias>
+```
+
+
+4. Open org in browser
+
+```bash
+cci org browser <alias>
+```
+
+5. Set org as the default for the project
+
+```bash
+cci org default <alias>
+```
+
+6. Set a CCI dev hub
+
+```xml
+<ask_followup_question>
+    <question>What is the alias of the dev hub?
+</ask_followup_question>
+```
+
+```xml
+<ask_followup_question>
+    <question>Should this dev hub always be assigned for the project?
+    <options>["Yes", "No"]</options>
+</ask_followup_question>
+```
+If the dev hub should always be assigned for the project, append `--project` to the following command when running it.
+
+```bash
+cci service default devhub <alias> 
+```
+
+</common_commands>

.forceignore

@@ -15,7 +15,7 @@ package.xml
 **profile
 **/profiles/**
 **/settings/**
-**/Account/**
-**/Contact/**
 
-**/unpackaged/**
+**/tsconfig.json
+
+**/*.ts

.github/CODEOWNERS

@@ -6,5 +6,9 @@
 /tasks/               @SFDO-Community/sfdo-release-engineers
 
 # Actions
-/.github              @SFDO-Community/sfdo-release-engineers
-/scripts              @SFDO-Community/sfdo-release-engineers
+/.github                @SFDO-Community/sfdo-release-engineers
+/scripts                @SFDO-Community/sfdo-release-engineers
+
+
+#ECCN:Open Source
+#GUSINFO:Open Source,Open Source Workflow

README.md

@@ -3,7 +3,6 @@
 
 With Salesforce Indicators, you can visually highlight important data at a glance, making it easy to focus on what matters most. This Custom Metadata driven Lightning Web Component is all about making key details pop, and giving you lightning-quick insights at a glance on your Salesforce records. 
 
-
 Features:
 * Visualize your data - Display key details in a visually engaging and clutter-free manner, allowing users to quickly understand important information on the record, summarize related records, or highlight exceptions.
 * Make your data come alive - Add a mix of Salesforce and custom colors to match your branding to create visually appealing indicators for your Lightning pages giving your users a more engaging experience.
@@ -14,38 +13,39 @@ Salesforce Indicators is part of the [Salesforce Open Source Commons](https://he
 
 ## Latest Release
 * [Install Salesforce Indicators](https://install.salesforce.org/products/indicators)
-* [Release Notes](https://github.com/SFDO-Community/Salesforce-Indicators/wiki/Release-Notes)
+* [Release Notes](https://sfdo-community-sprints.github.io/indicators-documentation/docs/release-notes/)
 
 ## Project Documentation
-* Documentation can be found in the repository [Wiki](https://github.com/SFDO-Community/Salesforce-Indicators/wiki).
-* Check out the [Cookbook](https://github.com/SFDO-Community/Salesforce-Indicators/wiki/Cookbook) to help you build Indicators that work for your org.
+* Documentation can be found on our [Documentation Site](https://sfdo-community-sprints.github.io/indicators-documentation/).
+* Check out the [Getting Started with Salesforce Indicators](https://sfdo-community-sprints.github.io/indicators-documentation/docs/getting-started/) page to help get started with how to set up Salesforce Indicators in your org.
 
 ## Ask Questions and Get Help
 * Salesforce Indicators is a community built and maintained Salesforce package, please help support this project and share your experiences in the [Trailblazer Community Group](https://trailhead.salesforce.com/trailblazer-community/groups/0F94S000000HEDASA4?tab=discussion). Ask any questions about the Salesforce Indicators project, or the Open Source Commons.
-* If you have any enhancements or issue you can [Log an Issue](https://github.com/SFDO-Community/Salesforce-Indicators/issues).
+* If you have any enhancements or issue you can [Log an Issue](https://github.com/SFDO-Community/Salesforce-Indicators/issues)..
 
 ## Vision & Goals
 * Enhance the current Indicators Bundle Component to improve the experience for Admins and Users.
 * Complete the documentation with different recipes to help Admins get up and running quickly.
 * Showcase and review different apps you can use to achieve similar results, and show how you will probably want to use Salesforce Indicators anyway.
 * Build our planned Components - these components are built on the same Custom Metadata framework and just show the data in different ways:
-  * A Grid Component to quickly show your users excptions or a checklist of fields on the record. Optionally show field values, a custom message for each field, and if the field has an exception. 
+  * A Grid Component to quickly show your users excptions or a checklist of fields on the record. Optionally show field values, a custom message for each field, and if the field has an exception.
   * A Panel Component to provide more value and features than the standard record highlights panel horizontally, or a panel that display the key data vertically.
 
 # How to Contribute:
 - [Install Salesforce Indicators](https://install.salesforce.org/products/indicators)
-- [Set up the Indicator Bundle](https://github.com/SFDO-Community/Salesforce-Indicators/wiki/Indicator-Bundle)
+- [Set up Salesforce Indicators](https://sfdo-community-sprints.github.io/indicators-documentation/docs/setup-salesforce-indicators/)
 - Ask any questions on our [Trailblazer Community Group](https://trailhead.salesforce.com/trailblazer-community/groups/0F94S000000HEDASA4?tab=discussion)
-- Add your own Recipes to the [Cookbook](https://github.com/SFDO-Community/Salesforce-Indicators/wiki/Cookbook) and 
-- Add reviews of any [similar or competitor components](https://github.com/SFDO-Community/Salesforce-Indicators/wiki/Other-Apps-and-Components-to-Enhance-Your-Org)
-- [Volunteer](https://github.com/SFDO-Community/Salesforce-Indicators/wiki/How-to-Volunteer) to enhance the code
+- Add your own [Recipes](https://sfdo-community-sprints.github.io/indicators-documentation/docs/recipes/) to our documentation
+- Add reviews of any [similar or competitor components](https://sfdo-community-sprints.github.io/indicators-documentation/docs/components/other-solutions/)
+- [Volunteer](https://sfdo-community-sprints.github.io/indicators-documentation/docs/getting-involved/how-to-volunteer/) to enhance the app
 - [Log an Issue](https://github.com/SFDO-Community/Salesforce-Indicators/issues)
 - Join us at an upcoming [Salesforce Commons Community Sprint](https://trailhead.salesforce.com/trailblazer-community/groups/0F94S000000GwVK?tab=discussion)
 
 ## Project Acomplishments
-* Rebuilt the component to support Custom Metadata Types
+* Built the component to support Custom Metadata Types
 * Enhancements to the Indicator Bundle Component
 * The Indicator Key compnent and Setup components to help build and understand the Indicators easily
 * New companion components (Grid and Panel) in progress
 * Packaging and release setup
 * Marketing and release of Salesforce Indicators
+* New UI for building Salesforce Indicators in progress

cumulusci.yml

@@ -4,9 +4,9 @@ project:
     package:
         name: Salesforce-Indicators
         namespace: inds
-        api_version: '55.0'
+        api_version: '65.0'
     git:
-        default_branch: 'master'
+        default_branch: 'main'
     test:
         name_match: '%Tests'
     source_format: sfdx
@@ -16,8 +16,7 @@ orgs:
         dev:
             config_file: orgs/dev.json
             days: 30
-            namespaced: True
-    scratch:
+            namespaced: false
         demo:
             config_file: orgs/demo.json
             days: 15
@@ -41,20 +40,31 @@ tasks:
 
     deploy_sample_indicators:
         description: Deploys - Sample Indicators
+        name: Deploy Sample Indicators
         group: Salesforce Metadata
         class_path: cumulusci.tasks.salesforce.Deploy
         options:
-            path: unpackaged/config/sample_AccountContact
+            path: unpackaged/config/sample_AccountContact/Part_1
 
     deploy_sample_indicators_layouts:
         description: Deploys - Sample Indicators Layouts
+        name: Deploy Page Layouts for Sample Indicators
+        group: Salesforce Metadata
+        class_path: cumulusci.tasks.salesforce.Deploy
+        options:
+            path: unpackaged/config/sample_AccountContact/Part_2
+
+    deploy_sample_indicators_objects:
+        description: Deploys - Sample Indicators Assigning Layouts to Objects
+        name: Deploy Page Layouts for Sample Indicators
         group: Salesforce Metadata
         class_path: cumulusci.tasks.salesforce.Deploy
         options:
-            path: unpackaged/config/sample_AccountContact_FlexiPages
+            path: unpackaged/config/sample_AccountContact/Part_3
 
     deploy_training_indicators:
         description: Deploys - Example Indicators used for Training 
+        name: Deploy Training Indicators
         group: Salesforce Metadata
         class_path: cumulusci.tasks.salesforce.Deploy
         options:
@@ -77,16 +87,17 @@ tasks:
 flows:
   sample_inds:
     steps:
-        1:
-            task: deploy_sample_indicators
-            ui_options:
-              is_required: False
-              is_recommended: False
-        2:
-            task: deploy_sample_indicators_layouts
-            ui_options:
-              is_required: False
-              is_recommended: False
+      1:
+        task: deploy_sample_indicators
+        ui_options:
+          is_required: False
+          is_recommended: False
+      2:
+        task: deploy_sample_indicators_layouts
+        ui_options:
+          is_required: False
+          is_recommended: False
+
   customer_org:
     steps:
       1:
@@ -100,21 +111,29 @@ flows:
         ui_options:
           is_required: False
           is_recommended: False
+
   config_dev:
     steps:
-        3:
-            task: generate_accounts_and_contacts
-        4:
-            flow: sample_inds
+      3:
+        task: generate_accounts_and_contacts
+      4:
+        flow: sample_inds
+      5:
+        task: deploy_sample_indicators_objects
+
   config_demo:
     steps:
       1:
         flow: install_prod
       2:
         flow: sample_inds
       3:
-        task: deploy_training_indicators
+        task: deploy_sample_indicators_objects
       4:
+        task: deploy_sample_indicators_layouts
+      5:
+        task: deploy_training_indicators
+      6:
         task: generate_accounts_and_contacts
 
 plans:

force-app/main/default/classes/Cmdt.cls

@@ -17,6 +17,7 @@ public with sharing class Cmdt {
                 sObject__r.QualifiedApiName, 
                 sObject__r.Label
             FROM Indicator_Bundle__mdt
+            ORDER BY Label
         ] ) {
             setBundle(bundle);
         }

force-app/main/default/lwc/illustration/illustration.html

@@ -6,7 +6,7 @@
     <div class="slds-text-longform">
       <h3 class="slds-text-heading_medium">{heading}</h3>
       <slot name="messageBody">
-        <p class="slds-text-body_regular">{messageBody}</p>
+        <p class="slds-text-body_regular slds-p-around_xx-small">{messageBody}</p>
       </slot>
     </div>
   </div>

force-app/main/default/lwc/illustrationImage/illustrationImage.html

@@ -1 +1,3 @@
-<template></template>
+<template>
+    <div>&nbsp;</div>
+</template>

force-app/main/default/lwc/indicatorBundle/indicatorBundle.css

@@ -1,4 +1,8 @@
 .cardIcon {
     --slds-c-icon-color-foreground: var(--foregroundColor);
     --slds-c-icon-color-background: var(--backgroundColor);
+    --slds-c-icon-color-foreground-default: var(--foregroundColor);
+    --slds-c-avatar-initials-text-color-hover:  var(--foregroundColor);
+    --slds-c-avatar-text-color-hover:  var(--foregroundColor);
+    --slds-c-avatar-text-color: var(--foregroundColor);
 }