Qrew LegendYes, you can use a pipeline but a far better solution is to reconsider your approach.
The best practice here is really to have a status field on the record and then have different reports and different notifications and subscriptions based on that status field. You will likely regret it in the end if you start making Duplicate tables. For example, if you decide to add a field to your form in one table, then you are going to need to add that field into other tables and keep the forms consistent.
Thanks Mark
I do understand your point, but in a sense, I am looking to save it almost like an audit table. You are correct, if we do make a change to the primary form, we may need to change a field on one or both of the "audit" tables, but I am looking to protect against if we needed to make significant changes to the table/form. At that point, the records in the audit table would technically be frozen as they were at the time they were approved. This is a small form/table so maybe it's not worth it here. If we were to make a significant change, maybe a new app might make sense.
