Release 4.12
SUMMARY
Job Scopes received more attention during this release. Several new capabilities were added to scopes and tasks as outlined in the New Features section below. In relation to the refactoring tasks in previous releases, other fixes and enhancements were identified and addressed. Some issues were discovered that were quite old, so this release contains considerable improvements and adds to the overall application stability.
We have recently been notified that the current version of the application framework will reach it's end-of-life in late 2020. We've anticipated this for a while and were reluctant to migrate before the new version had sufficiently stabilized. The new framework has some capabilities that we anticipate will add to the richness of this application. Over the next couple of months, development will focus on this migration. Expect interim releases to contain only bug fixes.
NEW FEATURES
Added duration to Job Scopes
You can specify the number of days duration of a job scope in conjunction with the start and end dates. For template scopes, this allows you to specify duration without committing to a date. When using a template, the dates will auto-fill to the job scope.
Added offset and duration to Job Scope Tasks
Tasks can now show the number of days duration, as well as the number of days after the scope starts that the task starts.
Added progress and dependencies to Job Scope Tasks
You can track progress and indicate task relationships. You can also set the default task.
Job and Purchase Order Items have Text Search restored
The last set of releases had the catalog text search removed when editing the item. This has been restored. It is shown collapsed and is revealed by clicking on "Text Search" below the catalog item dropdown list.
Work In Progress Reclaim (WIPR) Bin is closed later in the process cycle
Previously, an empty WIPR bin was closed when the Job status was changed to billable. This left it difficult to move materials around at the end of a job. An empty WIPR bin will now close only when the job is billed
.
Don't trigger late timesheets unless there are jobs assigned to the employee
Employees are not late if they don't have an assigned job. Currently, the problem exists that an employee may be assigned to the annual job to track office work overhead and non-billable items. This would still trigger late timesheets unless the employee is marked as an Occasional worker.
FIXES
Fixed synchronization between Job Items and PO LIne Items
Certain fields of the materials and expense items were not being updated between the Purchase Order and the Job.
Fixed Style, Description, & UOM not saving on non-catalog PO Line Items
Related to the above change, some fields were not being saved as expected and were causing data loss when trying to create a catalog item from a non-catalog item.
Redirect changed after materials and expenses PO Line Items are edited
When editing a PO Line Item, the next form shown was the purchase order main page. Instead, it will take you to the materials or expenses list. There are some instances where this is not desired, but until a complete solution is analyzed, this is the preferred behaviour.
Prevent setting invoice ID for time sheets on jobs with scopes
Job scopes have the Customer P.O./Invoice attached to the scope. To change the P.O./Invoice on a time sheet, you should change it on the scope.
If you intend to split a scope between invoices, you are likely better off creating a new scope. This behaviour is now more obvious and explicitly stated.
Add a link to the catalog item on the title in the Catalog list
The link is already on the item code. Placing it on the title makes it more consistent with Job and PO items.
Fixed Item Code not displaying in Reconcile Expenses
The previous release contained a bug that prevented some fields from being loaded, and thus being unable to display in some lists.
Fixed Various Defects and Code Cleanup
Some errors identified in the logs were fixed in addition to several code cleanup tasks.
