Webscreen 3.0 - any news?

[DavidYoung]

@PaddyNewman, I think we've found a bug in Webscreen 3 which really confused us. We were trying to run an IP-based report and getting no data in the report. Turns out we had the wrong school selected at the top of the page but we were trying to report on an address in a different school. The system should probably warn or prevent you from entering an IP address that doesn't belong to the selected school.

[JohnJackson]

David, I've also brought this to the notice of Atomwide. Great feedback.

[PaddyNewman]

@PaddyNewman, I think we've found a bug in Webscreen 3 which really confused us. We were trying to run an IP-based report and getting no data in the report. Turns out we had the wrong school selected at the top of the page but we were trying to report on an address in a different school. The system should probably warn or prevent you from entering an IP address that doesn't belong to the selected school.

Hi David,

 

Looking at this now for you. Thanks for making me aware!

[PaddyNewman]

@DavidYoung @JohnJackson a fix is being looked at now, you do get empty reports (logically correct as it's per establishment) but as there is no prompt regarding the establishment it makes it problematic.

 

I'll update you asap!

[DavidYoung]

Thanks @PaddyNewman. Overall Webscreen 3 looks pretty good. We're not making much use of it because of Freedom2Filter but there are some UX scenarios where I think Webscreen 3 works better like being able to see a list of which policies each category is assigned to easily.

[PaddyNewman]

@DavidYoung we've pushed out a change regarding validation. Can you cast your eye over, enter an incorrect IP and let me know how you find that.

 

Thanks for the feedback regarding the UX. I've fed this to our teams also!

Edited May 8, 2019 by PaddyNewman

[DavidYoung]

@DavidYoung we've pushed out a change regarding validation. Can you cast your eye over, enter an incorrect IP and let me know how you find that.

 

Thanks for the feedback regarding the UX. I've fed this to our teams also!

 

Thanks Paddy. This does seem to correctly block us from using the wrong IP now.

[PaddyNewman]

Great news! Thanks for pointing that out.