User Tools
development:applications:bubble_app
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:bubble_app [2021/12/13 12:33] – [Reports] 10.91.120.28 | development:applications:bubble_app [2021/12/13 14:40] (current) – [Analytical Reporting (Bubble App)] 10.91.120.28 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Analytical | + | ====== Analytical |
| Updated by Yanjun Wang 13/12/2021 | Updated by Yanjun Wang 13/12/2021 | ||
| Line 10: | Line 10: | ||
| Repo: https:// | Repo: https:// | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Access and Permissions ==== | ||
| + | |||
| + | The APP has been integrated with CAS and Userprofile. | ||
| + | |||
| + | User can visit the APP from either the button on Ticketer -> Admin Options -> Analytical Report, or link directly. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | Permission control is handled by Userprofile. | ||
| + | * System Admin: System Administrator can access all data and functionality. | ||
| + | * Supper System Admin: Supper System Administrator can access all data and functionality. | ||
| + | * End User: Application user without ability to create new user. | ||
| + | * API User: API User is allowed to access the APIs. | ||
| + | |||
| ---- | ---- | ||
| Line 66: | Line 83: | ||
| ---- | ---- | ||
| - | ==== Reports | + | ==== Impelmentation ==== |
| - | Report class has two methods. | ||
| - | * getParams to add parameters to report object sent in the request object. This report object will be returned as part of the response. | ||
| - | * Another method is the run method. This method returns the JSON string. This JSON string will be added to the report object sent in request as reportData. | ||
| - | |||
| - | Class: | ||
| * Ticket State Diagram Report: TicketStateReport.groovy | * Ticket State Diagram Report: TicketStateReport.groovy | ||
| * Ticket State Distribution: | * Ticket State Distribution: | ||
| + | |||
| + | Parameter table population is replying on QUARTZ job to run on a daily basis. The SQL query used for the corresponding table is at custom_query table. | ||
| ---- | ---- | ||
| Line 89: | Line 103: | ||
| Frontend | Frontend | ||
| * ReactJS | * ReactJS | ||
| - | * GoJS | + | * [[https:// |
| - | * amCharts | + | * [[https:// |
| * BubbleJS | * BubbleJS | ||
| Development | Development | ||
| - | * Jest | + | * Jest: helps running unit test on ReactJS Code |
| - | * Helps running unit test on ReactJS Code | + | * Storybook: helps speed up React Component Development |
| - | * Storybook | + | |
| - | * Helps speed up React Component Development | + | |
| Other | Other | ||
| * Ansible | * Ansible | ||
| Line 107: | Line 119: | ||
| Reports have the ability to connect databases via MySQL JDBC connector. For the state diagram report, it queries from key_stat table which is generated and updated by different processes that Marut introduced for Tableau. At the time of 3.11, table names that state diagram report looks up are wf_ticket_status_change and ticket_summary. | Reports have the ability to connect databases via MySQL JDBC connector. For the state diagram report, it queries from key_stat table which is generated and updated by different processes that Marut introduced for Tableau. At the time of 3.11, table names that state diagram report looks up are wf_ticket_status_change and ticket_summary. | ||
| - | For further information see requirements document[[https:// | + | ---- |
| + | |||
| + | ==== Appendix ==== | ||
| + | |||
| + | Project folder: | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | |||
| + | R&D Docs: [[https:// | ||
development/applications/bubble_app.1639398810.txt.gz · Last modified: 2021/12/13 12:33 by 10.91.120.28
Page Tools
