The log dashboard enables you to understand all the activities in the system.
Field name | Type | Definition | Main relationships with other tables |
---|
id | text | Primary key for the table log_all | |
client_id | text | This field is not maintained anymore | |
client_name | text | This field is not maintained anymore | |
timestamp | timestamp | Server time (time when the action is registered in the log at the time of the server) | |
bi_timestamp | timestamp | Local time (time when the action is made at the local time) | |
last_synchro | timestamp | Last time the mobile user synchronised before doing the action | |
system_action | boolean | True= The action has been automatically triggered by the system False=The action has been manually triggered by the user | |
user_id | text | User id | = mobile_users.id =teams_mobile_users.user_id |
user_type | text | MOBILE = the action has been made on the mobile WEB = the action has been made on the webapp | |
user_name | text | Name of the user as registered at the time of the action | |
user_phone | text | Phone of the user as registered at the time of the action | =mobile_users.phone (except if the phone number has changed) |
user_email | text | Email of the user as registered at the time of the action | |
action_code | text | The main options are: - ARCHIVE_DASHBOARDS: archive multiple dashboards (by selecting a group of items and doing an edit action) ARCHIVE_ITEM: archive a single item ARCHIVE_ITEMS: archive multiple items (by selecting a group of items and doing an archive action) ARCHIVE_LIST: archive a single list ARCHIVE_TEAM: archive a single team ARCHIVE_TEAMS:archive multiple items (by selecting a group of items and doing an archive action) ARCHIVE_WORKFLOW: archive a single item ASSIGN_ITEM: assign a single item ASSIGN_ITEMS:assign multiple items ASSIGN_MOBILE_USERS_TO_TEAMS CHECK_IN: check-in on the mobile app CHECK_OUT:check-out on the mobile app CREATE_DASHBOARD: create dashboard CREATE_ITEM: create a single item CREATE_ITEMS:create multiple items CREATE_LIST: create a single list CREATE_MOB_USER:create a single mobile suer CREATE_MOB_USERS: create multiple mobile users CREATE_SUBMISSION:create a single submission CREATE_TEAM: create a single team CREATE_TEAMS: create multiple teams CREATE_WEB_USER: create a single web user CREATE_WEB_USERS:create multiple web users CREATE_WORKFLOW: create a single workflow DELETE_ITEM: delete a single item DELETE_ITEMS: delete multiple items DELETE_MOB_USER: delete a single mobile user DELETE_MOB_USERS: delete multiple mobile users DELETE_SUBMISSION:delete a submission DELETE_TEAM: delete a single team DELETE_TEAMS: delete multiple teams DELETE_WEB_USER: delete a single web user DELETE_WEB_USERS:delete multiple web users EDIT_DASHBOARD: edit a single dashboard EDIT_GPS: edit the gps coordinates in the place list EDIT_ITEM: edit a single item EDIT_ITEMS:edit multiple items EDIT_LIST: edit a list EDIT_MOB_USER:edit a single mobile user EDIT_MOB_USERS:edit multiple mobile users EDIT_SUBMISSION: edit a single submission EDIT_TEAMS: edit a single team EDIT_TEAMS: edit multiple teams EDIT_WEB_USER: edit a single web user EDIT_WORKFLOW: edit a single workflow LICENSE_MOB_USER: license a single mobile user LICENSE_MOB_USERS: license multiple mobile users LOGIN: the user has logged in OTP: an OTP has been requested by the user RECORD_USER_LOCATION: user location has been automatically captured on mobile RESET_PASSWORD: reset the web user password on the profile module RESTORE_ITEM:restore a single archived item RESTORE_ITEMS: restore multiple archived items RUN_DASHBOARD: open the dashboard or apply some filters on a dashboard RUN_STREAM: run a stream UNLICENSE_MOB_USER: unlicense a single mobile user UNLICENSE_MOB_USERS: unlicense multiple mobile users UPLOAD_FILE_FOR_ITEM: have an attachement for an item, for example a picture for an item in a list UPLOAD_FILE_FOR_SUBMISSION: have an attachement for a submission, for example a picture for a workflow question UPLOAD_FILE_FOR_WORKFLOW: have an attachement for a workflow, for example a picture for a workflow
More details here | |
status | text | The main options are: ERR: The action has not been proceeded successfully SUCC: The action has been successfully made NALW: The user is not allowed to do this action, the user does not have enough rights, or the action is not possible to do NUTD: The resource is not up to date and the user needs to sync before doing this action. For example, if the item has been modified on the webapp and the user has not sync yet. RIBG: Run in Background PSUC: The action has been partially completed (for example when there is bulk operation, only a few items have been edited/created/… successfully) ITOP: Invalid OTP UNFD: The user (who is trying to do the action) not found LNVD: The mobile user license is not valid TCHG: The team has changed and the user needs to sync ALGI : The user is already logged in
More details here | |
response | text | More details on the response. It can be useful when the status='ERR' to get more information on the issue. | |
workflow_id | text | Workflow id when the action_code is related to a workflow (For example for action_code=CREATE_SUBMISSION or EDIT_SUBMISSION or CREATE_WORKFLOW or EDIT_WORKFLOW) | =workflows.id |
dashboard_id | text | Dashboard_id when the action_code is related to a dashboard (For example for action_code=CREATE_DASHBOARD or EDIT_DASHBOARD or RUN_DASHBOARD) | =dashboards.id |
list_id | text | Submission_id when the action_code is related to a list (For example for action_code=CREATE_SUBMISSION or EDIT_SUBMISSION) | =lists.id |
place_id | text | Submission_id when the action_code is related to a place (For example for action_code=CHECK_IN or CHECK_OUT) | =l_place._id |
submission_id | text | Submission_id when the action_code is related to a submission (For example for action_code=CREATE_SUBMISSION or EDIT_SUBMISSION) | =w_<workflowid>._id |
data | text | The data that has been submitted. For example, the submission data when the action_code is related to a submission | |
old_data | text | The data that has been replaced when there is an edition. For example, the old data when the action_code is related to an item edit | |
visit_id | text | The visit_id is a key to gather all the actions made between a CHECK_IN and a CHECK_OUT It will be the same for: 1. The check-in (action_code=CHECK_IN) 2. All the submissions made (action_code=CREATE_SUBMISSION) 3. The check-out (action_code=CHECK_OUT) | |
mobile_app_version | text | When the user_type='MOBILE', the version of the mobile app used at the time of the action | |