- About Vivit
- LUGs & SIGs
- Vivit Blogs
- News & Events
- Knowledge Base
|HPE Software Products: HPE Records Manager and HPE TRIM Discussion, Information and News|
I am currently assessing a technical upgrade from current TRIM version 7.3.5.
Is there a significant technical build for an upgrade from TRIM version 7.3.5 to CM9 i.e. will there be a signifcant change in infrastructure?
Is it recommended to move from TRIM 7.3.5 to 8.3X initially before an upgrade to CM9.
We have considerable time constraints and would like to ascertain how long it would take to upgrade based on the technical changes required.
Is it possible to provide any technical documents on the technical upgrade roadmap recommended by HPE please?
We recently received notice that our support service level is shifting to 24/7 support. HPE is calling it a "service level uplift." We did not need, and do not want 24/7 support, but we have been told it is non-negotiable. As a result, our annual maintenance bill has increased over 10+%. Under such short notice we do not have budget for such a large increase. We are public entity and we budget FY in advance.
Does anyone in the community have similar frustrations?
Most RM & CM customers will probably have their IDOL Content Engine(s) configured with RepositoryStorage=FALSE. This has been the installation default since RM 8.2 days.
In earlier releases (TRIM 7.2 - RM 8.1) this parameter defaulted to TRUE, but HP decided (based on the experience of the majority of our customers) the benefits of setting it to FALSE (primarily indexing speed) outweighed the benefits of setting it to TRUE (primarily index stability) in an IDOL OEM implementation, with an expectation customers included IDOL indexes in their regular RM/CM backup regime.
Things started changing more recently since IDOL 10. IDOL engineering have been progressively refining the behaviour where RepositoryStorage=TRUE, to a point where from IDOL 11 onwards (i.e. Content Manager 9.x) they recommend creating any new IDOL indexes with RepositoryStorage=TRUE. It's envisioned the RepositoryStorage parameter will be deprecated in future and hence IDOL will always behave as if RepositoryStorage=TRUE. This recommendation hasn't yet filtered through to the default IDOL configuration in Content Manager 9.x, so it's worth keeping in mind for any new installations it's a good idea to change it to TRUE before indexing your CM dataset.
So where does that leave TRIM/RM/CM customers whose IDOL index was built using RepositoryStorage=FALSE? There's no need to panic, as IDOL content engines will continue working if left as is. If you want to embrace the new changes, however, it's not as simple as just changing the parameter. This setting is persistent in the IDOL index and cannot be changed without a full reindex. Sure you could change the parameter in the configuration file, but it won't do anything except log a warning every time the content engine is started that the parameter value doesn't match the index state.
At some point in future you'll want to re-initialise and perform a full IDOL reindex with the parameter set to RepositoryStorage=TRUE. Perhaps something to factor in when planning your next CM upgrade.
The release notes for Content Manager 9 state the following. My question is can the review and authorize process be applied to an individual document rather than at the record type level?
Records can pass through a review process allowing a series of reviewers to comment on, modify and approve or disapprove the content of a record.
Following review, a record can also be passed through an authorization process. During this process, a series of authorizers can authorize the release of a record. This authorization process can utilize
Docusign® to digitally sign the associated document.
Both the review and authorization process can be configured for a Record Type. Records using that
Record Type will automatically proceed through the designated process.
Kind Regards Ian
Is there anyone out there having documentation on the differences between 6.2 and 8.3, or may be between 7.3 and 8.3? It is quite a pain to identify all the differences and show them to the users as part of the change management. We also have Office integration and have found that the documents newly created were not automatically added to RM when closing during user testing (ie only an entry without record). Sometimes the new file was found in the offline tray, sometimes not. Need help from those who have upgraded to 8.3.
This might be a question for support, but asking here first ...
We're dabbling with ECM 9.1, it came out just in time for our Next Big Upgrade (yay!). I notice that the 32BitInstalls and 64BitInstalls folders don't include VS2010_Runtimes_xxx.msi or VS2013_Runtimes_xxx.msi. Those are included in ECM 9.0, just not ECM 9.1
Are these no longer required, or is it just an oversight?
Are betas or future release notes published anywhere?
After months of badgering our HPE rep about LDAP directory synchronisation we bit the bullet, figured it wasn't coming any time soon and upgraded to HPECM 220.127.116.119 to support our upcomming Windows 10/Office 2016 operating environment upgrade.
Then this week 9.1 comes out and in the release notes:
This is frustrating to say the least!
Am I missing something about how future releases are communicated? What's the best way of avoiding making poor decisions like we did with this upgrade?
Is there any documentation on what is involved in developing an External Document Store?
Could I please add the following strong suggestion to the next patch of HPRM?
- currently if you try and contain a new document to a "Closed" HPRM container you get the following message -
"<field name.............> Field Cannot be Left Blank"
- does it make sense to the end-user - no, it makes them think they're having a possible database table/ technical issue or that they've input no container number, yet they can see it displayed (see also attached screen shot):
- Id recommend the following : "The Container Record has now been closed - navigate to the next part or volume (use KwikSelect) to contain to"
HPRM 8.1,.17919 32 bit
I am looking for a copy of the HP RM 8.3 patch 1 documentation, it is version from February 2016 (on the front cover) and has 67 pages plus the 6 contents pages.
I have a hard copy of this document but need an electronic version.
I would like to hear from other fellow members, if they have used HP RM as an Application Plaform for transactional systems compare to its traditional usage of being seens as Archiving solution only. We have implemented HP RM in the following scenarios where RM becomes an Application for
- Medical Prescription and medical records holding alll transactional data including collaboration,
- Sea Port Management for all Arrivals, Departures, Bunkering process, Incident Management, Document Submissions as transactions where RM holds uptodate and Live transactions
- Engineering Drawings Management (with Autodesk Vault), where live drawings pdf and metadata is stored and presented through Portal for Engineer's collaboration., update process is initiated from RM process as well.
- Environment Sampling and Statistics data ( collected from sensors) is stored in RM and reported based on business rules.
- Insurance CRM - Quote to Claim process including Case management managed in RM presented through Portal.
- Project Management Framework for all Engineering -Construction projects managed in RM through Web Portal.
- Financial Trading system small Trading firm where all the trades are mamaged in RM for Audit and Comliance leveraging on Spot Exchange rate fed through contract rate feed in XML basis stored and managed in RM for 6 currencies. End of Day Summary compied in Report and stored against each currency.
Currently in Progress - Distributed HA-DR Capable Hybrid RM Data Lake where RM Application is located at 3 different location ( 2 on prem - 1 in Cloud). We are using Power Plant Business case for this scenario for Power Plant controlled documents, Maintenance Checklist, Routine Maintenance and Drawing where Asset are identified by using Power Plant KKS Code for Asset amanagement.
I would like to hear how others have leveraged on HP RM as a Platform, happy to compare notes.
Due to a critical issue with 9 patch 1 that was released last week, a replacement patch will be reissued soon.
Has anyone upgraded to the current release.
I have started the process for migrating our existing and I am seeing strange results with HPEContentManger web services.
Internet Explorer 11 won't load it at all whereas Firefox works fine with intergrated authentication, which it shouldn't.
Not looking forward to loging a service ticket.
Readers digest version - something I can sell to powers that be.... What are the big selling points in CM9?
What's in it for the End User?
What's in it for the Information Managers
What's in it for the Technical Boffins
What can it do that 7.3 we are currently on CAN'T and what are the advantages over 8.X
Thanks in advance
I am looking for a separate, self-contained document, which may be printed or saved for convenience of reference, of the HP Records Manager 8 help file/user guide - can you help?
A big thanks to Jon Grundy for keeping the community updated in the past when new versions of HP TRIM, HP Records Manager (RM) and HPE Records Manager were released. See Jon's original thread here if you're interested.
From now on, HPE CM Support will update this thread when new versions of Content Manager are released.
So, just to repeat Jon's advice from his last update:
HPE Content Manager is now publicly released and available on SSO!
HPE CM 9.0.0 - Build 201
Released: July 7, 2016
Does HPRM 8.1.1 support Kofax Express 3.1?
It's currently 3.1 running on Windows 7.
I seem to ask this question every year! :p
Anyone have any clues as to whether there will be an IGF this year?