[Solved] Diagram component - usage scenarios

[Rob]

Wondering if the new Diagram component will satisfy feature requirements we have for our application:

1.  Admin/Developer builds a Diagram and saves to JSON text and puts that in SQL database (Table/Field json or nvarchar(max)) which is then loaded by end user in app.

2.  Some shapes in the diagram will be read only, can't be modified.

3.  Restrict what type shapes can be added and provide default size of shape.

4.  Shapes contain an image (as background).

5.  User clicks on shapes within the Diagram and event fires and we do stuff (execute code, get data, make visible another component, etc.)

6.  Or User links shapes but can't modify the shape/contents but can establish links between shapes (that we can respond to and update back end database) ... an event link connection trigger.

7.  User can save the connections/layout.

Viable?

Rob.

 

[Dimo]

Hello Rob,

So far I don't see any blockers in the described requirements. The following documentation content is the most relevant:

• Define Diagram Shapes and Connections in JSON
• Diagram Events
• Persist user changes in the Diagram and apply them to the component in a future user session

Regards,
Dimo
Progress Telerik