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.
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:
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>
참고:
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.
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 |
Scripts and styles can be debugged in different browsers.
- Debugging in IE: To debug AEM Forms workspace in IE, see: http://msdn.microsoft.com/en-us/library/hh772704(v=vs.85).aspx.
- Debugging in Chrome: To open debugger in Chrome, use the shortcut: Ctrl+Shift+I. For more information, see: http://developer.chrome.com/extensions/tut_debugging.html.
- Debugging in Firefox: Several Add-ons are available to debug scripts and styles in Firefox. For example, Firebug is one such debugging utility (http://getfirebug.com).
-
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.