Logging Activity: Difference between revisions
Jump to navigation
Jump to search
(Created page with "nuBuilder Forte can track when records are... *Added *Accessed *Edited and by whom. This information is stored as a JSON string in a field named by joining the table name ...") |
No edit summary |
||
| Line 7: | Line 7: | ||
and by whom. | and by whom. | ||
Simply add a varchar(1000) and nuBuilder Forte will start logging activity to each record in that table. | |||
This information is stored as a JSON string in a field named by joining the table name with '_nulog' eg. '''customer_nulog''' | This information is stored as a JSON string in a field named by joining the table name with '_nulog' eg. '''customer_nulog''' | ||
You can use a version of the SQL below to create the nulog field. | and looks like this... | ||
{ | |||
"added": { | |||
"user": "globeadmin", | |||
"time": 1513706208 | |||
}, | |||
"viewed": { | |||
"user": "globeadmin", | |||
"time": 1513706208 | |||
} | |||
} | |||
You can use a version of the SQL below to create the nulog field (change aaa to your table name). | |||
ALTER TABLE `aaa` ADD `aaa_nulog` VARCHAR(1000) NOT NULL | ALTER TABLE `aaa` ADD `aaa_nulog` VARCHAR(1000) NOT NULL | ||
Revision as of 19:59, 19 December 2017
nuBuilder Forte can track when records are...
- Added
- Accessed
- Edited
and by whom.
Simply add a varchar(1000) and nuBuilder Forte will start logging activity to each record in that table.
This information is stored as a JSON string in a field named by joining the table name with '_nulog' eg. customer_nulog
and looks like this...
{
"added": {
"user": "globeadmin",
"time": 1513706208
},
"viewed": {
"user": "globeadmin",
"time": 1513706208
}
}
You can use a version of the SQL below to create the nulog field (change aaa to your table name).
ALTER TABLE `aaa` ADD `aaa_nulog` VARCHAR(1000) NOT NULL