replied on April 26, 2021
Just thought of another way to do this.
Instead of adding the Redtail list to your metadata field directly, you could instead build the entire metadata template out as a form. Create a process and build the starting form to have the same fields as your metadata template. You can set up an application connection lookup rule to fill the form field with your Redtail clients. This should give the form the exact experience you are looking for in the metadata pane.
In the repository, you can use custom metadata panes to show the form in the web client right pane. Instead of users interacting with the metadata fields directly, they will interact with the starting form.
Some notes about the business process behind the form:
- Instead of showing the thank you page after submission, redirect back to the starting form URL so the form just shows up again (like the metadata pane would)
- The form should have a hidden field that's filled via URL parameter with the selected entry ID. That way, each submission knows which document metadata needs to be modified. You can use the field picker in the custom tab configuration to insert the starting form URL and the entry ID as a parameter.
- After submission, run a workflow service task with the entry ID to update that document's metadata.
To recap:
- Build a form with the application connection to Redtail
- Embed the form next to the documents in the repository
- Have the form submission update the actual document metadata