Skip to content

Clarified the purpose of the Script Function field #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 17, 2022
Merged

Clarified the purpose of the Script Function field #2

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b0fd366
Update define-a-local-script-step-03b32eb.md
mwittrock Nov 8, 2022
3ce0c12
Merge branch 'main' into patch-1
je-hal Nov 9, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/ISuite/50-Development/define-a-local-script-step-03b32eb.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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*.

Expand Down