1.0.7 Feedback: A Running List

Version 3

    EDIT: This list is no longer active. For bugs and features on the to-do list, please see https://github.com/tableau/VizAlerts/issues

     

     

    This is a list of all bugs, issues, feature change requests, or documentation deficiencies reported in v1.0.7 of VizAlerts, for tracking purposes. I'll keep this up to date with newly reported issues, and add notes should they be fixed in a newer version. Alongside each is who found / suggested each issue / feature request:


    Bugs:


    Functionality Changes:
     

    1. Change default hostname to localhost in vizalerts.yaml
    2. Camel-case placeholder config values in vizalerts.yaml for readability
    3. Provide a separate admin control on viz image rendering timeouts (matt c)
    4. Improve error emails by translating HTTP status codes to intelligible, actionable information (e.g., 403 = subscriber doesn't have permission, 406 = viz render failed; click this link to see error, etc) (matt c)
    5. Support plaintext email in Advanced Alerts (toby e)
    6. Support additional formats for embedded content in Advanced Alerts (csv, pdf, png, etc) (toby e)
    7. Add footer link for web editing alert viz, so long as user has permissions (matt c)
    8. Add multi-threading to support timely processing of heavy alert loads (matt c)
    9. Add support for subscribing to an entire Workbook (david l)
    10. Allow embedding of other View images in Advanced Alerts (e.g, "VIZ_IMAGE('myworkbook/view2')")  (matt c)
    11. In a single email for an Advanced Alert fails, do not stop processing remaining email (toby e)
    12. Store operational data in a structured log format and/or relational database specified by Admin (matt c)

     

    Documentation Changes: 

    1. Add quickstart guide for "just testing" on a QA server with PaperCut
    2. Expand the images in the documentation so they are more readable (toby e)
    3. Add an "advanced setup" section to the install guide. (toby e)
    4. Add instructions for increasing scalability (at least until multi-threading)