We've spent the past month working on fixing a couple of bugs, as well as adding one additional feature that aids your operators. Let's dive in...
Cross-referencing Matching Jobs
We noticed that when an operator loads a job in Compass - we didn't have a way to cross-check the current jobs in the queue to see if there was a match already waiting for them. So we added this query. If your operator loads a job with a matching work order number and unit name to one already waiting in their queue, we will prompt them to verify whether they wish to continue adding the new job (perhaps you're breaking up the work intentionally into multiple jobs!) or they wish to use the job that was previously loaded. The choice is theirs!
Please note: this will not take affect if the operator has already begun work on a previously matching job - this is related to jobs waiting to be started in the production queue. It's simply a better way to catch duplicate entries before an operator gets confused.
Other Adjustments:
- A couple of our customers will recognize this issue - you've sent a unit for publishing review, you've made all the approvals and the unit is sent for publishing, but for some reason the Under Review tab still shows but the page is blank?!! We fixed that... or at least we fixed one unique way to have caused that. If you continue to see this, please let us know.
- For those customers who have designers who are able to edit steps even when a unit is under review, we've stopped that ability. Your designer will no longer be able to grab the 'new step' url from the address bar history as a means to backdoor into editing a new step while it's under review. This allows us to maintain publishing log versioning consistency.
