If you are using CQ 5.4 you will notice that the user report is displayed in the browser and you cannot save/export any of the information in this list.
You can view the user report from the “Tools” console in CQ5. Select “Reports” in the left-hand pane, then double-click the user report in the right-hand pane to open it for viewing and/or configuration.
It is possible to export the user report as CSV content. You can do this in 3 steps.
- Overlay the /libs/cq/reporting/components/reportpage/ component to /apps/cq/reporting/components/reportpage/.
For detailed instructions on how to overlay a component watch the following video:
- In /apps/cq/reporting/components/reportpage/body.jsp replace the <body> section with the code in body_code.txt and save the changes.
- Navigate to the user report again and now you will see a link at the top to “Export” the content as CSV formatted text. This export function has different behaviour depending on the browser version.
Note: it is important to overlay the reportpage component in “apps”, rather than editing the file in “libs”, as libs is overwritten anytime you install a hotfix or a product update from Adobe, and therefore your changes are lost. It is a best practice to overlay components to apps, and then you always have a backup of the original component in libs.
You may have a requirement to provide a full breakdown of all Users/Groups/Roles for your installation of Adobe LiveCycle ES. It is possible to find out this information using the AdminUI, however this would take a lot of effort and time to perform all the necessary searches and manually compile the information returned. The other option would be to run an SQL query on the database to read the information directly from the DB tables.
The following are 2 SQL queries to:
Query 1: Identify all Users in each Group
select epea.commonname as GROUP_NAME,
epeb.commonname as USER_NAME
from lcesprd.edcprincipalentity epea,
where epea.id = epg.refprincipalid
and epea.id = epgc.refparentprincipalid
and epeb.id = epgc.refchildprincipalid
and epea.status = 'CURRENT'
and epeb.status = 'CURRENT'
and epea.principaltype ='GROUP'
and epeb.principaltype ='USER'
order by GROUP_NAME
Query 2: Identify all Roles assigned to each Group
select epea.commonname as ROLE_NAME,
epeb.commonname as GROUP_NAME
from lcesprd.edcprincipalentity epea,
where epea.id = epre.refroleid
and epeb.id = epre.refprincipalid
and epeb.principaltype ='GROUP' -- (Note: can change this value to 'USER')
order by ROLE_NAME
When you assign a task to a new user created in LDAP and synchronized with LiveCycle, an exception occurs. The error occurs when you assign a task before the new user has logged into Workspace.
2008-07-22 07:51:45,497 ERROR [com.adobe.workflow.AWS] stalling action-instance: 688 with message: A non- retryable Exception has occurred:
Attribute: out_of_office_user_id on object: workflow_user:[DCC77BA9-D281-1D96-D57E-EF9C5B804811] has not been loaded.;
CausedByException is: Attribute: out_of_office_user_id on object: workflow_user:[DCC77BA9-D281-1D96-D57E-EF9C5B804811] has not been loaded.
If the user has logged in to Workspace, the task is assigned without any problems or errors.
This issue is resolved in LiveCycle ES 188.8.131.52 and later. There is a patch available for LiveCycle ES 8.2.1; contact Enterprise Support to obtain the patch.
This problem occurs with the Oracle database. The Oracle POF adapter doesn’t work when a Proxy Object loads for a record not in the proxied table without populating all attributes in the query.
Users have duplicate queues in Workspace in Adobe LiveCycle ES 8.2.1. The first queue is the user’s personal queue (in blue below), and the second seems to be a shared queue (in red below).
Duplicate queues can appear if you had a custom application in LiveCycle 7 that created more than one queue per user. By default, LiveCycle doesn’t create more than one queue per user. LiveCycle clients, like Workspace (LC ES) and FormManager (LC 7) do not support multiple queues for the same user. The workflow engine in the background does support multiple queues per person, but this functionality is rarely used.
When there are multiple queues for a user, each queue has a row with a unique ID in TB_QUEUE. The ID in the default_queue_id column is the ID of the queue that workspace always uses for that user.
Remove the duplicate (shared) queue from the TB_QUEUE table. Before deleting the queue, run the following query to ensure that there are no assignments referencing the shared queue:
Select count(*) from tb_assignment where queue_id = xxx
Where xxx is the queue ID of the queue that is not the user’s default queue. That is, the queue ID not listed in the default_queue_id column.
If you are trying to apply rights to a PDF document with ReaderExtensions 7.0, you may receive the following error in the web browser:
Error 400: Applying User Rights to the document ‘SAE_V0.9Static.pdf’ failed:
and the following exception in the log file:
[26.08.05 09:21:03:361 CEST] 500fe7b1 Logger
E com.adobe.document.PDFManipulation document does not have certifying signature
[26.08.05 09:21:19:622 CEST] 50e8a7b1 Logger
E com.adobe.document.PDFManipulation an unknown exception caused the call
This error can occur on all application servers.
1. This is due to an incompatibility when using Designer 6 to design documents to be processed with ARES 7. This issue has also been seen using some language versions of Designer.
2. This issue could also occur if you are trying to apply rights to a password-protected PDF document, and you dont supply the password when applying the rights.
1. If you use Designer 7 or greater then the documents can be correctly extended with LCRE 7.
2. If you supply the password for the PDF when applying the rights, the error will not occur.
If you have installed PDF Generator 7, you may receive the following error when trying to start the application server service:
You must use the same user to install MS Word and PDFG, and this user must be the same user account used to start the application server service.
Re-install MS Word and PDFG using the same user account (this should be an Administrative user), and then change the LogOn properties for the application server service in the Control Panel to use this account to start the service.