PIM Document Management Series: Local File Management Overview
Overview
Course Details
Set up and use PIM Local File Management.
Duration: 10 minutes
Course Objectives
Throughout this course, we will:- Demonstrate how to navigate and launch Local File Management.
- Demonstrate how to search and add files, work with bulk actions, and use other new Local File Management features.
- Demonstrate System Tray features.
- Discuss LFM Dashpart support.
Instructor
Emma France
PIM Product Manager
Frequently Asked Questions
Version 1.0
Local File Management (LFM) is the replacement to the PIM Working Files component, which allows you to add files to PIM, and check them out in order to edit them. Built with new technology, LFM now works consistently across modern browsers.
The following features have been implemented in version 1:
- Delete Local File on Publish
- System Tray Component
- Desktop/Start Menu Icon
- Separation of Files
- Express Check In
- Modified Since Checkout
- Search Feature
Version 2.0 of Local File Management has seen a host of enhancements thanks to the feedback from our C-GA clients and their testing.
The following features have been implemented in version 2:
- 'Add FIles' Option
- Right Click and Publish
- File Modified Date
- Sortable Column Headers
- Bulk Remove Files from LFM
- Diagnostics Enhancements
- Search Feature
LFM currently only works on Windows machines. We plan to support Mac in a future update, but we can’t provide timescales at this time.
In version 20.1 of PIM, the Working Files dashpart does not work with LFM, and it is disabled when LFM is running. The dashpart displays a message to advise you to use alternative methods to add files into LFM. The 21.0 release will see the dashpart reinstated for LFM.
Due to technological constraints, the new LFM does not support dragging and dropping onto the new LFM page.
Testing has been performed against LFM and OneDrive, and this looks to be compatible. We have now added OneDrive support to our test plans, and we will continue to support this going forward.
The In PIM section shows files that you are currently working on, i.e., files that you have checked out to edit. The Not In PIM section shows files that you have not published to PIM for the first time.
Yes – once you publish a file to PIM, the file is removed from your local machine and sent to your Recycle Bin.
Yes – LFM points to the same folder that Working Files previously used.
As of PIM 20.1.4 there are multiple ways to add files into LFM. The ‘Open Local Folder’ option on the Local File Management page displays your local working files folder, which allows you to drag and drop files into it. You can also use the ‘Add Files’ option on the Local File Management page – this displays a file picker to select the files that you want to add to LFM. Alternatively, you can select files in Windows Explorer or on your local Desktop, and then use the right-click ‘Move to Deltek PIM – LFM’ context menu item to move files into your working files folder.
No – Local File Management can only work with one PIM site at a time. To change the target PIM site, you must uninstall and reinstall the Local File Management application, or modify the BaseURL registry key under HKLM\SOFTWARE\Deltek\PIM\LFM, and then restart Local File Management.
You can upload up to 100 files to the Local File Manager in a single operation.
Yes - you can upload large files using Local File Management.
No - Local File Management currently only works on Windows machines.
Yes – LFM has been tested and works using a UNC path configuration. For example: \\192.168.9.2\user\emmaf\Documents\workingfiles.
Yes – LFM has been tested and works with OneDrive when the Documents folder is synchronized with OneDrive, and when the Documents folder is replaced within OneDrive.
This option is used to do a bulk check-in of all documents that you currently have checked out from the PIM document management system – these are the files that are displayed in the In PIM section on the Local File Management page. This option bypasses the PIM Publish Document wizard, and maintains all previous publishing settings, such as where the documents are published to, and any linked record types (attributes). Note that when you use this feature, the version numbers of all files increment, even if you did not make any changes to the documents.
The Modified Since Checkout column indicates if you have made any edits to a file since you last checked it out. This is useful when using the Undo Checkout option, as any edits you have made to a file will be lost when you undo a checkout.
Local File Management is the replacement for Working Files. However, if Local File Management stops working for any reason, or if you are a Mac user, then the system falls back to using Working Files (assuming the Working Files component is still installed). You can easily determine if Local File Management has stopped working – you will not see the In PIM and Not in PIM sections when you access Local File Management via the Information Zone.
Local File Management needs to connect to PIM for it to work. If PIM is behind a VPN, you will receive an error until you establish a connection to the VPN. Additionally, if you do not have an internet connection, the LFM system tray icon will not show on start until you establish an internet connection.
LFM always checks the status of files to make sure they can be safely removed. Files that you currently have open, for example, cannot be removed until you close them. LFM continues to check files to ensure they can be safely removed. After a number of failed attempts to remove a file, an error displays to advise you of the reason.
Yes - the LFM dashpart will be available in the 21.0 release of PIM, and it will use the existing Working Files dashpart area. The new dashpart will display a smaller version of the Local File Management page, but with all the same features available. PIM 21.0 is due for release in Q1 2022. For the 20.1 release, the Working Files dashpart displays a message when LFM is running to advise you to use alternative methods to manage your local files.
Unfortunately, this is a limitation imposed by Microsoft. The same is true of other context menu items, such as Open, Print, and Edit. The reasoning behind this is to prevent users from accidentally performing particular actions on a large number of files. We are currently investigating whether there is a way to circumvent this limit.