-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for using Reports as Data Source for Outputting to Devices #2
Comments
As discussed, i'll take this one and implement to support our 'Opportunity (or Sales) Progress Tracker' demo at DF15. |
Here is the original blog from @corycowgill. I'll take the code from this an make it declarative! 👍 |
Ok made an initial commit, more work on tests before packaging, but its mostly in place for demo. Will need trigger validations in due course, e.g. to check report exists etc. Would like to improve the UI as well, to let users pick from a custom UI the parts of the report to map to the device outputs, but i'm getting ahead of myself for Dreamforce deadline a bit here! |
Done! 👍 |
Added in release v1.12 |
Based the work of @corycowgill implement a #clicksnotcode means to attach Report details and map to a device output. Using the Analytics Apex API and a Scheduled job.
Perhaps create a LittleBits Report Trigger object to allow the user to define the report and mappings from its output to the device output through fields. Then have a scheduled job to read LittleBits Report Trigger records to process.
The text was updated successfully, but these errors were encountered: