I agree completely... Some way to make them stand out is an outstanding ideaSwenVandenberk wrote:Maybe, but an app closure is usually not complete, maybe one or two segments are reported while other segments stay open. Plus they do not stand out from other closures which are entered in WME and which most likely are complete.taco909 wrote: That function should be there.
Pending closures (those not yet active due to schedule, or those entered from the app by a low-level user and not yet confirmed) display in the WME closures layer with a grey icon.
Active closures show with a red icon.
Opening the closure option on the segment (L4+) will show if it is a 1-way or a 2-way, the person reporting the closure (if L1/2/3 then the closure came from the app since they do not have access to RTC)
The end date is often "1969" or some other date that makes no sense.
But I agree that having something more clearly displayed in WME as to whether the closure is from the app and not yet confirmed, or from the RTC system is a good idea.
That suggestion is to make clear in WME that an editor needs to take a closer look and complete the closure in that area.
To add...
If an L4 or L5 editor adds an in-app closure to a segment locked above their level, it would be nice for them to be able to manually adjust that closure rather than having to seek out an unlock.
Sometimes I'll drop a closure, or see something that might warrant a UR, and if I have my notebook or tablet with me, I'll tether it to my phone and try to make the changes immediately on the side of the road.
Re: WME v1.10 Release - Official Feedback Thread