...
This URL will be resolved and used by the client if it is found in a form and offers the user a behavior similar to a dynamic list field.
The URL can be configured with the placeholders that are resolved by the client. Placeholders must be entered with brackets like {placeholder name}.
List of placeholders:
Placeholder | Description |
|---|---|
situation | Possible resolved values are |
objecttype | The technical name of the object type of the opened object (no value in the situation search). |
objectid | The object Id of the opened object (no value in the situation search). |
field:<field name> | The value of a qualified technical field name of the opened object (no value in the situation search). |
clientlocale | Beginning with version 9.16 LTS, the 2 characters-long language code of the |
schemalocale | Beginning with version 9.16 LTS, the 2 characters-long language code of the |
Including a Plug-in in the Client-Service
...
To check the new plugin, it must be placed in the directory described above and the client-service must be restarted.
Form script usage for dynamic list fields
The endpoints can be directly used for string properties which are classified as a dynamic list. The following form script gives an example:
| Code Block |
|---|
// fill a dynamic list field with catalog data
var greekalphabet = scope.model.stringforalphabet
scope.api.http.get('/dummy','/app/api/autocomplete').then(
function(result) {
greekalphabet.setList({
entries: result.data.entries
});
},
function(error) {
scope.api.util.notifier.error('Failed to load greek alphabet',error+'');
}
) |
To produce the data used by the script, the following plug-in must be placed in the folder “autocomplete-plugins”.
| View file | ||
|---|---|---|
|
The data looks like this:
...
Plug-in Examples
You can find some plug-in examples in the tutorial section: