This chapter covers the following topics:
Autolinks define a set of special keyword pattern words, for example, bug, that maps to an HTML context in the database. If the word bug has been created as an autolink, then when you author a solution that contains bug and an unique parameter--such as the bug number, for example bug: 10020--Oracle Knowledge Management automatically creates a hyperlink to that context in the database.
Autolinks let you create links automatically to other contexts in the application, which is useful in building a knowledge base where there is linked information.
Note: For statement details with content type Text with Autolink, you cannot use the following characters as preceding or following characters: < > " ' % ; ( ) & !
Note: For statement details with content type HTML with Autolink, you can use these characters as the preceding or following characters. If you create the statement details using the Rich Text Editor, then add the > character in the keyword pattern Preceding Characters field and the < character in the Parameter Following Characters field to enable the New Line delimiting character. The Rich Text Editor automatically generates HTML tags to wrap around each paragraph that you type in the editor.
Note: It is highly recommended that if you want to render a URL keyword pattern as hyperlink, you should use the HTML content type--such as HTML with Autolink--rather than the Text content type.
Notes
The keyword pattern Value is required but need not be unique. This supports the same keyword pattern being routed differently through different autolinks.
Preceding Characters distinguishes your keyword pattern Value from identical text values, and Following Characters determines where the hyperlink stops.
You need to create a function in Forms only if you choose Function for the type and the function is not available from the search list. For more information on how to create a function, see the Oracle E-Business Suite Security Guide.
For a keyword pattern used in agent pages, if the autolink is the Function type, then the function definition must include &cskDLink=OA.
For customer pages, if the autolink is the Function type, then the function definition must not include &cskDLink=OA.
If the autolink is Function type, the Function type must be INTEROPJSP.
A function definition used by an autolink must not contain "param=" at the end of its HTML call. If the URL needs to have a dynamic parameter value appended to it, then the proper procedure is to set the Destination Parameters field for an autolink.
When upgrading from a release of Oracle Knowledge Management prior to release 11.5.10, be aware of the following:
Because agents and customers have different sets of autolinks as compared to previous releases where they had the same set of autolinks, you must map autolinks that you defined before the upgrade to a new context, Service Provider, if you want agents to share the same rules. The application does not automatically remap existing rules.
For rules that use FND function, the Function type must be of INTEROP JSP type.
To create an autolink to a solution, you can define the following:
Define the function:
Function type = “JSP INTEROP”
HTML call = “csksxvm.jsp”
Create an autolink to a JTT view solution page:
Destination Type = “Function”
Destination Parameters = “nSetNumber”
Define the function:
Function type = “JSP INTEROP”
HTML call = “OA.jsp?page=/oracle/apps/cs/knowledge/solution/search/webui/SolViewPG&cskDLink=OA”
Create an autolink for a dynamic link to an OA view solution page:
Destination Type = “Function”
Destination Parameters = “cskSolNum”
With this page you can test the effects of an autolink for text for a given context. You can select a subset of links to test. This page shows how the autolinks are applied and the log list of possible errors in the text that prevent the link to be rendered.