Hello everyone,
I’m a junior developer working with FlexiCapture 12, and I’m currently exploring a more efficient way to import emails from business mailboxes.
These mailboxes are shared by business units and must remain accessible to users. Typically, we connect our project to a subfolder within these mailboxes, such as FLEXICAPTURE/NONPROD or FLEXICAPTURE/PROD. We configure our Image Import Profile with four environment-specific options, each pointing to the corresponding subfolder.
- For the NONPROD environments, we copy the email to the subfolder so that it remains available for users in Inbox.
- For the PROD environment, we move the email to the subfolder, process it with FlexiCapture, and then move it back to the original Inbox if needed.
These behaviors are managed through Outlook rules.
For Hot Folders, we’ve successfully used environment variables to maintain a single Image Import Profile per environment, dynamically adapting it. However, this approach doesn’t seem to work with IMAP.
The issue we’re facing is that all four Image Import Profiles are present in every environment, which risks cross-environment processing — something we absolutely want to avoid.
So my question is:
In a professional context, how do you organize email imports when working with shared mailboxes and multiple environments?
コメント
2件のコメント
Hi Jessica,
Unfortunately import profiles from e-mails is not easily manageable in Flexicapture when working across multiple environments.
When we update the project from one environment to another, we use FCAdminTools / UpdateProject and then we manually change the configs in the updated environment.
We opened a feature request to add the /UpdateImportProfiles parameter to the UpdateProject command so that it can be optionally configured and updating the project does not overwrite the existing configuration. This feature has been added to the product backlog nearly 1.5 years ago, but has not been implemented nor has ETA.
Best regards,
Cyril
Hi Cyril,
Thank you for the information. Such a feature would be greatly appreciated.
We also use the
UpdateProjectcommand, but as you mentioned, it overwrites the Image Import Profiles…We are currently looking for a way to avoid manual deployments and rely solely on scripts via FCAdminTools.
Thanks again for your support.
Best regards,
Jessica
サインインしてコメントを残してください。