For 7.5 we have made it easy to create a Documentum connection using Captiva Designer. Check out the following topics in the Captiva 7.5 Help to guide you:
As for 7.1, unfortunately this functionality wasn't added yet, so you will need to write scripting to connect to Documentum from Captiva Desktop.
Thank you for the update, this helps us a lot and we can plan accordingly.
Is there any sample or document that talk about writing script for connecting documentum from Captiva Desktop it will be a good starting point for us for implementing this in Captiva 7.1 until we upgrade to Captiva 7.5.
Since this is a post installation and scripting question, I would encourage you to open an SR with support for further investigation on Captiva Desktop and to get any sample script.
We hope to hear more from you on installation and upgrade!
Did you know that the capture flow file (XPP) format is updated in version 7.5?
Whilst Capture Flow Designer automatically converts Capture Flows to the new version, it is recommended to follow the procedure below in order to mitigate against any potential problems:
- Ensure you have a backup copy of the XPP files
- [Optional] Prepare separate (standalone) copies of any meaningful script code from AssemblyInfo.cs
- Upgrade your system
- Open the old Capture Flow (there will be a version warning icon displayed)
- Save as new (the save dialogue is displayed automatically)
- Compile the new Capture Flow and verify new event handlers (BatchDelete, BatchError, StepError) were added to script code
- [Optional] Restore saved code from AssemblyInfo.cs (use _Global.cs)
- Upgrade/Install process on test server
- Remove the old Capture Flow
Please check out the white papers on the support site notably this one:
Did you know that Captiva Capture 7.5 Server was improved as a 64-bit application? This means higher performance enabling more batches to be loaded in memory and also larger batches.
As part of the move to 64-bit the Server parameter BatchMaskAddressSpaceK should be set to Max Physical Memory - .5 GB. For e.g., for a 16 GB memory set BatchMaskAddressSpaceK to 15.5 GB.
Only batches created from a 7.5 XPP run in 64-bit mode. Otherwise, all batches created prior to 7.5 processes, including 7.1 XPP, run in 32-bit mode. However, the Server is backward compatible with 7.1 and older batches/processes.
Upgrade to 7.5 and take advantage of 64-bit performance!
Re: In CaptureFlow Designer (specifically in 7.1)...how are RetriesLeft handled? Is our FinishRoutine called for every retry, or the FinishRoutine is only called after all retries have been exhausted?
With the auto-generated code from CaptureFlow Designer RetriesLeft is still a trigger but only internally. It should not be manipulated in the XPP. There should be no attempts to manipulate trigger values in an XPP - just pretend it does not exist. All triggering should be implicit from the flow through the steps. To "retrigger" a step, you need to have a "jump" back to that step in the flow.
Generally Finish routine is only called if module successfully processes the task. If there is an error, then auto-generated code will handle it and deal with implementing the automatic retries. Only if all retries are depleted will it trickle up the error to CaptureFlow scripting (a.k.a. code-behind), or set the task on error.
However, if you enable the step option in CFD to automatically go to next step, then even module errors will result in Finish being called, but with a non-blank "ErrorCode" value. So, you must take care to check the "ErrorCode" value and do something in your flow if it is non-blank.
When upgrading Captiva Capture, ensure that you have the following minimum hard disk space free to run the Captiva Capture installers:
- Database and Captiva Capture Server: 4GB
- Captive Capture Client modules: 16GB
These temporary hard disk requirements are necessary because the Microsoft Windows installer backs up the existing files before upgrading to the new version.
One thing to remember is that when configuring a module to run as a service, do not enable Allow service to
interact with desktop. When a module runs as a service, it suppresses its user interface and
does not run properly when configured to interact with the desktop.
Another Expert, Bryan Gard, touched on this but did you know that there is a new distributed capture client, Captiva Web Client, that was released in Captiva Capture 7.5 and will be our long term remote capture?
Captiva Capture Web Client provides the following features:
Upgrade to 7.5 and take advantage of new easier to use distributed capture Captiva Web Client!