Upgrading FURL from 8.1 to 8.5

Christine_Howell

Hello,

In 8.1, we had added our own attributes for Furl names for our channels and contents.  I see that 8.5 has included these as standard.  However, the biggest difference is that we used a listener to properly fill in the field value for the furl name attribute based on the channel or content name.  It was not writeable by users.  In 8.5, this attribute is writeable by users and so far, I am unable to make this field read-only. 

I am guessing also, that I will have to write a run-once app to move all the existing furlname values in 8.1 to the new furlname fields in 8.5, unless someone has a better idea.

Has anyone else utilized the furlname approach in 8.1 similar to ours?  Has anyone upgraded to 8.5 from 8.1 and had to migrate the furlname behavior?  I am basically looking for others' experiences with furl during upgrades.

Thanks,
Christine

dsarada

Hi Christine,

 

With 8.5, we ship vgnfurlmigrate tool which is meant for migration of data from the custom (furl name) attribute to the Friendlyurl (virtual) attribute.

 

IMHO, you can refer to Chapter 6.3.2 in the WEM 8.5 upgrade guide which details this topic.

 

Thanks and Regards,

Deepak.

 

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, June 03, 2014 5:59 PM
To: eLink Recipient
Subject: Upgrading FURL from 8.1 to 8.5

 

Upgrading FURL from 8.1 to 8.5

Posted byhowellc@franklin.edu (Howell, Christine) On 06/03/2014 08:26 AM

 

Hello, In 8.1, we had added our own attributes for Furl names for our channels and contents.  I see that 8.5 has included these as standard.  However, the biggest difference is that we used a listener to properly fill in the field value for the furl name attribute based on the channel or content name.  It was not writeable by users.  In 8.5, this attribute is writeable by users and so far, I am unable to make this field read-only.  I am guessing also, that I will have to write a run-once app to move all the existing furlname values in 8.1 to the new furlname fields in 8.5, unless someone has a better idea. Has anyone else utilized the furlname approach in 8.1 similar to ours?  Has anyone upgraded to 8.5 from 8.1 and had to migrate the furlname behavior?  I am basically looking for others' experiences with furl during upgrades. Thanks, Christine

---

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center