Using a logged field for the approval process might not be the best solution. Generally speaking, I structure this type of process in 1 of 2 ways.
- For each Role / Person that must approve the record, create both an Approved By user field and an Approved Timestamp date/time field. You can then create a checkbox or button that would fill these fields based on Form Rules, Actions, or the API
- Create a child table for Approvals, where each Role / Person would have what would essentially amount to an Approval Task. These would then have Assigned To, Status, Status Timestamp, Notes, etc.
Regarding the dual workflow for the Projects, I think keeping both workflows on the same form is probably the best option at this point. You're right in thinking that creating a 2nd form would be a nightmare, unless the workflow can be differentiated by Role, though it doesn't sound like that's the case.
Another - even
more complicated - option might be to split the workflow into 2 tables. I realize this seems counter-intuitive, but you would be able to completely separate things in this way. If I were to do that type of setup, I would make a copy of the Projects table and I would create a new table that would act as a Parent to both of the Projects tables, aggregating the information on the Projects and giving your users a single place to view Project info. You could then have a button for users to click that would open the correct record in the correct table in Edit. This isn't an ideal setup, but it's possible this might work for what you're trying to do.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quickbase Solution Provider
Atlanta GA
404.800.1702 /
http://datablender.io/------------------------------
