Skip to content
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

Warning message if a service is not responding or temporarily unavailable #298

Closed
brosenbaum opened this issue Jan 10, 2017 · 10 comments
Closed

Comments

@brosenbaum
Copy link
Contributor

In Flex, we had a pop-up that would warn the user of service that would be unavailable for the session based on a response status at the initial configuration xml. Since this may not be as much of an issue with JavaScript, the request is a little different:

Would like to have some warning pop-up - if a layer is selected - that the service may be temporarily unavailable if there is no response from the server.

@Baohong
Copy link
Contributor

Baohong commented Feb 8, 2017

Unavailable layers could be tested by the first 4 layers in topic "Crop Productivity".
File config.json in LocalLayer will be reversed by after testing.

@torrin47
Copy link
Contributor

torrin47 commented Feb 8, 2017

Move to Add Data Drawer, otherwise awesome!

@torrin47
Copy link
Contributor

Per client feedback - widget should have two different sections - one for enviroatlas.epa.gov services, and a second for everything else. Old flex application has boilerplate text for each. Maybe button that could trigger an email to our team with the list of problem services.

@brosenbaum
Copy link
Contributor Author

so... here's some info from the flex code. Currently not working in the latest version. The text is in the flex code...

Popup_for_missing_services.txt

@torrin47
Copy link
Contributor

torrin47 commented Mar 2, 2017

Barb is going to provide some revised text for two sections - one addressing internal services that we control and one addressing external services that we may not be able to control. Failed services should be grouped accordingly into two sections in the dialog. Notification emails are addressed in a different ticket #355

@torrin47 torrin47 modified the milestones: Milestone 31, Milestone 32 Mar 2, 2017
@torrin47 torrin47 modified the milestones: Milestone 32, Milestone 33 Mar 16, 2017
@brosenbaum
Copy link
Contributor Author

here is some text cleaned up from several versions. I put a note about the emailing, we can leave it in or take it out - I'm fine either way.

"The following web service(s) failed to load at this time and may be unavailable for this session.

For web services hosted outside of the EnviroAtlas hosting environment, EnviroAtlas is not responsible for the performance of these services:
{list of anything not https://enviroatlas.epa.gov/arcgis/rest/services or https://enviroatlas2.epa.gov/arcgis/rest/services}

For EnviroAtlas services, an email will be sent notifying administrators of these issues:
{list of all non-functioning https://enviroatlas.epa.gov/arcgis/rest/services or https://enviroatlas2.epa.gov/arcgis/rest/services}"

@torrin47
Copy link
Contributor

torrin47 commented Apr 7, 2017

Let's put this on the back burner for now, it's working pretty well as is, and we may have fewer and fewer failed layers as we clean up the config files.

@torrin47 torrin47 removed the MVP label May 24, 2017
@brosenbaum
Copy link
Contributor Author

is this still an "MVP" item?

@torrin47
Copy link
Contributor

We removed the MVP label a while back, but kept it in the backlog because external services that should have been working were not. But at this point I think it's all working, and the outstanding work on this issue was just the email functionality, which can definitely wait until after this release.

@torrin47
Copy link
Contributor

This issue was moved to USEPA/EnviroAtlas_JSApp#23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants