76543718-3fcd-408a-babb-69833d9ab00b.jpg

Consultant/Developer

2dece64c-8362-41da-899b-f20323232603.zip

f9cc99b5-f1a6-4750-b853-040fb0474c8f.png

Across many sectors, it is very common to have use cases involving the use of File Explorer or SharePoint for :

1.  Storing/archiving of files.
2.  Downloading of attachments from browser or applications.
3.  Working across multiple user profiles and machines via file sharing services.

These use cases often require many pre/post-requisite steps to ensure that the environment is bot-friendly. Due to the repetitive nature of these steps, we have created utilities/libraries for this purpose and have saved many hours of development as well as ensure quality and consistency across all our processes.

  

Some examples of these utilities are :

1.  Checking if certain file or folder paths are rooted, and if not, to append a user profile root to the file path (useful for cases where file and folder paths provided by users may or may not be rooted and if working across multiple user profiles, etc.).
2.  Validating if the default downloads folder is empty, and if not, archive the items within into a date-time stamped folder (useful for situations where downloading of attachments from browser or applications does not have the option of specifying folder or file paths).
3.  Uploading files to SharePoint - utility works for either file or folder uploads and if upload has failed, files/folders are copied to a predefined local destination to avoid data loss + custom error message to inform user on the error (useful for any process that requires work with SharePoint).

This release contains 5 snippets:

1.  **Util\_CheckFolderStructureIsRoot** - This workflow is used to check if configuration file paths are full paths and skip, else add local user profile to the relative paths to complete the configuration values.
2.  **Util\_CheckLocalRootDirectory** - This workflow is used to check if a given folder structure exists on the user's machine. If not (i.e. on first run), bot will copy a mock directory from the source code stored in "Data\\Local Root Directory\\Data" into the desired location on the user's machine.
3.  **Util\_ClearDownloadsFolder** - This workflow checks if there are files in the default downloads folder and proceeds to delete them. This is used in tandem after Util\_ValidateDownloadsFolder, and in a Process Try Catch to reset the environment for the retry.
4.  **Util\_UploadFilesToSharePoint** - This workflow uses the CopyDirectory method to move files from inSourceFolderPath (usually "Data/Temp") and copies the directory into inTargetFolderPath (usually the bot output path).
5.  **Util\_ValidateDownloadsFolder** - This workflow checks if the default downloads folder has no files, else creates an archive folder within to move the files into that folder to avoid file name conflicts in future workflows.

These snippets are used to simplify file and folder level workflows and can be reused multiple times in a complex process.

e041b0ac-dc03-4057-845b-6616b5e3fd9c.jpg

dac4c421-acf4-47ba-8de6-722a4996d03d.jpg

2a9be8f3-d3ec-4eb0-82e0-3afcb6efe6fe.jpg

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Folder Level Utilities