Troubleshooting guidelines for AEM Forms workspace troubleshooting-guidelines-for-aem-forms-workspace

Last update: Wed Feb 28 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

This article discusses how to debug AEM Forms workspace by enabling logging and by using debugger in a browser. It also explains some common issues that you can encounter when using AEM Forms workspace and their workarounds.

Unable to install AEM Forms workspace package unable-to-install-aem-forms-workspace-package

Ater installing the patch, open the AEM Forms workspace. If you encounter the No Resource Found error, open the CRX Package Manager, and reinstalling the adobe-lc-workspace-pkg-<version>.zip package.

While installling the package, if you encounter an error javax.jcr.nodetype.ConstraintViolationException: OakConstraint0025: Authorizable property rep:authorizableId may not be removed, perform the following steps:

Log in to CRXDE Lite. The default url is https://[localhost]:'port'/lc/crx/de/index.jsp
Delete the following node:

/home/groups/P/PERM_WORKSPACE_USER
Go to the Package Manager. The default URL is https://[localhost]:'port'/lc/crx/packmgr/index.jsp.
Search and install the adobe-lc-workspace-pkg-[version].zip package.
Restart the application server.

NOTE

It is recommended to use the ‘Ctrl + C’ command to restart the SDK. Restarting the AEM SDK using alternative methods, for example, stopping Java processes, may lead to inconsistencies in the AEM development environment.

AEM Forms workspace logging aem-forms-workspace-nbsp-logging

You can generate logs at various levels to enable optimal troubleshooting of errors. For example, in a complex application, logging at the component level helps in debugging and troubleshooting specific components.

In AEM Forms workspace:

To get the logging information about a specific component file, append /log/<ComponentFile>/<LogLevel> in the URL, and press Enter. All logging information for the component file at the specified log level is printed on the console.
To get logging information of all component files, append /log/all/trace in the URL, and press Enter.
Log format: <Component file> <Date>:<Time>: <Log Level> : <Log Message>

NOTE

By default log level of all components is set to INFO.

The log level set by user is maintained only for that browser session. When the user refreshes the page, the log level is set to its initial value for all components.

List of component files in AEM Forms workspace list-of-component-files-in-nbsp-aem-forms-workspace

allcategoryModel

processinstanceModel

tasklistModel

appnavigationModel

processInstanceView

tasklistView

appnavigationView

processnamelistModel

taskModel

categorylistModel

processnamelistView

taskView

categorylistView

processnameModel

teamqueuesView

categoryModel

processnameView

todoView

categoryView

searchtemplatedetailsView

trackingView

favoritecategoryModel

sharequeueModel

uisettingsModel

filterlistView

sharequeueView

uisettingsView

filterView

startpointlistModel

userinfoModel

outofofficeModel

startpointlistView

userinfoView

outofofficeView

startpointModel

usersearchModel

preferencesView

startpointView

usersearchView

processinstancehistoryView

startProcessView

wserrorModel

processinstancelistModel

startprocessView

wserrorView

processinstancelistView

taskdetailsView

wsmessageView

Log levels available in AEM Forms workspace log-levels-available-in-nbsp-aem-forms-workspace

FATAL
ERROR
WARN
INFO
DEBUG
TRACE
OFF

Debugging information for browsers debugging-information-for-browsers

Scripts and styles can be debugged in different browsers.

Debugging in IE: To debug AEM Forms workspace in IE, see: https://learn.microsoft.com/en-us/office/dev/add-ins/testing/debug-add-ins-using-f12-tools-ie.
Debugging in Chrome: To open debugger in Chrome, use the shortcut: Ctrl+Shift+I. For more information, see: https://developer.chrome.com/docs/extensions/mv3/tut_debugging/.
Debugging in Firefox: Several Add-ons are available to debug scripts and styles in Firefox. For example, Firebug is one such debugging utility (https://getfirebug.com).

FAQs faqs

PDF form is not getting rendered or submitted in Google Chrome.
1. Install the Adobe® Reader® plug-in.
2. In Chrome, open chrome://plugins, to view available plug-ins.
3. Disable the Chrome PDF Viewer plug-in, and enable the Adobe Reader plug-in.
SWF form or Guide is not rendering in Google Chrome.
1. In Chrome, open chrome://plugins, to view available plug-ins.
2. See details for Adobe Flash® Player plug-in.
3. Disable PepperFlash under Adobe Flash Player plug-in.
I have customized AEM Forms workspace but I am unable to see the changes.

Clear your browser’s cache, and then access AEM Forms workspace.
What needs to be done by the user to enable the form to be rendered in HTML when opened in desktop?

Select the HTML radio button for default profile in the assign task step while using Workbench.
Attachment does not show up when clicked.

To view attachments, enable popups in your browser.
A user is logged in to a forms application. If the user tries to log in to workspace, it may not load, if the user does not have workspace permissions.

Logout from the other forms application, and then log in to workspace.
HTML forms, using Process Properties in their design, when rendered in AEM Forms workspace, display Submit button inside the form.

When designing forms, when you use Process Properties, it adds a Submit button inside the form. When rendered as a PDF in AEM Forms workspace, the Submit button is not visible to the end user. However, when rendering as an HTML form in AEM Forms workspace, the Submit button is visible to the end user. Clicking on this Submit button inside the form does not initiate any action. Clicking on the Submit button at the bottom of the AEM Forms workspace, outside the form, completes the task.

recommendation-more-help

19ffd973-7af2-44d0-84b5-d547b0dffee2