Posts tagged "variable"

CQ5.5 SP1: Inserting variables in newsletters doesn’t work in Chrome

Issue

If you are using Chrome with CQ5.5 SP1 and attempting to insert variables into newsletters as detailed below, you may notice that the variables are not inserted as expected.

1. Open Chrome and go to http://localhost:4502/content/campaigns/geometrixx/monthly_newsletter.emailclient.html
2. Double click on a text component to open the Edit component window.
3. Click on insert to insert a variable, for example ‘Firstname’.

Result: The variable isn’t inserted, and Chrome logs a javascript error: “Uncaught error: Index size error: DOM Exception 1″.

Solution

This issue is fixed in CQ5.5 SP2.1.  Chrome is only supported in CQ5.5 SP2.1 and later versions, as we made many changes to offer Chrome support in these versions.

Workaround

The procedure above works fine in Firefox and Internet Explorer.

reference: (44087/CQ5-16244)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 5.5/10 (2 votes cast)

LiveCycle ES2: results missing when using a Search Template

Issue

There are no search results when using a process variable at the top of the sort order list in a Search Template in the adminui in LiveCycle ES2 SP1.

Solution

This is a bug in LiveCycle ES2 SP1.  Update to LiveCycle ES2 SP2 or later.  You can also contact Enterprise Support if you require a patch for ES2 SP1 9.0.0.1.

Additional information

To reproduce this issue:

  1. Create a search template (Services > LiveCycle Workspace ES2 > Search Template Definition) with process variables in the layout column.
  2. Put the process variable at the top of the sort order list in the sort tab of the Search Template Definition.
  3. Go to Workspace; there are no search results.
  4. Move the process variable down in the sort order list in sort tab and save the Search Template.
  5. Refresh Workspace and there are result rows in the search template.

The search result rows should appear even when the process variable is at the top of the sort order list.

reference: (181660090/2651808)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES2: duplicate process variables in Search Template definition

Issue

When you define search templates in the adminui, some process variables are duplicated in the Criteria and Layout tabs. The duplication occurs after you switch between template names in the Identification tab.

Solution

Use LiveCycle ES2 SP2 or ES3.  Or, contact Enterprise Support to obtain a patch for ES2 SP1, 9.0.0.1.

Additional information

To reproduce this error:

  1. Create two search templates (Services > LiveCycle Workspace ES2 > Search Template Definition) with each having process variables in layout column.
  2. Switch to the other search template name in Identification tab, and switch back to the first several times. The process variable is duplicated under Process Variables heading in Criteria as well as in Layout tabs.

reference: (181648653/2651801)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle Workbench ES: PATRuntimeException: Invalid variable type

Issue

After migrating Adobe LiveCycle 7 to LiveCycle ES, the properties dialog for some of the LiveCycle 7 components do not open in imported processes in Workbench.  This issue occurs particularly with components from other vendors.

In the server log file, you may find an exception similar to the following:

<Mar 18, 2009 5:38:47 PM CET> <Error> <com.adobe.workflow.AWS> <server> <LCServer1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<anonymous>> <BEA1-30E1940ABA8BD8AE228B> <> <1237394327753> <000000> <stalling action-instance: 803 with message:
com.adobe.workflow.pat.PATRuntimeException: Invalid variable type. Variable: com.adobe.workflow.template.document.DefaultVariableTemplate@5ebcf7d, Type: lc7form at com.avoka.workflow.qpac.userplus.UserPlusService.A(Unknown Source) at
com.avoka.workflow.qpac.userplus.UserPlusService.execute(Unknown Source) at
com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:551) at
com.adobe.workflow.engine.ProcessEngineBMTBean.executeAction(ProcessEngineBMTBean.java:1933) at
com.adobe.workflow.engine.ProcessEngineBMTBean.asyncExecuteActionCommand(ProcessEngineBMTBean.java:1878) at com.adobe.workflow.engine.adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.asyncExecuteActionCom
...

Reason

Most QPACs from LC7 need to be updated to be able to handle the new “lc7form” variable type.  According to the documentation on the adobe site, this is a pre-requisite for using LC7 QPACs in LC ES.

On pg.4 of the doc at: http://help.adobe.com/en_US/livecycle/8.2/upgrade_changes.pdf

there is the following text:

Changes in variable types

Adobe LiveCycle Workflow 7.x supported a series of variable types that you can use in process definitions. The form variable type is renamed lc7form when you upgrade to LiveCycle ES. The upgrade willautomatically update your processes to use the new variable type name; therefore, in most cases, thechange is transparent. However, if you are using a custom component from a third-party or have created oneinternally and the QPAC makes an explicit reference to the form variable type, the QPAC must be updatedto recognize the lc7form variable type name instead. The new QPAC must then be deployed to the serverfrom Adobe LiveCycle Workbench ES.

Solution

For Adobe components, make sure you are using the latest version of the component available from the Workflow SDK.  For QPACs from other vendors, please contact these vendors and request an updated QPAC which is compatible with LiveCycle ES.

To deploy the updated component:

  1. Copy the component jar file to a local folder on the server
  2. Open Workbench
  3. Show View -> LiveCycle 7.x components
  4. Right click in the LiveCycle 7.x components view, and select “Deploy new component”
  5. Browse to the component jar file from step 1 above
  6. Set the appropriate deployment properties for the component
  7. Click OK

You may have to close and re-open the process map in Workbench for the changes to take affect.  You should now be able to open the properties dialog for the affected component activity.

reference: (180802977/2302710)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)