[On-prem release: 2022 Spring]
[On-prem build: 22.02.25005]
When setting up a Scheduled Job with the 'Folder' delivery type, you can select a folder in the TARGIT folder structure (the VFS) for export.
Note: The 'Export' option will contain file locations that have been defined by the 'Export folders' settings in the TARGIT Management client.
End-users will be able to access the exported documents via the TARGIT client. The new type of files can be filtered as an 'Other' document type from the Start page. When opened, they will open in the associated application (e.g., Adobe Reader for PDF files, Excel for xlsx files, etc.).
Keeping everything within the TARGIT folders structure will also make it easier to set up and administrate links via Triggers to pre-rendered PDFs, Excel files, etc. The trigger type for this type of action is called 'Open pre-rendered export'.
Governance
By using the TARGIT folders for export, the exported documents are embraced by TARGIT Governance via Roles:
- The Designer user can only select output folders that he or she has write access to.
- The Consumer user can only open exported documents from folders that he or she has read access to.
Comments
Notice if you want to locate these PDFs, Excel, CSV files in the folder structure once they have been placed there by the scheduler, you should tick the type called "other" in the right hand side when you are browsing through folders in the Windows Client
Niels Thomsen and Ole Dyring
I'm trying to understand better how this works in the 2022 version you're discussing here, as well as earlier versions. For example 2019 does not appear to have the "Other" option.
In any event, my question is: If the export folder is outside of the VFS, can it still be accessed from within the TARGIT client?
For example, in 2019, I have the Default set up in TARGIT Management
C:\ProgramData\TARGIT\ANTServer\Exported Reports\
I can schedule a job and it successfully writes the output to that folder.
I can find it in Windows Explorer because I have access to the Windows Server.
In the TARGIT Client, I am SYS, and I'm in a role that has permissions to see this Default folder.
But is there a way for me to see this folder's contents from within the TARGIT client in 2019? If I upgrade to 2022 or newer would I be able to see this folder in the TARGIT client?
It's fine if the answer is "No" and folders outside of the VFS are only accessible via other means. I'm just trying to understand if that is the case.
Hi Karl,
In versions earlier than the 2022 Spring version, your Shared folders cannot be selected as an export folder. You will be able to define any physical folder, reachable by the TARGIT server, as an export folder. See this article: https://community.targit.com/hc/en-us/articles/360017202138-Export-Folders
Although you would be able to physically create one of your Shared folders as an export folder in this way, versions prior to 2022 Spring does not have the ability to view the exported content from within the TARGIT client. You will only be able to view the exported content with a standard Windows Explorer.
In the 2022 Spring version and later versions you can add the Shared folder or any subfolder in the Shared folder as your export folder. By using the "Other" setting - as mentioned by Niels - you will be able to view your exports from within the TARGIT client.
Inthe 2022 Spring version or later versions you will not be able to add folders outside the Shared folder (C:\ProgramData\TARGIT\ANTServer\VFS\Global) to be viewed from within the TARGIT client. I.e., you will not be able to add C:\ProgramData\TARGIT\ANTServer\Exported Reports\ as something you can view from within the TARGIT client. You would need to move that folder to e.g., C:\ProgramData\TARGIT\ANTServer\VFS\Global\Exported Reports. In your Management client, it should be a matter of changing the definition of the 'Deafult' export folder to point to this new location as well.
I hope this clarifies the possiblities and limitations regarding export folders.
BR / Ole
Great explanation, thank you!
Please sign in to leave a comment.