Difference between revisions of "User talk:SBS8478D"
Jump to navigation
Jump to search
m |
m |
||
| Line 1: | Line 1: | ||
==August 2015== | ==August 2015== | ||
<blockquote>"1.4. '''When updating de-registered buses, they are to be updated after 2359 hours of the actual de-registration date of the bus.''' They are not allowed to be updated before the timing as the list will be reverted back if it is updated too early or before the stipulated time. For buses that are awaiting de-registration prior to de-registration, only reflect the status as "Awaiting de-registration" when there's confirmation based on the physical evidence."<blockquote> | <blockquote>"1.4. '''When updating de-registered buses, they are to be updated after 2359 hours of the actual de-registration date of the bus.''' They are not allowed to be updated before the timing as the list will be reverted back if it is updated too early or before the stipulated time. For buses that are awaiting de-registration prior to de-registration, only reflect the status as "Awaiting de-registration" when there's confirmation based on the physical evidence."</blockquote> | ||
==Reply== | ==Reply== | ||
Searching of past deployment are available through past deployment of bus model. I can assure you it is much faster this way than to manually retrieve past deployment of a single service by going through the 3000+ history for it. | |||
Revision as of 07:22, 5 November 2017
August 2015
"1.4. When updating de-registered buses, they are to be updated after 2359 hours of the actual de-registration date of the bus. They are not allowed to be updated before the timing as the list will be reverted back if it is updated too early or before the stipulated time. For buses that are awaiting de-registration prior to de-registration, only reflect the status as "Awaiting de-registration" when there's confirmation based on the physical evidence."
Reply
Searching of past deployment are available through past deployment of bus model. I can assure you it is much faster this way than to manually retrieve past deployment of a single service by going through the 3000+ history for it.