Hi @Kiersten_Kollin, we've been running a similar workaround, ironically also for designers. This seems complex - 90% of the complexity stems from the initiators of the re-request being outside of the base ecosystem - but it should work following the setup.
There are five big components that will need to be introduced to the ecosystem:
- A view-only grid of the Retouchers Base for the Graphic Designers to see.
- A new "re-open" button field that, when clicked, opens the form and prefills any pertinent information.
- A new linked record field that will connect the re-opened requests to the original requests.
- A new "re-opened" checkbox field that will check itself via automation on the original request when a re-opening request is submitted.
- An automation that checks that checkbox field.
Before I describe these components specifically, the workflow would be as follows: designers would look through the shared view to find a request they want to resubmit. They would click on the "re-open" button for that request, which would take them to a form prefilled with the information from the initial request, and also with a prefilled (optimally hidden) record link via a linked record field. Upon submission of the form, an automation would run that would use that linked record to locate the original request and check its "re-opened" checkbox. From here, it would simply be a matter of filtering the Retouchers base to exclude requests with the "re-opened" checkbox checked.
Let me know if that makes sense - wouldn't want to dive into ultra-specifics if this is enough to get you started!