@aglyn/plugins-crm 1.0.0-beta.199 → 1.0.0-beta.201

package/src/lib/components/lead-properties-card.d.ts

@@ -70,15 +70,23 @@ export interface LeadPropertiesCardProps {
  * What the team knows and decides about a lead: status, owner, notes, and
  * the identity and consent the capture recorded (AGL-2608).
  *
+ * Two cards. The record's header carries the identity, the status and owner,
+ * the consent the capture recorded and the record's actions. **Details**
+ * under it carries the profile, the org's own lead fields under **More
+ * fields**, and the notes — one card with one Save in its header, the way
+ * Salesforce keeps a record's standard and custom fields in one Details
+ * section.
+ *
  * Status and owner are single-field client writes — the rules let a site
  * admin, editor or author update `hosts/{hostId}/leads`, and a one-field
- * `update` cannot roll anything else back. Notes are a text field seeded
- * from the document, so that save goes through `writeGuardedBySeed`: a draft
- * edited over a cached read would otherwise overwrite a newer note with an
- * older one plus a sentence.
+ * `update` cannot roll anything else back. The details are drafts seeded
+ * from the document, so their save goes through `writeGuardedBySeed`: a
+ * draft edited over a cached read would otherwise overwrite a newer note or
+ * profile with an older one.
  *
- * Converted leads are read-only here. Their status is the conversion, and
- * the actions become links to what the conversion made.
+ * Converted leads are read-only here, but for the notes. Their status is the
+ * conversion, and the header's actions become links to what the conversion
+ * made.
  */
 export declare function LeadPropertiesCard(props: LeadPropertiesCardProps): import("react").JSX.Element;
 export declare namespace LeadPropertiesCard {