Save a record then revert it
Please bear with me as I try to explain the scenario. I'm looking for a couple things out of this: 1- Is the method I'm trying to implement the best way to do this, or is there a better one 2- I'm t...
Forum Discussion
What is the ultimate goal?
One user inputs what they want new values to be for a certain number of fields, but those new values do not populate until another user 'approves' the changes?
------------------------------
Mike Tamoush
------------------------------
One user inputs what they want new values to be for a certain number of fields, but those new values do not populate until another user 'approves' the changes?
------------------------------
Mike Tamoush
------------------------------
That's correct Mike.
This would be in lieu of our staff having to retype in all the information in a record to send as a notification, our staff would instead just make the change, and save the record to send to the end user. Meanwhile the record would revert back to its original values, and would get written permanently only when the user approves it via their email button. (i.e: it would then be updated with their own Quickbase user, for auditing purposes)
With that said, I think I got it resolved. I will do some more testing, but, in case someone else might have a similar scenario.
What I did is I removed the second (Revert) part of the formula, and I created a Pipeline to trigger on the record if the field "Staging" is checked, (and if the modified date is within 5 minutes, for good measure)
Then I used the values in there to get the previous value {{a.$prev.First Name}} , etc...
This seems to have worked like a charm!
Thanks!
------------------------------
George Khairallah
CTO
gotomyerp, LLC
------------------------------
This would be in lieu of our staff having to retype in all the information in a record to send as a notification, our staff would instead just make the change, and save the record to send to the end user. Meanwhile the record would revert back to its original values, and would get written permanently only when the user approves it via their email button. (i.e: it would then be updated with their own Quickbase user, for auditing purposes)
With that said, I think I got it resolved. I will do some more testing, but, in case someone else might have a similar scenario.
What I did is I removed the second (Revert) part of the formula, and I created a Pipeline to trigger on the record if the field "Staging" is checked, (and if the modified date is within 5 minutes, for good measure)
Then I used the values in there to get the previous value {{a.$prev.First Name}} , etc...
This seems to have worked like a charm!
Thanks!
------------------------------
George Khairallah
CTO
gotomyerp, LLC
------------------------------
- You could also make a new form with new fields (named on the form the same as the old fields for the users ease). Call them Proposed New Field 1, Proposed New Field 2, etc.
On your main form just have a button that says enter new proposed values. All that does is take you to a new form where they edit the values. Save and have something trigger the notification.
If the values are approved, THAT button will change the values of the original.
You could even have the first button click check a box that says something like 'Changes Pending', and then the approval button click uncheck that box. You can use that changes pending checkbox in a formula rich text or dynamic field to show on the main form when changes are pending.
------------------------------
Mike Tamoush
------------------------------- Ah.. awesome! that's a great idea too.
So I think if I understand you correctly, the initial button would take the user to the new form, AND populate it with the existing values from the original fields, and then the staff member can make any necessary changes, which will then get sent to the user for the approval step.
Did I get this right?
I think I will see if the delay in triggering the pipeline will create any workflow issues for our team (i.e: the waiting game for the record to revert back). If it doesn't, then what I have might work, otherwise, I might implement your suggestion. It's a good one even though it doubles the number of fields in my table :)
Thanks Mike!
------------------------------
George Khairallah
CTO
gotomyerp, LLC
------------------------------- Actually, that's not what I originally wrote (about initial button populating existing values), but yes that is a good idea lol.
Yes, it will double the number of fields though (or at least add in as many fields that can be changed). There may be an even better idea but that is all I could think of for right now!
------------------------------
Mike Tamoush
------------------------------
