Therefore™ Help

Zoom Window Out
Larger Text | Smaller Text
Hide Page Header
Show Expanding Text
Printable Version
Save Permalink URL

Tutorials > Solution Designer > Design > Indexing Profiles

Defining What Should be Saved

Scroll

Once the index data extraction has been defined, the next step is to define what should be saved to Therefore™.

The file itself should be saved

This is the default, and so only the category where the document should be saved needs to be defined.

The files to be saved are defined in an XML or text data file

Choose the category where the document should be saved, then click the Script browse button and enter the script:

FilesToSave = ExtractList ("FileName")

info

Filename is the tag that defines the files that make up the content of the document.

To make this step clear here are some wrong example scripts:

FilesToSave = Extract(“FileName”): will only extract the FIRST file in each document. If there is more than one file, it will not work.

FilesToSave = Extract(“FileNames”): will not import any files.

FilesToSave = ExtractList(“FileNames”): will not import any files.

The files to be saved are in an accessible folder

In the case where another file should be saved, choose the category where the document should be saved. Click the Script browse button and enter the script: FilesToSave = "<path or relative path to the file>"

No file should be saved

In the case where no file should be saved (Therefore™ Form), choose the category where the document should be saved. Click the Script browse button and enter the script: FilesToSave = empty

A new case should be created

Where a new case should be created, do NOT select a category. Click the Script browse button and use the script below.

dim IxDataCaseHeader

dim CreateParams(0)

CreateParams(0) = "IndexData" ' we want an index data object - currently that's the only one supported

dim CreateParamsVar

CreateParamsVar = CreateParams

' Create an index data object

set IxDataCaseHeader = CreateThereforeObject(CreateParamsVar)

' Set which case definition we want to use. Either the CaseDefNo or the CaseDefName.

' Please note: if the Case definition name is not unique (can be with TF2014) it will take the first case definition found.

IxDataCaseHeader.SetCaseDef("TestCase")

' set the case header fields - this can only be done with the SetField function.

' Change this to your fields

'IxDataCaseHeader.SetField "<the column name>", "<the value to set>"

IxDataCaseHeader.SetField "CaseHeaderData1", "My case header data 1"

IxDataCaseHeader.SetField "CaseHeaderData2", "My case header data 2"

IxDataCaseHeader.SetField "CaseNumberData1", 9001

' SearchCase(true) - Will return either 0 for no case found or the CaseNo if a case was found, when multiple cases are found, will return the CaseNo of the first case.

' SearchCase(false) - The same as above, but will return -1 when multiple cases are found instead of the CaseNo of the first case found.

nCaseNo = IxDataCaseHeader.SearchCase(true)

if nCaseNo > 0 then

' A case with this index data exists already

' Don't create a new case - use existing

SetCaseNo(nCaseNo)

elseif nCase = 0 then

' No case was found with this index data

' Create a new case

nCreatedCaseNo = IxDataCaseHeader.CreateCase

SetCaseNo(nCreatedCaseNo)

elseif nCase = -1 then

' This can only happen if you use SearchCase(false) instead of SearchCase(true)

' This means that multiple cases with this index data were found.

' You could throw an error in this case for example

ScriptError("Multiple cases found.")

end if