admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2020-09-14 18:39:33 +00:00
parent 8105677a14
commit 77d030e04b
2 changed files with 2 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
ayanova/devdocs/todo.txt
View File

@@ -3,28 +3,15 @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
todo: Need client to accept an open object url which directly opens a report
This is becuase Notification will send a link to a Customer with a workorder or quote to be rendered for them
There will be an object type, object id and report id
object type will initially only ever be a workorder or a quote to support customer notification
(And a Widget for testing)
However, there is likely no reason not to support any report and any type of object in the client code in case it is useful to support a feature down the road
since there would be little difference between supporting this for wo and quote and any other object
This should be sent to the server directly to render the report in the current user's Client browser context
So they would click on a link in an email and be taken to login and then directly to previewing the report
URL: 404 - Object not found: "/viewreport/2/100/1" /viewreport/objecttype/:objectid/:reportid
http://localhost:8080/viewreport?oid=100&rid=1
todo: export from grid to xls, csv etc. todo: export from grid to xls, csv etc.
I'm thinking perhaps also a secondary ability to make report templates that are actually intended for export to xls or whatever as an additional feature I'm thinking perhaps also a secondary ability to make report templates that are actually intended for export to xls or whatever as an additional feature
but the easiest thing for people would be a straight export of grid data from grid, perhaps using the reportdata system since it pulls in all the bits needed for full data rather than just id links but the easiest thing for people would be a straight export of grid data from grid, perhaps using the reportdata system since it pulls in all the bits needed for full data rather than just id links
https://www.npmjs.com/package/json-2-csv https://www.npmjs.com/package/json-2-csv
Is the report list filtered by roles? It should not present reports that a user is not permitted to use by role. todo: Is the report list filtered by roles? It should not present reports that a user is not permitted to use by role.
probably need to post-process the report list or include the roles with it and then test them at the client before displaying or at the server before sending probably need to post-process the report list or include the roles with it and then test them at the client before displaying or at the server before sending
Add sanitize html for Marked markdown helper as in Wiki control todo: Add sanitize html for Marked markdown helper as in Wiki control
TODO: Report confirmation checklist TODO: Report confirmation checklist

9
ayanova/src/components/report-selector-control.vue
View File

@@ -154,21 +154,12 @@ export default {
this.reportList = res.data; this.reportList = res.data;
} }
//TESTING generate extra items
// for (let x = 20; x < 60; x++) {
// this.reportList.push({ name: "REPORT NAME HERE", id: x });
// }
this.isVisible = true; this.isVisible = true;
return new Promise((resolve, reject) => { return new Promise((resolve, reject) => {
this.resolve = resolve; this.resolve = resolve;
this.reject = reject; this.reject = reject;
}); });
}, },
// ok() {
// this.isVisible = false;
// this.resolve(this.selectedReport);
// },
cancel() { cancel() {
this.isVisible = false; this.isVisible = false;
this.resolve(null); this.resolve(null);