Lucid Custom Shape Library - BPMN objects

Following is the additional info to go on the BPMN task object:

Hi Richard - OOTB functionality if at all possible maybe via formulas etc.

Please advise

Addendum: Richard I may be interested in API questions per some other functionality we are seeking. Can you advise on this? is there a DEVOPS guide for Lucid? are the customizations implemented in the backend web services environment or as jscript on the client side of the SaaS platform?

Please advise

Hey John! These are very good questions and thanks for your work. We unfortunately don't currently have a way to extend an existing Lucidchart shape via our Extension API.

I would love to get feedback on your ideas and see what we can support. I have your email from the Extension API Beta submission. Will follow up there

Ibaenzinger - thanks for your reply. That is unfortunate. I realize on an SaaS platform one cannot directly affect the functionality of a platform (ie: Visio + VBA) as one would in a desktop application. However there are some capabilities that could be significantly enhanced and/or extended via custom coding that may well lead to product enhancements adopted by Lucid to the benefit of both the product portfolio and user community.

Just a thought.

Hi Ian a thought.

Can sub-shapes within an shape/object group be "turned on/off" (made visible or invisible) based on metadata settings? I'm thinking of an alternative to the task-type and activity-marker symbols.

Thanks

Hi Ian thanks for the update. Please help me understand where to implement. Searching formulas there are no functions for "geometry" "type" or "condition". I assume one must inspect the page and update? How does this become persistent with a custom object in the Lucid repository?

Thanks

I believe I misunderstood how you were implementing the library. It looks like you're trying implementing the shapes in code (via an editor extension).

We have separate functionality to build a more traditional shape library on the Extension API. This allows you as a developer to define shapes in an extension/app. When a user installs the app they will be able to add the shapes to the canvas like they would with a typical Lucidchart shape (e.g. shapes appear in left hand panel and user can drag onto canvas to create an instance of the shape). That documentaiton is here.

We've never actually had a developer try to implement shape library functionality via an editor extension (e.g. a script). I'd recommend against it as it's not how we've designed the API. But of course how you build is up to you and happy to answer questions as they come up!