You are here
This release has several updates that’ll make working with Packages and Field easier. For example, Package users can speed up their processes using the new Auto-numbering feature and save time when removing multiple packages by using the bulk delete functionality. The Template editor in Field has been re-vamped to make it easier to create and edit template items. You can also mark items as mandatory, which means an Inspection has to be completed before it can be closed.
Auto-numbering for Packages
Numbering conventions are used between organizations to ensure all parties understand which document is which, and to keep order in a project's structure. You can use auto-numbering to avoid human error and to reduce the amount of time you spend validating and confirming package numbers.
Auto-numbering can be enabled (or disabled) by package type in the Package Type settings. If a package has been created using auto-numbering, the package number can't be changed. At the moment, you can select either Package Type code or Project code. But from release 19.1 you can also add an Organization code.
When you define your numbering scheme, you'll have a sequence number. For example, if your package type code is DES, and you use this for your numbering scheme, this may start with DES-00001. You can choose the length of this sequence number - from 4-6 digits - and with which number it will start with.
Deleting unused packages
Imagine you've just created hundreds or even thousands of packages using bulk creation and you realize there's a problem with them and they need to be deleted. Before this release you couldn't, but as of 18.12 you can use the new delete functionality to remove packages.
However, you can only delete packages that don't contain documents, mails or attachments, and have not been transmitted or used in a package review. The package numbers from the deleted packages can be used on new ones.
Only package administrators can use this functionality.
Adding and removing columns for documents
Ever wished you could replicate the columns you use in your Docs Register in Packages? Well it is Christmas so we've fulfilled your wish!
As with the Docs Register, you can add, remove or rearrange columns to the Documents tab for a package. Bingo!
Marking Packages as "No Longer in Use"
If a project's scope changes, you may find that some packages become obsolete. In this case you'll probably want to hide them in the Package Register. Package Admins can do this using No Longer in Use, which also hides all related package actions. If you want to re-open the package, you can do so at any time.
We’ve improved the way you create checklists templates in Field by improving the design of the editing screen providing a way for keyboard users to reorder template items with an alternative to drag and drop, and making it possible to set checklist items as mandatory.
Template editing screen
We’ve increased the editing page space to make it easier to create and manage checklist templates. This means the entire page is now available when you create a template, instead of being limited to a few lines.
When you’re adding item questions and response types, the menu is on the left-hand side of the page, instead of at the bottom.
The Details section at the top of a template can be collapsed so you can hide the sections you aren’t currently working on. If that wasn’t enough, you can now also move items using drag n drop to move items within and/or between sections.
Mandatory responses for checklists.
Do you ever wish you could force some checklist items to be answered in some way? For example, do you want an inspector to add their signature before sending the inspection in? Well you can now select the new Mandatory tick box when editing a template, this forces the inspector to add their signature before the checklist can be set to Closed.