How would I go about doing that?  I am fairly new to laserfiche.

I've never done this in Workflow, but theoretically you could use a Script Activity. Anything you can do in .NET you can do in Workflow using scripts. I don't know what extent Workflow sandboxes what scripts can do, but you should be able to do all the standard file I/O operations. You could write the code directly in the script window or build a custom DLL that you call.

There's not enough room here to write a full tutorial, but you'll probably need a developer if you want to go that route. Otherwise, I'd recommend seeing if Import Agent can satisfy your needs. It would be an extra purchase, but it will probably cost less when all is said and done than going the scripting route.

Nicholas - I have a custom activity available that allows workflow to move, copy, rename, and/or delete Windows files from a UNC path or mapped drive.  The free 30 day demo is available for download at http://www.qfiche.com/products.html.  I am slowly adding custom workflow activities to my 'Qfiche Toolkit' and the FileIO activity is just one of them.  Please try the free demos and feel free to contact me at cprimmer@qfiche.com if you have any questions.

Hey Devin,

How would I go about creating a script activity to do this ?  

Hey Cliff,

  I would like to create an activity that will do what I need?  I feel that this can be done without a cost.  If you could provide some information as to what would need to be done, or point me in the right direction , that would be great.

Thanks.

One way to make is simpler is to line up your physical path with your Laserfiche path. That way you could take the Laserfiche path and use the path token to tell your script what paths to use.

With your level of experience, you'll definitely need a developer to help you out, or buy the Qfiche activities.

Script activities are very powerful, but they require advanced knowledge of both Laserfiche and software development. Not really stuff we can help you with during a few quick posts.

Well I know I am fairly new to laserfiche but I do have a fair amount of development experience.  Is there any tutorials I can look at.  To start, how would I go about integrating a script activity into the workflow?

Nicholas - There are two types of script activities available in the Workflow Designer.  They are the 'Script Activity' and 'SDK Script Activity'.  Use the SDK Script Activity if you want to interact with Laserfiche Entries (documents and folders).  If you don't need to interact with Entries then you can use the Script Activity.

Just drag-and-drop one of those activities onto the Designer canvas and then double-click on it to open up the script editor.  Once you have the script editor open you can use the Help menu item to see some script examples.  You can write your scripts in either VB or C# but real developers use VB! 

If you have access to the Laserfiche SDK then there are a lot of additional examples and object descriptions available there.

Here is a link to some additional SDK resources on the support site "https://support.laserfiche.com/index.aspx?product=SDK"

To make the water a little muddier; there are two distinctly different development libraries for Laserfiche.  LFSO (Laserfiche Server Objects) and RA (Repository Access).  LFSO is the older of the two libraries and is being phased out so I would focus on using the RA libraries when you start writing scripts.

If you are using Workflow 9.1 then the default is the RA libraries but if you are using an earlier version of Workflow then the default will be the LFSO libraries.

Most of the script documentation available is for the LFSO model but that is gradually changing.

Lots of information but I am confident that you can get through it!

Let me know if you have additional questions or need specific help...

Nicholas - Here is a code snippet that moves a file using the System.IO functions. 

Note: the service account that workflow is running under has to have the appropriate permissions to copy and delete files in the source and target folders.

The code below is in a workflow Script Activity;

Imports System
Imports System.Collections.Generic
Imports System.ComponentModel
Imports System.Data
Imports System.Data.SqlClient
Imports System.Text
Imports System.IO   'NOTE: You need to add this namespace reference...

Namespace WorkflowActivity.Scripting.Script
    '''<summary>
    '''Provides one or more methods that can be run when the workflow scripting activity is performed.
    '''</summary>
    Public Class Script1
        Inherits ScriptClass90
        '''<summary>
        '''This method is run when the activity is performed.
        '''</summary>
        Protected Overrides Sub Execute()
            'Write your code here.

            'Wrap all of the code in a Try/Catch to trap any errors...
            Try
                'A little bit contrived.  Everything hard coded
                'You will probably want to pass these into the script as tokens instead...
                Dim sourceDirectory as String = "C:\TestData\Source"
                Dim targetDirectory as String = "C:\TestData\Target"
                Dim filename as String = "test.tif"

                'NOTE: If the source or targets do not exist then the routine 
                'will throw an error...
                'NOTE: If you do not use the 'Imports System.IO' in the header
                'you will have to use the full namespace reference for these methods,
                'i.e. System.IO.File.Copy(....
              
                'The two lines of code to move a file (copy and delete vs move)...
                File.Copy(Path.Combine(sourceDirectory, filename), Path.Combine(targetDirectory, filename), True)
                File.Delete(Path.Combine(sourceDirectory, filename))

            Catch ex As Exception

                'If there is an error this line will write it out 
                'to workflow as a trackable error...
                WorkflowApi.TrackError(ex.Message)

            End Try

        End Sub

    End Class

End Namespace

Depending on how many files and your local network you'll probably want to put that script in a parallel activity. If the file copy operation takes a long time or there's an issue with it, you don't want it to block the rest of the workflow. Better yet, put the script activity in it's own Workflow and then fire and forget from your main workflow.