From b0fd3666dd9fa91527684b7944c98e85f5429a77 Mon Sep 17 00:00:00 2001 From: Morten Wittrock Date: Tue, 8 Nov 2022 16:45:18 +0100 Subject: [PATCH] Update define-a-local-script-step-03b32eb.md Clarified the purpose of the Script Function field. --- .../ISuite/50-Development/define-a-local-script-step-03b32eb.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/ISuite/50-Development/define-a-local-script-step-03b32eb.md b/docs/ISuite/50-Development/define-a-local-script-step-03b32eb.md index 87f86e24..38e5bf28 100644 --- a/docs/ISuite/50-Development/define-a-local-script-step-03b32eb.md +++ b/docs/ISuite/50-Development/define-a-local-script-step-03b32eb.md @@ -116,6 +116,8 @@ Cloud Integration provides a Java API to support this use case. > - In tab *General*, you can edit the name of the Script step shape. > > - In tab *Processing*, you can choose *Select* to browse for a script file. + > + > - The *Script Function* field on the *Processing* tab holds the name of the script function you want to call. However, if the function has the default name (`processData` for both Groovy and JavaScript) you can leave the field empty. > > You can add external jar files using the *Resource* view. You can then invoke functions from these external jar files in the script. You can also upload a script from your computer using *Upload from File System*.