I value OpenText Core Content Management for its robust built‑in audit trail and flexible record retention functionality which is critical for our banking compliance obligations. The audit trail logs every view, download, edit, and permission change within the system, offering complete traceability for any document‑related incidents, which helps in our day‑to‑day risk mitigation. Last quarter we went through an official review with our state regulatory audit vendor. A temporary contract worker on our operations team had received folder access to closed‑loan customer records, and shortly before their assignment ended, they downloaded a batch of borrower disclosure files. We did not catch this action right away, and there was concern they might share that sensitive financial information externally. Thanks to the detailed logging inside OpenText Core Content Management, I could pull up the exact timestamps, user ID, and list of every file they had touched. I compiled that report and submitted it directly to our auditor, showed them I had already revoked all leftover system access for that temp worker. That concrete log evidence kept us from receiving a formal regulatory penalty that could have hurt our branch standing. I also appreciate the ability to set automated retention policies, which automatically archive or flag documents based on their legal storage timeframes. Not long ago one of my coworkers tried to bulk‑delete a group of old loan closing files thinking they were past their required holding period. The retention policy triggered a hard block and popped up a warning notice, stopping them from wiping records we still needed to keep for two more years. These features, although not without their drawbacks, notably the configuration complexity, significantly remove compliance risks and support our regulatory requirements. Review collected by and hosted on G2.com.
The most frustrating issue is how OpenText Core Content Management handles large audit‑ready exports, as exporting big CSV datasets often times out. During a formal examination with our state regulatory audit vendor earlier this year, I needed to pull six months of access activity for our main loan document repository. Every time I tried running the full export job it would hang and fail halfway through. I had to split the data into multiple smaller date ranges and generated four separate CSV files. I sent all those files over to the audit vendor, but their compliance analyst mixed up the split datasets and completely missed several high‑priority download events within one file. They came back to us with dozens of extra follow‑up questions, and that whole mess pushed our audit completion back by more than one full business week. Setting up custom metadata for banking‑specific documents is also cumbersome, requiring multiple layers of configuration steps with no easy way to copy existing metadata rule sets. Every time I create a new folder for a fresh loan batch, I have to manually rebuild tags for loan numbers, branch locations and regulatory form IDs from scratch, which eats hours out of my weekly schedule. The search performance suffers when dealing with thousands of archived records; running keyword searches for old borrower files can take a very long time to load results. Notifications are another issue, as they fire for nearly every document action, leading to important alerts being buried and overlooked. On one busy day with lots of vendor activity, hundreds of routine access emails flooded our inbox, and we almost missed a critical alert about misassigned folder permissions. The platform's configuration process, especially for banking‑specific needs, is tricky and time‑consuming, sometimes resulting in mistakes that require significant time to fix. Review collected by and hosted on G2.com.
