Ticketing system replica, is it possible?

[ALBJORGUI]

I have been having issues trying to create something that resembles a ticketing system for my organisation.

So, the way I have imagined it is:

I have a feature service made of one feature layer and one table. There is a 1:M relationship so I can have as many entries on the table related to one entry on the feature layer.

In experience builder I imagined the following workflow:

One column on the left has a widget list with  the ticket itself, and the column on the right another list widget that shows the comments from the table.

I had also imagined to Edit widgets, one that allows the user to add a new ticket and a second one that allows the user to add new records to the relationship class.

In an ideal world, the globalId to parentId transaction would happen when the user selects an existing ticket, and then presses the edit for the comments and it would magically populate the parentid field.

Am i completly out of my mind? Has anyone ever attempted to create something like this?

Any help will be greatly appreciated.

[ShengdiZhang]

Hi @ALBJORGUI ,

Editing related records is supported by the Edit widget, and you can find details at: https://doc.arcgis.com/en/experience-builder/latest/configure-widgets/edit-widget.htm#GUID-7D3B4D8A-... 

Besides, in the left list widget, you can add the following message action: Record selection changes - Data - Filter data records, and use the layer's relationship to build the connection. In this way, if a ticket is selected from the left list, the right list will be filtered to show only comments from that ticket.

Please let me know if you have other questions.

Thanks,

Shengdi