Opentext EMC² Captiva

Hey, There is an option for maximum files per batch which allows you to define the number of files that will be imported per batch in the Standard Import module. This will work for normal scenarios but in case of a scenario where we need to import a file and the respective data file this will not help us. By providing the maximum files per batch as 2 we may be importing 2 separate files and leave their respective data files to next cycle or the next batch hence that option is ruled out. Its again an issue with standard import which is a feature present in Multi directory watch module which is deprecated in 7.5 version. The solution for this is to write a profile script where you can import one document in a cycle and make sure its respective data file is present in the list of files and ignore the other documents in the list and keeping them in the same source path. The next cycle will pick the remaining file again and create a new batch for every cycle. That's just one so...

Hey, We had the feature of xml parsing in mdw for each document with same name in Multi directory Watch in the previous versions of Captiva but in Standard Import that functionality is no more. We have to do it in the code inside the workflow manually to parse an xml file. Apart from that we have a new feature of data file in the Standard Import profile. We have the field of Data file Extension where we can specify any extension to use as the data file. For example if we provide the value as txt then we need to pass the txt file with the dicument having the metadata. The format of the values should match data = "value" in the txt file to be read by the standard import module. We can provide multiple values separated by newline. The metadata from every txt file is stored in the IA values for the respective document. If the customer agrees to provide the metadata in the format of data="value" as expected by Standard Import then we can use any file extension ...

Hey, For the Standard import module to work we need to make sure that we have provided the profile name for example(myprofile1,myprofile2) in the shortcut of the executable file you are using. Create a shortcut of  CPIMPORT.exe file from "C:\Program Files (x86)\InputAccel\Client\binnt" path and in the properties window of the shortcut modify the target field as shown below. Target field contains : "C:\Program Files (x86)\InputAccel\Client\binnt\CPIMPORT.exe" - FileProfileNames:myprofile1,myprofile2 When you are running the module as service please provide the import profile names in the file "CPIMPORT.config" as shown in below format. FileImportProfileNames="myprofile1,myprofile2" The CPIMPORT.config file is located in C:\ProgramData\EMC\InputAccel\CPIMPORT\Config folder.