Using #LD-notation
#LD notation is used for displaying language-dependent information. #LD notation is mainly used in process tracking and processing notification, but it can also be used in scripts that are stored in the script library.
Syntax
Value=#LD[<language>|<language code>](<key>,{<Parameter>}*)#
where:
|
<language>|<language code> |
(Optional) Language or language variant for the output |
|
<Key> |
Basis string with place holder. The place holder syntax corresponds to a format place holder in VB.Net ({0} to {9}) |
|
<Parameter> |
Parameter for replacing the place holder (comma delimited) |
Table 136: Using #LD-notation
|
Process tracking |
Job.ProcessDisplay |
Mapped to DialogProcessStep.DisplayName |
|
JobChain.ProcessDisplay |
Mapped to DialogProcessChain.DisplayName |
|
JobEventgen.ProcessDisplay |
Mapped to DialogProcess.DisplayName |
|
Process handling notification |
Job.NotifyAddress |
|
|
Job.NotifyAddressSuccess |
|
|
Job.NotifyBody |
|
|
Job.NotifyBodySuccess |
|
|
Job.NotifySender |
|
|
Job.NotifySenderSuccess |
|
|
Job.NotifySubject |
|
|
Job.NotifySubjectSuccess |
|
|
JobRunParameter.ValueTemplate |
On in the MailComponent process component |
| Templates
|
DialogColumn.Template |
|
|
DialogColumn.CustomTemplate |
|
| Formats
|
DialogColumn.FormatScript |
|
|
DialogColumn.CustomFormatScript |
|
|
Task definitions |
DialogMethod.MethodScript |
|
| Insert values
|
DialogObject.InsertValues |
|
|
DialogTable.InsertValues |
|
|
DialogTree.ListInsertValues |
|
|
DialogSheet.InsertValues |
|
| Selection scripts
|
DialogTable.SelectScript |
|
|
DialogObject.SelectScript |
|
|
Process generating scripts |
Job.GenCondition |
|
|
Job.PreCode |
|
|
Job.ServerDetectScript |
|
|
JobChain.GenCondition |
|
|
JobChain.PreCode |
|
Related topics
Using #LD notation in process tracking
For language-dependent representation of process information, a relevant template must be defined to display the captions in the active languages.
The captions for language-dependent text are entered in DialogMultiLanguage when the script is compiled. A key (column Entrykey), the language and the translation (column EntryValue) are entered into the table. The key should be in the corresponding default language. If a language caption has not been entered, the key is used as the display text. Use the Language Editor to add translations for the captions in other languages.
Example
A change is made to an employee. The language-dependent process information could be formulated as follows:
-
Value template for the process information on the Update event
Value = #LD("Change of properties of person {0}.", $InternalName$)#
-
Templates for the display texts in the DialogMultiLanguage table
|
Changed properties of employee {0}. |
English - United States [en-US] |
Changed properties of employee {0}. |
|
Changed properties of employee {0}. |
German - Germany [de-DE] |
Änderung der Daten der Person {0}. |
With InternalName = JBasset, the following display texts are produced in the process view.
|
English - United States [en-US] |
Change of properties of person JBasset. |
|
German - Germany [de-DE] |
Änderung der Daten der Person JBasset. |
Related topics
Example of specifying the language or language variant
#LD notation supports the specification of a language or language variant. This is particularly useful in cases where users need to receive system messages in their preferred language.
Examples
-
Output in the default language:
Value = #LD("Test: {0}", <parameter>)#
Value = #LD[""]("Test: {0}", <parameter>)#
-
Output always in English
Value = #LD["en-US"]("Test: {0}", <parameter>)#
Value = #LD["english"]("Test: {0}", <parameter>)#
-
Using a variable:
Dim lang As String = "en-US"
Value = #LD[lang]("Test: {0}", <parameter>)#
You do not need to enter the language in square brackets, it is optional. However, it is important that the language statement is a String expression. If the language is not specified or the resulting String expression is empty or Nothing, the language currently set for the application is used for translation.
Script library
The script library contains source code for all the scripts used in One Identity Manager. The default scripts that we supply cannot be edited. These scripts are overwritten during schema installation even if they are used in custom scripts.
NOTE: You can find detailed examples for syntax and usage of scripts on the installation medium in the QBM\dvd\AddOn\SDK\ScriptSamples directory. You can find examples of unit tests under QBM\dvd\AddOn\SDK\UnitTestSamples.
Scripts are displayed under Script Library in the Designer. You can gather all the information about usage, for example, in column definitions, processes, or other scripts, in the script overview.
Use the Script Editor to create, edit, and test scripts. To use Visual Studio's more extensive debug and edit options, edit, and test the scripts in the System Debugger.
Detailed information about this topic
