Custom CIF is not loading in V8 Style Editor

GangiReddy_Nandyala

HI,

i developed custom CIF as follwis, which rendering "SAMPLE-ID1" only.

i bundled this .jsp as war and deployed using confip.

<%@ page contentType="text/html; charset=UTF-8" %>
<%@ page import="com.vignette.as.ui.cm.coe.*,
com.vignette.as.ui.common.widgets.*,
com.vignette.as.client.common.*,
com.vignette.wcm.taglibs.*"%>
<%@ page import="org.apache.struts.action.ActionErrors" %>
<%@ taglib prefix="wcm" uri="/WEB-INF/wcm-appsvcs-cma.tld" %>
<%@ taglib prefix="cma" uri="/WEB-INF/vgn-appsvcs-cma.tld" %>
<%@ taglib prefix="bean" uri="/WEB-INF/struts-bean.tld" %>
<%@ taglib prefix="logic" uri="/WEB-INF/struts-logic.tld" %>
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
* Indicates Bold Only
<cma:transfer />
<wcm:initPage />
<wcm:renderWidgetTitle name="SAMPLE-ID1" />
<wcm:renderWidgetBody name="SAMPLE-ID1" />

The problem here is , the view is coming fine in V7 Style Editor it is displaying only one filed, For the same CI the view is different in V8 Editor Style, it is displaying all the fileds.

After that i modifed the above code to generate compilation errors, and deployed the in correct code.

in this case View is not coming in V7 eidtor style, but in V8 Style editor still i am getting the View(default view same as above). even i added some Sop's in the JSP.

when i access the CI from V7 Style Editor , sop's are printing in the log file, but if i acces the same ci in V8 style editor sop's are not printing.

I feel it is not calling the custom CIF at all in V8 Editor Style.

i developed the custom CIF using the instructions provied in the VCM docs.

any one have sample custom CIF working in both V7 and V8 Style Ediotr.

 

Bertrand_de_Coatpont

Hi Bob,

 

Thanks for your feedback. As you know extensions and extensibilitypoints are a double edged sword. The flexibility that you get on one hand is inverselyproportional to the complexity of future upgrades, as demonstrated by thisthread.

 

In the V8 user interface, the former “custom input form”extension point is not supported and not documented as it’s one of theprimary areas that make development complex, risky and upgrades complicatedlater on. In V8 we productized what we have found as the two primary use casesfor custom input forms:

 

<![if !supportLists]>-       <![endif]>Organizing the fields in multiple “groups” (Tabs bydefault), and I hope this would work for your first example below (instead ofusing collapsed fields)

<![if !supportLists]>-       <![endif]>Having the widgets labels automatically associated to messagebundle entries so that the entry forms can be truly multilingual

 

There’s a lot you can do at the V8 “widget” level,though. As before, custom widgets with custom renderers can be written,including for look’n feel requirements (though I would try to stay away).We are planning to expose more of the JavaScript API in the upcoming 8.1release to manage these fields (e.g validation API, getters/setters….)

 

Of course if there’s evidence of functionalities (outsideof look’n feel requirements) that would require CIFs as before, we willlook into it once more, but so far out of all the already V8 upgraded customersthis has not been an issue.

 

Thanks!

 

Bertrand

 

From: eLink Entry:Vignette V7 and V8 Web Content Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, September 21, 2010 5:16 PM
To: eLink Recipient
Subject: RE RE RE Custom CIF is not loading in V8 Style Editor 2

 

RE RE RE Custom CIF is not loading in V8 Style Editor 2

Posted by bob@kraai.com (Kraai, Robert) On 2010/09/21 18:15

 

Bertrand, The use case for this is to align with Author expectations where attempts to productize and address All or Nothing has failed.  Any number of customers can have something as simple as hiding or reformatting a page, creating a different look and feel to the content entry to provide better end user acceptance when switching from another system, to supporting business rules about what and how elements are displayed. For instance, I have a customer from pre-V8 that has collapsed fields that aren't as important depending on the group that is editing to allow for easier focus on the attributes that apply to the particular domain knowledge, but still allows editing of other fields if needed. I have another customer pre-V8 that replicated the look and feel of their custom application that the VCM was replacing so that the end users would have a better understanding of the system (and better user acceptance of the Vignette product). ! In my opinion, you can't take these features away.  Make them less necessary by making the system easier to use, but leave the extensibility points for those cases that you simply cannot address globally for everyone. ---Bob

---

[To post a comment, use the normal reply function]
Topic:	Custom CIF is not loading in V8 Style Editor
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01