Hello!
Assuming that we have a system with Chronoconnectivity v5 and our users can view a list of database and they can edit all the information using a connection with Chronoforms v5...
¿How can I create a "log" with the changes that users does into this database?
For example, an user edits 2 of the 5 boxes throught the connection (chronoforms). In this case I need to save that the user with nick "xxxx" has change "box2" and "box3", putting this information: "xxxx(box2)" "xxxxx(box3)".
Can we do that?
>> I was thinking and the only solution that I have in mind is this one:
1- Into the edit form (chronoforms) put javascript code that duplicates the loaded information into "temp variables".
2- When the users clic on "send" button, compare the temp variables with the real variables (also with javascript.
3- For ones which are different, put into new "log variables"
4- This new-variables will be saved into another database putting "save database" action in the setup of chronoforms, before connection action of chronoconnectivity.
But this is a rudimentary process....
Could we optimize?
Assuming that we have a system with Chronoconnectivity v5 and our users can view a list of database and they can edit all the information using a connection with Chronoforms v5...
¿How can I create a "log" with the changes that users does into this database?
For example, an user edits 2 of the 5 boxes throught the connection (chronoforms). In this case I need to save that the user with nick "xxxx" has change "box2" and "box3", putting this information: "xxxx(box2)" "xxxxx(box3)".
Can we do that?
>> I was thinking and the only solution that I have in mind is this one:
1- Into the edit form (chronoforms) put javascript code that duplicates the loaded information into "temp variables".
2- When the users clic on "send" button, compare the temp variables with the real variables (also with javascript.
3- For ones which are different, put into new "log variables"
4- This new-variables will be saved into another database putting "save database" action in the setup of chronoforms, before connection action of chronoconnectivity.
But this is a rudimentary process....
Could we optimize?
Hi Kronosites,
I think you are on the right track but I'd do this with PHP in the On Submit event of the form. Reload the record being edited using a DB Read action with a Model ID. Compare those results, unset any that match and update the others, then save to your log table.
Bob
I think you are on the right track but I'd do this with PHP in the On Submit event of the form. Reload the record being edited using a DB Read action with a Model ID. Compare those results, unset any that match and update the others, then save to your log table.
Bob
This topic is locked and no more replies can be posted.
