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 `create`, `edit`, and `search` depending on the situation the corresponding form is used.
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 `Application` language the user has configured in the client settings.
schemalocale	Beginning with version 9.16 LTS, the 2 characters-long language code of the `Definition` language the user has configured in the client settings.

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:

...

You can find some plug-in examples in the tutorial section: