Member Tickets
Â
The following describes the member tickets table.
Name | Description | Example |
---|---|---|
ticketid | This is the unique ticket id for this ticket |
|
status | The current status of the ticket.
|
|
personid | The unique id for the person for this ticket. This can be linked to people table. |
|
formdata | This is the JSON object that contains the form data that was entered into the form. Â |
|
ticketentry | Information about how this ticket was created. |
|
person | This is the person’s name |
|
assignedto | The social navigator that this ticket is assigned to. |
|
updateddate | The date that this ticket was last updated |
|
createddatetime | The time that this ticket was created. This is in epoch format |
|
referralid | This will be the service request id that was created when the service request was submitted to CIE hub and that was shared with the service organization when the service request was forwarded to them. |
 |
logs | This is a array of JSON objects that contains information about actions that have been taken on this member ticket. It includes attempt logs, appointment logs, assignment logs, and assessement logs. Please note below we have a view to get data out of the attempt logs |
|
Â
MemberTicket Attempts View
This is a cross join of the logs to get the attempts.
Name | Description | Example |
---|---|---|
ticketid | *See Above in the main table | Â |
status | *See Above in the main table | Â |
closereason | This is reason that the ticket was closed |
|
referralid | *See Above in the main table | Â |
personid | *See Above in the main table | Â |
person | *See Above in the main table | Â |
attempt_datetime | The date and time the attempt was made | Â |
attempt_log | Information about the attempt | Â |