Manager SE Settings, Defaults, Database

Timestamp RO

Timestamp RO

Postby rojogar » Tue Apr 04, 2017 9:36 am

Our shop does not take appointments. We do not use Management's Scheduler. We have relied on the feature that automatically timestamps when a repair order is created from F6. That feature appears to be missing in the latest release of Manager. Is there a work-around or a quick method for time-stamping work orders without going through a lot of extra steps? This is one of a number of disappointments in the new release. We have been Mitchell1 customers since 1998.
rojogar
Member
 
Posts: 2
Joined: Wed Apr 06, 2011 3:12 pm

Re: Timestamp RO

Postby timbre4 » Tue Apr 04, 2017 10:24 am

If I understand correctly, I believe you are referring to the Time/Date In as "timestamp"? Nothing has changed in the software in this regard and I just had the field fill in automatically:
time1.png
 


The trigger is marking the R.O. as PRINTED; this is either accomplished by steps manually or automatically if you have the Mark All ROs as Approved/Printed option box checked. You might check your settings.
time2.png
 
Tim McDonnell -
Sr. Product Market Mgr / Forum Moderator / Mitchell 1 Media Developer
User avatar
timbre4
System Guru / Moderator
System Guru / Moderator
 
Posts: 4537
Joined: Tue May 25, 2004 5:47 pm
Location: TN - Volunteer State

Re: Timestamp RO

Postby GUTHTIRE » Tue Apr 04, 2017 10:38 am

This functionality creates problems here as well. When the RO is is first printed it should print that timestamp on the RO as time in, regardless of a secondary RO approved trigger. In our situation, marking all RO's approved seems counter intuitive. The RO isn't approved until the job is sold.
Dan
GUTHTIRE
100 Club: Active Contributor
100 Club: Active Contributor
 
Posts: 103
Joined: Thu Dec 10, 2015 5:19 am
Location: Glenmoore, PA

Re: Timestamp RO

Postby timbre4 » Tue Apr 04, 2017 10:46 am

GUTHTIRE wrote:This functionality creates problems here as well. When the RO is is first printed it should print that timestamp on the RO as time in, regardless of a secondary RO approved trigger. In our situation, marking all RO's approved seems counter intuitive. The RO isn't approved until the job is sold.


Perhaps we're getting hung up on semantics; Printed/Approved is a SINGLE event. There is no actual 'Approved' phase in the software.
Tim McDonnell -
Sr. Product Market Mgr / Forum Moderator / Mitchell 1 Media Developer
User avatar
timbre4
System Guru / Moderator
System Guru / Moderator
 
Posts: 4537
Joined: Tue May 25, 2004 5:47 pm
Location: TN - Volunteer State

Re: Timestamp RO

Postby rojogar » Tue Apr 04, 2017 12:48 pm

I'm referring to the field in the "Sched" column on the WIP page.
rojogar
Member
 
Posts: 2
Joined: Wed Apr 06, 2011 3:12 pm

Re: Timestamp RO

Postby GUTHTIRE » Tue Apr 04, 2017 1:37 pm

timbre4 wrote:
GUTHTIRE wrote:This functionality creates problems here as well. When the RO is is first printed it should print that timestamp on the RO as time in, regardless of a secondary RO approved trigger. In our situation, marking all RO's approved seems counter intuitive. The RO isn't approved until the job is sold.


Perhaps we're getting hung up on semantics; Printed/Approved is a SINGLE event. There is no actual 'Approved' phase in the software.


Perhaps, but we have multiple Advisors and when you print the RO the it changes to Approved. We use that as an indicator to show the job has been sold. It's the initial timestamp that's printed causing confusion. If the customer is scheduled for 9AM and they drop the vehicle at 8AM and the RO is printed at 8AM the timestamp on the printed page should be 8AM, not the scheduled time.
Dan
GUTHTIRE
100 Club: Active Contributor
100 Club: Active Contributor
 
Posts: 103
Joined: Thu Dec 10, 2015 5:19 am
Location: Glenmoore, PA

Re: Timestamp RO

Postby timbre4 » Wed Apr 05, 2017 5:50 am

rojogar wrote:I'm referring to the field in the "Sched" column on the WIP page.


We have recorded an issue with Sched field population IF you launch a Repair Order instead of Estimate from the New/F6 dialog. There will be some internal discussion with development TBD. The simple workaround is to change the selector to Start New Order as Estimate:
As.png
 
Then when you click on Convert to Repair Order, the Sched field (and WIP column) will be filled in.
Tim McDonnell -
Sr. Product Market Mgr / Forum Moderator / Mitchell 1 Media Developer
User avatar
timbre4
System Guru / Moderator
System Guru / Moderator
 
Posts: 4537
Joined: Tue May 25, 2004 5:47 pm
Location: TN - Volunteer State

Re: Timestamp RO

Postby timbre4 » Wed Apr 05, 2017 5:55 am

GUTHTIRE wrote:
timbre4 wrote:
GUTHTIRE wrote:This functionality creates problems here as well. When the RO is is first printed it should print that timestamp on the RO as time in, regardless of a secondary RO approved trigger. In our situation, marking all RO's approved seems counter intuitive. The RO isn't approved until the job is sold.

Perhaps we're getting hung up on semantics; Printed/Approved is a SINGLE event. There is no actual 'Approved' phase in the software.

Perhaps, but we have multiple Advisors and when you print the RO the it changes to Approved. We use that as an indicator to show the job has been sold. It's the initial timestamp that's printed causing confusion. If the customer is scheduled for 9AM and they drop the vehicle at 8AM and the RO is printed at 8AM the timestamp on the printed page should be 8AM, not the scheduled time.


The intended workflow as designed is:
Estimate = to sell the work and gain approval
Repair Order = customer approved, proceed
Invoice = confirm, subtract inventory, etc.
Pay/Post = pay and file it into history

By launching into R.O. immediately, you will populate Time/Date In and Scheduled right away (too soon in your scenario). If you were to start with an Estimate, then the time used is when you convert it to R.O.
Tim McDonnell -
Sr. Product Market Mgr / Forum Moderator / Mitchell 1 Media Developer
User avatar
timbre4
System Guru / Moderator
System Guru / Moderator
 
Posts: 4537
Joined: Tue May 25, 2004 5:47 pm
Location: TN - Volunteer State

Return to Database / Settings

Who is online

Users browsing this forum: No registered users and 2 guests