User Tools
support_request_application_database_tables
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| support_request_application_database_tables [2023/06/23 13:56] – 10.91.129.7 | support_request_application_database_tables [2023/06/27 16:43] (current) – 10.91.110.100 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| **Support Request Application Config Tables** | **Support Request Application Config Tables** | ||
| + | |||
| + | [[https:// | ||
| **config_entry** | **config_entry** | ||
| Line 27: | Line 29: | ||
| |22|Support Request Form POC Field Name|REQUEST_POC_FIELD|customer_contact|Customer Update Form| | |22|Support Request Form POC Field Name|REQUEST_POC_FIELD|customer_contact|Customer Update Form| | ||
| |23|Support Request Form Billable Field Name|REQUEST_BILLABLE_FIELD|billable|Where the billable status is pulled from ( Support Request Details)| | |23|Support Request Form Billable Field Name|REQUEST_BILLABLE_FIELD|billable|Where the billable status is pulled from ( Support Request Details)| | ||
| - | |24|Indicate if the environment is for multiple customers.|MULTI_CUSTOMER_ENV|TRUE|| | + | |24|Indicate if the environment is for multiple customers.|MULTI_CUSTOMER_ENV|TRUE|If true then logic to limted what user sees will be determined by thier access such as emails and tickets| |
| |25|Support Request Form Last Update Field Name|REQUEST_LAST_UPDATE_FIELD|latest_update|This reads the latest update field (ticket_update)| | |25|Support Request Form Last Update Field Name|REQUEST_LAST_UPDATE_FIELD|latest_update|This reads the latest update field (ticket_update)| | ||
| - | |26|Customer - Workflow Status that indicating the ticket is either resolved or cancelled.|CLOSED_STATUSES|Resolved, | + | |26|Customer - Workflow Status that indicating the ticket is either resolved or cancelled.|CLOSED_STATUSES|Resolved, |
| |27|Resolution Form Name|RESOLUTION_FORM_NAME|Resolution Form|Form that is used for the Resolution tab| | |27|Resolution Form Name|RESOLUTION_FORM_NAME|Resolution Form|Form that is used for the Resolution tab| | ||
| |28|Resolution Form Work Details|RESOLUTION_DETAILS_FIELD|work_details|Form that is used for the Resolution tab| | |28|Resolution Form Work Details|RESOLUTION_DETAILS_FIELD|work_details|Form that is used for the Resolution tab| | ||
| |29|Resolution Form Date Resolved|RESOLUTION_DATE_FIELD|date_resolved|Form that is used for the Resolution tab| | |29|Resolution Form Date Resolved|RESOLUTION_DATE_FIELD|date_resolved|Form that is used for the Resolution tab| | ||
| |30|List all the users have permission to access My Company page(split by comma)|ADMIN_USERS|User ids |Used to be used to determine of user can see the My Company option| | |30|List all the users have permission to access My Company page(split by comma)|ADMIN_USERS|User ids |Used to be used to determine of user can see the My Company option| | ||
| - | |31|Support Request Form Company Field Name|REQUEST_COMPANY_FIELD|sco_company|Used on multi Tenant ( SCO) environment , on ticket create uses customers company details and adds it to the sco_company field on the support request details | + | |31|Support Request Form Company Field Name|REQUEST_COMPANY_FIELD|sco_company|Used on multi Tenant ( SCO) environment , on ticket create uses customers company details and adds it to the sco_company field on the support request details |
| - | |32|System admin user email regex which allow to access all SCO tickets regardless company.|SYS_ADMIN_EMAIL| see db for value|System admin user email regex which allow to access all SCO tickets regardless company.| | + | |32|System admin user email regex which allow to access all SCO tickets regardless company.|SYS_ADMIN_EMAIL|see db for value|System admin user email regex which allow to access all SCO tickets regardless company.| |
| |33|Customer - Workflow Pending Approval Status|PENDING_APPROVAL_STATUS|Pending Approval|Status that determines if the approval billable hours is visible on the Customer Update form| | |33|Customer - Workflow Pending Approval Status|PENDING_APPROVAL_STATUS|Pending Approval|Status that determines if the approval billable hours is visible on the Customer Update form| | ||
| |34|Customer Update Form Request Ticket to Approve Billable Hours|CUSTOMER_UPDATE_FORM_BILLABLE_APPROVED|billable_approved|Relates to the Customer Update form| | |34|Customer Update Form Request Ticket to Approve Billable Hours|CUSTOMER_UPDATE_FORM_BILLABLE_APPROVED|billable_approved|Relates to the Customer Update form| | ||
| Line 56: | Line 58: | ||
| |id|config_json|request_name|Used For| | |id|config_json|request_name|Used For| | ||
| - | |1||General Support Request|Display name is shown on the My Ticket , My Company page Request name is shown on drop down on ticket submit form config json is how the questions are configured| | + | |1|see db for value|General Support Request|Display name is shown on the My Ticket , My Company page Request name is shown on drop down on ticket submit form config json is how the questions are configured| |
| - | |2||New Report Request|Display name is shown on the My Ticket , My Company page Request name is shown on drop down on ticket submit form config json is how the questions are configured| | + | |2|see db for value|New Report Request|Display name is shown on the My Ticket , My Company page Request name is shown on drop down on ticket submit form config json is how the questions are configured| |
| - | |3||Improvement Request|Display name is shown on the My Ticket , My Company page Request name is shown on drop down on ticket submit form config json is how the questions are configured| | + | |3|see db for value|Improvement Request|Display name is shown on the My Ticket , My Company page Request name is shown on drop down on ticket submit form config json is how the questions are configured| |
support_request_application_database_tables.1687525013.txt.gz · Last modified: 2023/06/23 13:56 by 10.91.129.7
Page Tools
