@salesforce/ui-bundle-template-app-angular-template-b2e 12.5.3 → 12.5.4

package/README.md

@@ -0,0 +1,54 @@
+# Angular Internal App
+
+Angular internal app template — Agentforce conversation client and object search across Salesforce records, surfaced through a CustomApplication without a site container.
+
+## In this monorepo
+
+This package is a **template app** in the ui-bundle monorepo. It is built by applying feature patches to the base Angular app; the output is written to `dist/`.
+
+### Build
+
+```bash
+nx run @salesforce/ui-bundle-template-app-angular-template-b2e:build
+```
+
+Produces an SFDX project in `dist/` with the UI Bundle at `dist/force-app/main/default/uiBundles/angularintapp/`.
+
+### Dev server
+
+```bash
+nx run @salesforce/ui-bundle-template-app-angular-template-b2e:dev
+```
+
+Starts the Salesforce Angular dev server (`sf-angular-serve`) from the built output in `dist/`.
+
+### Watch
+
+```bash
+nx run @salesforce/ui-bundle-template-app-angular-template-b2e:watch
+```
+
+Re-applies patches automatically when source files change.
+
+### Test
+
+This package has no dedicated test target. To run tests, build first, then run them from the built UI Bundle:
+
+```bash
+nx run @salesforce/ui-bundle-template-app-angular-template-b2e:build
+cd dist/force-app/main/default/uiBundles/angularintapp && npm install && npm test
+```
+
+Runs the unit test suite via `ng test`.
+
+### Clean
+
+```bash
+npm run clean
+```
+
+Removes the `dist/` directory.
+
+---
+
+For standalone run, deploy, and test instructions (e.g. after publishing or extracting `dist/`), see the [UI Bundle README](dist/force-app/main/default/uiBundles/angularintapp/README.md).

package/dist/CHANGELOG.md

