Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
PerthRM8 Outstanding Contributor.
Outstanding Contributor.
406 views

The difference between Check in Styles and extended MAPI Folder QUEUE in CM9.3

Hi,

CM 9.3.1.300, MS Office 2016, Win 10 , SQL 2016 (in DEV)

We are really strugling with the fact that linked fodlers in 8.3 will not be available...e.g. linked when we go to CM 9.3.1.300 ...  There is no conversion tool ..Trying to create check in styles in bulk, no options to do that ...

I have noticed that in DEV env 9.3 there is check in style last modified January 2015???!??!!! They never existed in 2015.... Investigation showed that was user's Extended MAPI Folder Document queue and some how got converted, recognised as the check in style in 9.3.1.300 ...

Can someone tell me please or compare the entries in SQL in these two tables for check in styles and these MAPI Document queues ... how similar they are? File Number, record type, the name of the queue , mailbox name... everything exactly as the check in style//..?

 

Why cannot we export / import them in DATAPORT ?

Is there any other way of creating check ins tyles in bulk... or moving the windows registries from HPE MS Outlook Add-in Registry Key somehow to be used?

Thanks

 

 

 

 

0 Likes
3 Replies
MichaelQ Super Contributor.
Super Contributor.

Re: The difference between Check in Styles and extended MAPI Folder QUEUE in CM9.3

As linked folders were a per-user implementation so too was the conversion.  It used to be the case that when an Outlook session makes a connection to TRIM any legacy linked folders were converted to checkin-styles and then available for use.  The user should not have any reduction in functionality.

Whether this is still the case in 9.3 I cannot comment.

PS. Other things may also have been converted to checkin-styles too.  Perhaps Extended MAPI queues are one of them.  That process, as you have identified, does not relate to Outlook's Linked Folders functionality.

0 Likes
Kengland Trusted Contributor.
Trusted Contributor.

Re: The difference between Check in Styles and extended MAPI Folder QUEUE in CM9.3

We recently upgraded from HPE RM 8.3 to HPE CM 9.2 - and all of the linked folders converted seamlessly to the new check in styles and were linked.  We did get everyone who had linked folders to take screen captures, just in case we had to recreate, but this was not needed in the end.

I would expect the same would be of 9.3?

Thanks,

Kaye

0 Likes
PerthRM8 Outstanding Contributor.
Outstanding Contributor.

Re: The difference between Check in Styles and extended MAPI Folder QUEUE in CM9.3

Thank you both,

Can you please have a look at my replies to the similar topic:

https://community.softwaregrp.com/t5/Content-Manager-User-Discussions/Script-creation-of-container-and-Check-in-Styles/m-p/1672834#M37581

Kaye: you are still with Hewlett-Packard branding there in CM 9.2? In your windows registries there is Hewlett-Packard key where the info about linked mailbox folders is stored (folder name, file number and record type) ? that maybe can explain that these folders are magically converted to a Check-In styles..

Can something else be done here? Large number of our users are using these linked folders in their daily jobs saving the hundreds emails to a different files and they expect this to be working from a day 1 after the upgrade to CM 9.3.1 ...

Regards

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.