Skip to main content

Idea pipeline

Filter by idea status

Filter by product

1823 Ideas

plaird
Lucid Legend Level 1
plairdLucid Legend Level 1

Lucid AI changing advanced properties on SFACardsIdea

First time bug reporter. I think I am following the correct process as described in the community bug report explainer apologies if not! I asked Lucid AI to write up its own bug report on the issue it faced. Problem: Lucidchart AI Cannot Change Advanced Properties on SFACards Use CaseSetupCreate a new Lucidchart diagram In the Shape Gallery, select all 4 Salesforce architectural libraries (header, card, icons) Drag a Collapsed Card shape onto the canvas Give the card name in the text headerActionAsk Lucid AI to enable the Header icon advanced property for the card. “for the salesforce card shape, set the ‘Header icon’ property to true” It will fail. “I can’t directly toggle the ‘Header icon’ property on the Salesforce card shape via automation. You can do it manually using Shape Options” We are hoping to generate diagrams using Lucid AI. But for complex diagrams with many shapes, there will be a lot of manual fixups (header icons, footer icons, etc) which makes Lucid AI difficult to use. Lucid AI’s Self DiagnosisI asked Lucid AI why it couldn’t complete the task. After some back and forth diagnosis chatting, this is what Lucid AI reports about its failure to toggle the Header Icon toggle: Subject: SFACard advanced toggles (Header icon / Footer icons) not settable via EditBlockAdvancedProperty Summary: When working with Salesforce Architecture “SFACard” shapes, several Advanced Options toggles (notably “Header icon” and related icon/footer toggles) appear to be stored as block properties (e.g., ShowEntityIcon), but they cannot be programmatically set via the EditBlockAdvancedProperty automation API. This prevents automation from enabling header/footer icons on SFACards even though the UI supports it. EnvironmentShape: SFACard from Salesforce Architecture Diagrams library (salesforcearchitecture.js)Automation tools used: EditBlockAdvancedProperty, CanvasQuery, ShapeDetails, DocumentHistory Repro stepsCreate an SFACard and confirm Advanced Options toggles exist in UI: Advanced options: Allow nesting, Header icon, Header line, Condensed, Footer, Footer icons, etc. In the Lucid UI, toggle “Header icon” ON for a card. Observe the underlying property change captured in document history: SetProperty on the card: Property = ShowEntityIcon, Value = true (OldValue = false) Attempt to set the same property on another SFACard via automation: Call: EditBlockAdvancedProperty(ItemId=, PropertyName="ShowEntityIcon", Value="true", ValueType="boolean") Observed behaviorThe automation call fails with:“Advanced property 'ShowEntityIcon' is not registered for SFACard.” CanvasQuery (IncludeAllProperties=true) does not reliably surface these advanced-toggle properties for the SFACard instance, even after toggling them in the UI. ShapeDetails does not expose a usable, instance-specific list of registered advanced properties for SFACard (i.e., we can’t discover the correct property key(s) that are accepted by EditBlockAdvancedProperty).Expected behaviorAdvanced options toggles that are user-editable in the UI (e.g., “Header icon”, “Footer icons”) should be settable via EditBlockAdvancedProperty.At minimum, the property keys that correspond to those toggles (e.g., ShowEntityIcon) should be registered/whitelisted as advanced properties for SFACard so automation can set them. ImpactPrevents programmatic configuration of SFACard features that are important for standardized architecture-diagram generation (header icons, footer icons, potentially header line / condensed / footer toggles).Forces manual per-card UI changes, which defeats automation workflows.Evidence / notes Document history shows SFACard instances created with (non-exhaustive) SFACard-specific fields such as:ShowEntityIcon, IncludeHeaderLine, CondensedPadding, CondensedPaddingAmount, ShowFooter, FooterIconIds, SecondaryColor, AttrColumnsCount, etc.Of these, at least ShowEntityIcon clearly maps to the UI “Header icon” toggle, but it is rejected by EditBlockAdvancedProperty as “not registered.” RequestPlease confirm intended API support for SFACard advanced toggles.If supported, register/enable the relevant properties (e.g., ShowEntityIcon, FooterIconIds / Footer icons toggle, ShowFooter, IncludeHeaderLine, CondensedPadding, etc.) so they can be updated through EditBlockAdvancedProperty, and/or expose them through ShapeDetails (BlockId mode) so automation can discover valid PropertyName values.  

Potential Lucid AI agent autonomyIdea

I would like to report a behaviour I recently observed while using your Lucid AI, which may warrant further review from a security and user-safety perspective.As a new user of the platform, I generated a flowchart using the AI system. Subsequently, I asked the AI for guidance on how to download the generated file. Instead of providing instructions or directing me to the appropriate interface option, the AI automatically packaged the artefact into a ZIP file and started the download without first asking for confirmation or obtaining my explicit consent.While the file involved was one generated by the system itself and no apparent unauthorised access occurred, I believe this behaviour raises questions regarding user intent verification, autonomous action execution or excessive permission. Specifically, a request for procedural guidance ("how do I download this file?") was interpreted as authorization to perform the action on my behalf.From an AI security perspective, I would appreciate clarification on whether this behavior is expected by design. If so, it may be worth assessing whether additional confirmation mechanisms should be introduced before the system performs consequential actions, particularly in environments where broader permissions or access to user data may exist.I am not claiming this is a security vulnerability; however, I believe it may represent a potential agent autonomy or user-consent concern that deserves further evaluation.

Convert Mermaid diagrams to editable shapesIdea

Hello Lucid Support Team,I’m running into an issue with a diagram created using Diagram as Code (Mermaid) that I’m unable to resolve, and I’d appreciate guidance on whether this is a product limitation or a configuration issue.GoalI want to convert an existing Mermaid-based diagram into fully editable native Lucidchart shapes (so individual boxes, connectors, and containers can be selected and edited without touching Mermaid code).Current State The diagram was created using Diagram as Code (Mermaid). Clicking the diagram always selects it as a single object and opens the Mermaid editor. Individual shapes and connectors are not directly editable. What I’ve Tried Right-clicking the diagram and checking for: “Convert to shapes” “Detach from diagram as code” → These options do not appear. Keyboard shortcuts: Ctrl+Shift+V (Paste special) → No prompt appears; nothing happens. Copy → Paste within the same document: No option to paste as shapes. Checking top menus and contextual toolbars: No visible option to convert or detach from Mermaid. Verifying selection: The diagram always behaves as a single Diagram-as-Code object. Observed LimitationIt appears that in my Lucid environment / tenant: Mermaid diagrams cannot be converted into native shapes There is no exposed “convert” or “paste as shapes” workflow Diagram-as-Code objects are effectively locked to code-only editing Question Is this behavior expected for certain plans or tenant configurations? Is there an official way to convert Mermaid diagrams into native Lucidchart shapes in this environment? If not, is recreating the diagram manually the only supported path? I’ve attached screenshots showing: The Mermaid editor opening when the diagram is selected The absence of any “Convert to shapes” or “Paste as shapes” options Thanks in advance for your help and clarification.