Alright, I give up on thinking that I can keep this blog updated with any sort of regularity. Sorry folks.

I talked about SwiftScan earlier and had thought I was mostly done with it. Since then it has grown into more than just an afterthought of a tool, and more of a primary production interface. I’ve attempted to make things as simple to understand at first glance as possible, so I’ll just stop talking and start posting screenshots.

It’s worth noting that when an operation is “Checked Out”, SwiftScan queries Epicor for the Estimated Labor/Burden set for the operation and uses that for the labor detail record.

What has surprised me the most about writing this program, is that even though I use the Epicor .NET libraries and everything is done via “BusinessObject” calls, it is SO much faster than the Epicor Client. Blazing fast. The JobDetails window is essentially the Job Status Dashboard and it loads all of that data in 1-2 seconds at most. Pulling the same information from the Job Status Dashboard might take 15 seconds – 2 full minutes, depending.

This application is customized pretty heavily for my environment–for example–the Check In button only writes the OprSeq to a UD field on the JobHead table. We use this in a custom report for job status. However, if you’d like help creating a similar tool or if you’d like to see some of the code, just let me know. It was all done in C# with Visual Studio 2010.