Deeplinking to ADF Pages
The workflow interface will supply a URL for the user to deeplink to certain UI pages (from outside the application). This section describes the structure of the URL so that the URL may be useful for other deeplinking purposes.
A Login presents if the user is yet to log in, and later redirects to the page with the deeplink URL.
When opening a tab in this way, the tab title will not show any row-specific information, like the Claim Code. So there may be a difference in how the tab title shows from when to open a tab for the same row, from inside the application.
URL Structure
To create a deeplinking URL, concatenate several parts:
-
The part of the URL that before
/faces
.
http://<host:port>/<****webApplContextRoot****>**.
2.
/faces/UIShell?jhsTaskFlowName=<TASKFLOW_NAME>
. The user can access the
right <TASKFLOW_NAME>
by going to the right page. Open
the About This Page pop up and look up the TaskFlow Name.
* &jhsSubMenuName=<menuName>
: In theory, combine any page with any menu, but use the menu to which the page belongs.
Use ClaimsMenuModel
for constructing a deep link for the Claims page.
The allowable values for menuName
are:
-
ReferenceDataMenuModel
-
ConfigurationMenuModel
-
ClaimsMenuModel
3.
OperationsMenuModel4
(optional) parameter:
&rowKeyValue<TASKFLOW_NAME>=
. Ensures one row queries automatically
while entering the page. Use the same taskflow
name as in the second step. Also, use the ID in the database ID column of the desired
(parent) row on the page. The page opens querying no data if there is no specified parameter.
Example
The URL below opens the Person page and queries one particular Person (the Login page presents if the user is yet to login):
<<application hostname and port>>/<context-root>/faces/UIShell?jhsTaskFlowName=Persons&jhsSubMenuName=ReferenceDataMenuModel&rowKeyValuePersons=
for example, <<application hostname and port>>/claims/faces/UIShell?jhsTaskFlowName=Persons&jhsSubMenuName=ReferenceDataMenuModel&rowKeyValuePersons=10242