Posts tagged "search"

CQ5.5: Activated images in publisher are displayed as pending in DAM search results

Issue

If you are activating images in DAM, and then searching for those images in DAM search as detailed below, you may notice that the image activation status appears as “pending” in the search results.

  1. Open DAM
  2. Navigate to a folder with images (example: /content/dam/geometrixx/banners)
  3. Activate all the images.
  4. Ensure that the image status is published.
  5. Switch to DAM search.
  6. Enter a search string (example: .png)

Result: The activated images appear as pending for activation.

dam_search

Reason

This is an issue in CQ5.5 and has been resolved in AEM 5.6 and later versions.

Solution

Upgrade to AEM 5.6.

reference: (43813/CQ5-23686)

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

CQ5: Fulltext search not working for asset content

Issue

You are searching in CQ5 for text contained within assets like PDF & Word documents in DAM, and not getting any results.

Solution

This issue is resolved in CQ5.5 SP1 and SP2 and later versions.  You should download these updates from PackageShare and update your CQ instance.

After updating CQ new documents in DAM will be indexed, but the existing documents will not.  Perhaps this is acceptable if you are just setting up a new instance, and do not have any existing documents that you need indexed.

To get existing documents indexed, you will have to re-build the lucene index as follows:
[1] Open http://<host>:<port>/system/console/bundles
[2] Find the ID for the following bundles

  • Apache PDFBox (org.apache.pdfbox)
  • Apache Tika core (org.apache.tika.core)
  • Apache Tika parsers (org.apache.tika.parsers)

[3] Look into crx-quickstart/launchpad/felix for the folders corresponding to the 3 IDs in [2]:

  • crx-quickstart/launchpad/felix/bundleXX

[4] For each bundle in [3], change the value in the bundle.startlevel from 15 to 14
[5] Restart CQ and check in the Felix console that the 3 bundles has the start level set to 14.
[6] Stop CQ
[7] Delete crx-quickstart/repository/workspaces/crx.default/index folder
[8] Restart CQ and wait for the indexing to complete

reference: (44511/GRANITE-761)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

LiveCycle ES2: Search template returns results outside of date filter

Issue

If you are using Search Templates in Workspace ES2 to search for tasks between certain dates for a particular process, you may notice that the results return tasks outside of the specified dates.

This problem occurs when using a localized Workspace and adding the Task Start date in the search template criteria as seen below:

Then you specify a date range when executing the search template in Workspace ES2:

The results returned from the localized Workspace versions are not filtered at all on date, whereas in the English Workspace they are (i.e. it only returns the results between the given dates):

Reason

This is a bug in the localized versions of LiveCycle Workspace ES2 where the results are not filtered by the date criteria specified.

You can check this by using a database logging to track what SQL statements are being sent to the database when the search template is executed.  In the localized Workspace the SQL is as follows:

SELECT  DISTINCT T0.id, T0.status, T0.step_name, T0.route_list, T0.process_name, T0.process_instance_id, T0.action_instance_id, T0.update_time, T0.create_time, T1.id, T1.type, T2.id, T2.status, T2.complete_time, T3.id, T3.workflow_principal_id, T4.id, T4.commonname, T5.id FROM tb_task T0  INNER JOIN tb_assignment T1  ON (T0.current_assignment_id = T1.id) INNER JOIN tb_process_instance T2  ON (T0.process_instance_id = T2.id) INNER JOIN tb_queue T3  ON (T1.queue_id = T3.id) INNER JOIN EDCPRINCIPALENTITY T4  ON (T3.workflow_principal_id = T4.id) INNER JOIN tb_task_acl T5  ON (T0.id = T5.task_id) WHERE (T5.user_id = ’9B365DDD-C7D4-102C-8DFF-00000A24CEC9′  AND T0.process_name = ‘Task_Forwarding/Task_Forwarding_Test’ )

whereas in the English Workspace the SQL contains the date criteria at the end:

SELECT  DISTINCT T0.id, T0.status, T0.step_name, T0.route_list, T0.process_name, T0.process_instance_id, T0.action_instance_id, T0.update_time, T0.create_time, T1.id, T1.type, T2.id, T2.status, T2.complete_time, T3.id, T3.workflow_principal_id, T4.id, T4.commonname, T5.id FROM tb_task T0  INNER JOIN tb_assignment T1  ON (T0.current_assignment_id = T1.id) INNER JOIN tb_process_instance T2  ON (T0.process_instance_id = T2.id) INNER JOIN tb_queue T3  ON (T1.queue_id = T3.id) INNER JOIN EDCPRINCIPALENTITY T4  ON (T3.workflow_principal_id = T4.id) INNER JOIN tb_task_acl T5  ON (T0.id = T5.task_id) WHERE (T5.user_id = ’9B365DDD-C7D4-102C-8DFF-00000A24CEC9′  AND T0.process_name = ‘Task_Forwarding/Task_Forwarding_Test’  AND T0.create_time >= ’2011-08-14 00:00:00′  AND T0.create_time <= ’2011-08-22 00:00:00′ )

Solution

There is a patch available for Workspace ES2 SP2 (9.0.0.2), so contact enterprise support if you require this patch.  The issue will also be fixed in future versions of Workspace (Es2 SP3, and ADEP).

reference: (182579627/2951216)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.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 ES: AdminUI does not show all process names in the process search tool

Issue

 If you are using LiveCycle ES to search for processes using the adminui, then you may notice that not all processes are listed under the “Process Name – Version” drop-down list.  Only processes which are activated in Workbench, and which have process instances in the TB_PROCESS_INSTANCE table in the database, will show up in this drop-down list.

Solution

 Check that the process is activated in Workbench, and then you can run the following SQL query to verify that there are existing process instances for that process:

select distinct service_name, count(id) from tb_process_instance

group by service_name

order by service_name

reference: (181613727)

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