@@ -3,6 +3,14 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [12.5.4](https://github.com/salesforce-experience-platform-emu/webapps/compare/v12.5.3...v12.5.4) (2026-09-09)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
 ## [12.5.3](https://github.com/salesforce-experience-platform-emu/webapps/compare/v12.5.2...v12.5.3) (2026-09-08)
 
 **Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project

package/dist/README.md

@@ -1,69 +1,107 @@
-# Salesforce DX Project: Next Steps
+# Angular Internal App
 
-Now that you’ve created a Salesforce DX project, what’s next? Here are some documentation resources to get you started.
+An internal Angular starter template for the Salesforce platform. Includes an Agentforce conversation client and object search across Salesforce records; intended for internal (non-Experience Cloud) deployment via a CustomApplication in the Lightning Experience App Launcher. Built with Angular (standalone components), Spartan NG (`@spartan-ng/brain` primitives with helm UI components copied into `src/app/shared/`), Tailwind CSS, Lucide icons (`@ng-icons/lucide`), and TypeScript.
 
-## Web app: install, build, and dev server
+## What's included
 
-From the **SFDX project root** (this directory), run:
+This project ships the UI Bundle plus a CustomApplication that surfaces it in the Lightning Experience App Launcher. No additional data-model metadata (objects, Apex, etc.) is included — bring your own data model.
+
+```
+force-app/main/default/
+├── applications/                 # CustomApplication (App Launcher entry)
+├── permissionsets/               # Permission sets
+└── uiBundles/
+    └── angularintapp/            # Angular UI Bundle (source, config, tests)
+```
+
+## Getting started
+
+Install project dependencies and start the local dev server:
 
 ```bash
+npm install
 npm run sf-project-setup
 ```
 
-This installs dependencies in the UI Bundle, builds it, and starts the Vite dev server. Use this after cloning or extracting the project.
+This installs the UI Bundle dependencies, builds the app, and starts the Salesforce Angular dev server (`sf-angular-serve`). For manual build and test instructions, see the [UI Bundle README](force-app/main/default/uiBundles/angularintapp/README.md).
+
+## Add features
+
+Use the features CLI to install additional UI features into the UI Bundle.
+
+List all available features:
+
+```bash
+npx @salesforce/ui-bundle-features-experimental list
+```
+
+Get details about a specific feature (description, dependencies, files, and integration examples):
+
+```bash
+npx @salesforce/ui-bundle-features-experimental describe <feature-name>
+```
+
+Install a feature:
 
-## Set up the org
+```bash
+npx @salesforce/ui-bundle-features-experimental install <feature-name> --ui-bundle-dir angularintapp
+```
+
+After installation, the CLI will list any `__example__` files that need manual integration. Read each example file to see the integration pattern, apply it to the target file, then delete the example file.
+
+## Deploy
+
+### Deploy everything (CustomApplication + UI Bundle)
+
+```bash
+cd force-app/main/default/uiBundles/angularintapp && npm install && npm run build && cd -
+sf project deploy start --source-dir force-app --target-org <alias>
+```
 
-`npm run setup` configures a target org from this project in one command: it logs in
-(a required precondition — auto-skipped if the org is already connected), deploys
-metadata, assigns permission sets, imports sample data, refreshes the GraphQL
-schema/types, and builds the UI Bundle. When `--target-org` is omitted it uses your
-default org or, in an interactive terminal, prompts you to pick one.
+### Deploy the UI Bundle only
 
 ```bash
-npm run setup -- --target-org <alias>     # or omit --target-org to use the default / pick
+cd force-app/main/default/uiBundles/angularintapp && npm install && npm run build && cd -
+sf project deploy start --source-dir force-app/main/default/uiBundles --target-org <alias>
 ```
 
-Setup does **not** start the dev server. Once the org is set up, use `dev:preview` to
-refresh the GraphQL types against the org and launch the Vite dev server on its own:
+Replace `<alias>` with your target org alias.
+
+## Setup scripts
+
+Two npm scripts at the project root streamline getting started and deployment.
+
+**`npm run sf-project-setup`** — installs the UI Bundle dependencies, builds the app, and starts the dev server (see [Getting started](#getting-started)).
+
+**`npm run setup`** — runs the full deployment setup in one command: org login (a required precondition, auto-skipped if already connected), UI Bundle build, deploy metadata, fetch GraphQL schema, and run codegen. It no longer starts the dev server — run `npm run dev:preview` for that:
 
 ```bash
-npm run dev:preview
+# Install project dependencies first (required before running setup)
+npm install
+
+npm run setup -- --target-org <alias>
 ```
 
-### Setup configuration (`scripts/org-setup.config.json`)
-
-`org-setup.config.json` controls which steps run and how. Every top-level section is
-optional; an absent section hides its step. It is validated against a shared schema
-at build/CI time and again at the start of every `npm run setup`, so a malformed
-config fails fast rather than misbehaving.
-
-```jsonc
-{
-  "permsetAssignments": {
-    "assignments": {
-      "My_Access": { "assignee": "currentUser" }
-    }
-  },
-  "role": { "assignee": "currentUser", "roleName": "Admin" },
-  "selfRegistration": {
-    "selfRegProfile": "My Prospect Profile",
-    "accountName": "My Self-Registration"
-  }
-}
+Running without flags presents an interactive step picker. Pass `--yes` to skip it and run all steps immediately:
+
+```bash
+npm run setup -- --target-org <alias> --yes
 ```
 
-When a `selfRegistration` section is present, setup runs a **license pre-check**
-before configuring self-registration: it derives the required `UserLicense` from the
-configured `selfRegProfile` (matched on the stable `LicenseDefinitionKey`, not the
-display name) and, if the org lacks that license or has no available seats, **warns
-and skips** self-registration instead of reporting success — so prospect login can't
-silently fail on an under-provisioned org. No separate license field is configured;
-the requirement always follows the profile the flow assigns.
+Common options:
+
+| Option                    | Description                                     |
+| ------------------------- | ----------------------------------------------- |
+| `--target-org <alias>`    | Target org. If omitted, uses default org/prompt |
+| `--skip-deploy`           | Do not deploy metadata                          |
+| `--skip-graphql`          | Skip GraphQL schema fetch and codegen           |
+| `--skip-ui-bundle-build`  | Skip `npm install` and UI Bundle build          |
+| `--ui-bundle-name <name>` | UI Bundle folder name when multiple exist       |
+| `-y, --yes`               | Skip interactive step picker; run all steps     |
 
-## How Do You Plan to Deploy Your Changes?
+> Login is a required precondition (no `--skip-login`), and the dev server is no longer part of setup (no `--skip-dev`); both flags are accepted but ignored. To start the dev server after setup, run `npm run dev:preview`.
 
-Do you want to deploy a set of changes, or create a self-contained application? Choose a [development model](https://developer.salesforce.com/tools/vscode/en/user-guide/development-models).
+For all options: `npm run setup -- --help`.
 
 ## Configure Your Salesforce DX Project
 

package/dist/force-app/main/default/uiBundles/angularintapp/README.md

@@ -1,6 +1,6 @@
 # Base Angular App
 
-Base Angular App is a template application that demonstrates how to build an Angular UI Bundle on the Salesforce platform with the Angular CLI, TypeScript, Tailwind, and the Salesforce UI Bundle SDK. It provides a minimal shell (home, 404), routing with standalone components and signals, so feature apps can extend it via the patches pipeline.
+Base Angular App is a template application that demonstrates how to build an Angular UI Bundle on the Salesforce platform with the Angular CLI, TypeScript, Tailwind, Spartan NG (shadcn/ui for Angular), and the Salesforce UI Bundle SDK. It provides a minimal shell (home, 404), routing with standalone components and signals, so feature apps can extend it via the patches pipeline.
 
 This UI Bundle lives inside an SFDX project. The project root is the directory that contains `force-app/` and `sfdx-project.json`. Run the commands in the sections below from the paths indicated.
 

package/dist/force-app/main/default/uiBundles/angularintapp/package.json

@@ -28,8 +28,8 @@
     "@angular/router": "^21.2.0",
     "@ng-icons/core": "^32.2.0",
     "@ng-icons/lucide": "^32.2.0",
-    "@salesforce/angular-plugin-ui-bundle": "^12.5.3",
-    "@salesforce/platform-sdk": "^12.5.3",
+    "@salesforce/angular-plugin-ui-bundle": "^12.5.4",
+    "@salesforce/platform-sdk": "^12.5.4",
     "@spartan-ng/brain": "^1.3.1",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
@@ -62,7 +62,7 @@
     "typescript": "~5.9.2",
     "typescript-eslint": "^8.0.0",
     "vitest": "^4.1.0",
-    "@salesforce/graphiti": "^12.5.3"
+    "@salesforce/graphiti": "^12.5.4"
   },
   "overrides": {
     "undici": "^7.28.0"

package/dist/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@salesforce/ui-bundle-template-base-sfdx-project",
-  "version": "12.5.3",
+  "version": "12.5.4",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@salesforce/ui-bundle-template-base-sfdx-project",
-      "version": "12.5.3",
+      "version": "12.5.4",
       "license": "SEE LICENSE IN LICENSE.txt",
       "dependencies": {
         "fast-xml-parser": "^5.9.3",

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/ui-bundle-template-base-sfdx-project",
-  "version": "12.5.3",
+  "version": "12.5.4",
   "description": "Base SFDX project template",
   "license": "SEE LICENSE IN LICENSE.txt",
   "publishConfig": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/ui-bundle-template-app-angular-template-b2e",
-  "version": "12.5.3",
+  "version": "12.5.4",
   "description": "Salesforce Angular internal app template",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "",