Anyone here work in an environment where if a ticket's Approval is rejected, it gets sent back to the submitter for a "rework" and resubmitting that same ticket record? Im used to just telling the user to submit a new ticket with the proper information but I dont have that choice here.
The issue is because I use a record producer, the user will have to update entries in the question_answer table. For my use case, because there's a dedicated table with dedicated fields for this ticket type, I just use the Form widget to allow the user to modify and resubmit. The issue with this is that OOTB the Portal is designed with Catalog Items in mind for things like Ticket Details and Approvals showing the Variable/Option values. So even if the user updates the ticket's fields, the variables are still showing the initial data.
I was wondering if there's a better way to handle this scenario that Im not seeing. I could completely go full Form eventually and just not deal with record producers. Ill still have to update the widgets that display the variable data and replace it with something useful. But then I lose functionality like Multi-Row Variable Sets...
