Install the dev package of HTML Workspace on your server. See dev package, for instructions to create it.
Last updated on
Apr 27, 2021
|
Also applies to Adobe LiveCycle
The default installation and settings of Adobe LiveCycle allow for only one HTML Workspace to be available on the server. However, you may need to host two different instances of HTML Workspace on a single LiveCycle server. The two instances are accessbile by different URLs.
LiveCycle administrators customize the Workspace to create two different URLs and make two workspaces available on the same server. In this customization article, we assume the two workspaces are accessible at http://[server]:[port]/lc/ws and http://[server]:[port]:/lc/ws2.
Follow these steps to configure HTML Workspace.
-
-
Login to CRXDE Lite as an administrator, by accessing http://[server]:[port]/lc/crx/de/index.jsp.
-
Copy node ws at /content and paste at /content. Rename node to ws2. Click Save all. In properties of this node, change value of sling:resourceType to ws2. Click Save all.
-
Copy folder ws from /libs and paste at /apps. Rename the folder to ws2. Click Save all.
-
In GET.jsp at /apps/ws2, make the following code changes. Replace the following
<html lang="en"> <head> <meta charset="utf-8"> <title>Workspace Next</title> <meta http-equiv="refresh" content="0;URL='/lc/libs/ws/index.html'" /><html lang="en"> <head> <meta charset="utf-8"> <title>Workspace Next</title> <meta http-equiv="refresh" content="0;URL='/lc/libs/ws/index.html'" />with the following code
<html lang="en"> <head> <meta charset="utf-8"> <title>Workspace Next</title> <meta http-equiv="refresh" content="0;URL='/lc/apps/ws2/index.html'" /> -
In registry.js at /apps/ws2/js, change path of templates to refer to templates at /apps/ws2/js/runtime/templates. Replace the following code
"tasklist" : { "name": "tasklist", "path": "tasklistview", "model": "tasklist", "template": "text!/lc/libs/ws/js/runtime/templates/tasklist.html", "utility": "utility", "view": "taskview", "errorModel": null }with the following code
"tasklist" : { "name": "tasklist", "path": "tasklistview", "model": "tasklist", "template": "text!/lc/apps/ws2/js/runtime/templates/tasklist.html", "utility": "utility", "view": "taskview", "errorModel": null } -
In userinfo.js at /apps/ws2/js/runtime/models and /apps/ws2/js/runtime/views, change string /lc/content/ws to lc/content/ws2.
-
In /apps/ws2/js/runtime/services/service.js, change the path in getLocalizationData function to point to /lc/apps/ws2/Locale.html.
-
To refer to pdf.html of the new Workspace, change the path of pdf.html in /apps/ws2/js/runtime/views/forms/pdftaskform.js.
-
To refer to pdf.html of the new Workspace, change paths of pdf.html and WsNextAdapter.swf in startprocess.html, taskdetails.html, and processinstancehistory.html at /apps/ws2/js/runtime/templates.
-
Copy /etc/map/ws folder and paste at /etc/map. Rename the new folder to ws2. Click Save all.
-
In properties of ws2, change value of sling:redirect to content/ws2.
-
Change value of sling:match to ^[^/\||]/[^/\||]/ws2$.
More like this
- Introduction to Customizing HTML Workspace
- Generic steps for HTML Workspace customization
- Managing tasks in an organizational hierarchy using Manager View
- Integrating Correspondence Management in HTML Workspace
- Single Sign On and timeout handlers
- Displaying the user avatar
- Displaying information in the Task Summary pane
- Changing the organization logo
- Changing the color scheme of the interface
- Changing the font on the interface
- Changing the locale of the user interface
- Customizing error dialogs
- Customizing tabs for a task
- Customizing Task Actions
- Customizing the listing of process instances
- Customizing the task Details page
- Displaying additional data in ToDo list
- Getting Task Variables in Summary URL
- Images for Route Actions
- Creating a new login screen
- Minification of the JavaScript files
- Sorting of Tracking tables and adding more columns
- Updating the link to the documentation
- Hosting two HTML Workspace instances on one server