Document Management
Document Management - 12 items delivered in v1.1
What Was Delivered
-
FACADE EXPLORER Make space for a snippet of the front facade (see also innovation backlog lane) Add ability to add a facade image to a project entity:
-
Edit project allows for the image to changed.
-
They should be able to copy and paste it from clipboard.
-
Also, they should be able to upload a file using file upload interface.
-
The file should not be bigger than 5MB Additional notes below:
-
The facade image attached is what we would want to expose - this facade is from job 753250 - LOT 807 (23) GUINEA ROAD OFFICER 3809.
-
Intention is to then map all projects in FTS platform onto Metro Maps (we have a subscription) via a pin.
-
Then tell us when we are adding a new project IF the new project is within 500m of an existing project in our database.
-
Build online FTS QA checklist tab This is the form that FTS Consultants use to check the job file prior to submitting for Building Permit. I have attached an image of how it gets completed in the current PDF. I have attached an excel of the file. I have made some notes in cells to guide you but you can refer to the image to see how we fill it it. We are looking to greatly improve the efficiency of this process by automating some things and connecting to certain pieces of information in the platform where we can. The form is retained on the system in Documents but if our new format is via a TAB and once completed locked then this will suffice. Here’s a google sheets version of the XLS file that’s been updated with a note. When you select “Yes” for some checklist items, they should present the options displayed From Column C onwards. https://docs.google.com/spreadsheets/d/1wP9nPQeKKLRtg9WW5f_DFlyDXK0_VizsvELEWx4LgqA/edit?gid=1584738676#gid=1584738676
-
Develop Preview window for document in Document tab as per image?
-
PREVENT CUSTOMER ADDING DUPLICATE PROJECTS Example in Image.
- Customer is Lazy and won’t check before uploading
- Solution - stop them being able to add duplicate jobs based on job numbers and flag a warning in their window please.
-
Auto popup category and subcategory selection modal on a project document, after documents are uploaded / click + dragged. Auto popup category and subcategory selection modal on a project document, after documents are uploaded / click + dragged.
-
Document upload should be able to detect what the documents is when uploaded this will save time sorting out each document Here’s a Spreadsheet with the filenames and Category and Subcategory assignments. https://docs.google.com/spreadsheets/d/1Or7RiJOquZTA8NJ_yNSlKImciqfWSak9_l0pdu3iQfs/edit?gid=0#gid=0 The Category / Type for the document will be automatically set based on this matrix. For subactegories, you just need to add a hypen fater the filename with the subcategory name. For example: FTS Purchase Order - General.pdf this will auto assign General subcategory for FTS Purchase Order category. The name matching is very strict. If the names do not match, (for example if a hyphen is not entered, or a filename is misspelt, then it will not detect it and auto assign).
-
HOTFIX: Can we add a 'DELETE SELECTED' function to the Doc Actions please We still experience the old jobs in October where the documents are jumbled so we would save 5+ mins having this capability.
-
Remove document trash icon for customer
-
Create a Document Action which allows FTS users to update documents in a modal Update the Update Selected function to display a datagrid of documents instead with the following fields:
-
File name. (original name from entity - text only).
-
Type / Category (dropdown).
-
Subcategory (dropdown).
-
Status. (dropdown). When the user updates this, it will update all of the documents listed.
-
Document delete issue
-
Document form update
-
DOCUMENT VERSIONING: Take subcategories into consideration when calculating if a document being updated is already existing in the project DOCUMENT VERSIONING: Take subcategories into consideration when calculating if a document being updated is already existing in the project Currently, we’re only determining that a document is a previous version if there is a document that has the same category as the one being set. We need to change this so that it also checks to see if the category + subcategory are a match before identifying it as a previous version.
Impact
Improved document handling and version control, reducing manual effort and minimising processing errors.