From 88269f6460c36d11da1b18ae14a7b94d67cc4a91 Mon Sep 17 00:00:00 2001 From: gardian12 Date: Tue, 22 Oct 2024 22:12:37 +0200 Subject: [PATCH] Update background-mode.md Added corrections --- src/user-guide/repo-settings/background-mode.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/user-guide/repo-settings/background-mode.md b/src/user-guide/repo-settings/background-mode.md index e31a46430..2c725e760 100755 --- a/src/user-guide/repo-settings/background-mode.md +++ b/src/user-guide/repo-settings/background-mode.md @@ -46,7 +46,6 @@ If credentials are required for accessing the repository, you will have to maint ### Custom background modes -Implement interface `ZIF_ABAPGIT_BACKGROUND` in a global class, and it will automatically show up in the abapGit background settings, making it possible to configure and run for a repository. -While using the standalone version of abapGit implement the include `ZABAPGIT_BACKGROUND_USER_EXIT`. -Both ways of adding a plugin can exist in parallel, but due to the restrictions of dynamic method calls global classes are available by the developer version only. Same is true for include based implementations. These are execute by the standalone version only. - +Implement interface `ZIF_ABAPGIT_BACKGROUND` in a global class, and it will automatically show up in the abapGit background settings, making it possible to configure and run for a repository. While using the standalone version of abapGit implement the include `ZABAPGIT_BACKGROUND_USER_EXIT`. +All implementations of the interface as well as the local include will be determined automatically. +Both ways of adding a plugin can exist in parallel, but due to the restrictions of dynamic method calls global classes are available within the developer version only. Same is true for include based implementations, which are executed by the standalone version only.