PDF form is not getting rendered or submitted in Google Chrome.
Last updated on
Apr 27, 2021
|
Also applies to Adobe LiveCycle
This article discusses how to debug HTML Workspace by enabling logging and by using debugger in a browser. it also explains some common issues that you can encounter when using HTML Workspace and their workarounds.
Logging in HTML Workspace
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 HTML 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 HTML 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 HTML Workspace
- FATAL
- ERROR
- WARN
- INFO
- DEBUG
- TRACE
- OFF
Debugging information for browsers
Scripts and styles can be debugged in different browsers.
- Debugging in IE: To debug HTML 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).
FAQs
-
- Install the Adobe® Reader® plug-in.
- In Chrome, open chrome://plugins, to view available plug-ins.
- Disable the Chrome PDF Viewer plug-in, and enable the Adobe Reader plug-in.
-
SWF form or Guide is not rendering in Google Chrome.
- In Chrome, open chrome://plugins, to view available plug-ins.
- See details for Adobe Flash® Player plug-in.
- Disable PepperFlash under Adobe Flash Player plug-in.
-
I have customized HTML Workspace but I am unable to see the changes.
Clear your browser's cache, and then access HTML 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 an Adobe® LiveCycle® 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 LiveCycle application, and then log in to Workspace.
-
HTML forms, using Process Properties in their design, when rendered in HTML 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 HTML Workspace, the Submit button is not visible to the end user. However, when rendering as an HTML form in HTML 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 HTML Workspace, outside the form, completes the task.