ExecutePythonScript step WorkingDirectory input
Comments
-
Hi
We are trying to execute queries in Decisions using the ExecutePythonScript step. We see there is an input, namely WorkingDirectory. Our scripts reside in a different domain than the machine where we have our Decisions installed. How do I get past this?[img]att1[/img]
-
The [b]Working Directory[/b] relates to the directory that the script would be looking for if it has to do anything related to the directory such as inserting something at a particular location or fetching the file count from a specific folder. This input field doesnt refer to the place where the Python script resides. If you can bring the scripts in Decisions by establishing connections to the other machine, you can provide them as the [b]ScriptFile [/b]input, and you should be good to execute them without any issues.
Howdy, Stranger!
Categories
- 4.4K All Categories
- 86 General
- 13 Training
- 212 Installation / Setup
- 1.2K Flows
- 112 Rules
- 282 Administration
- 216 Portal
- 501 General Q & A
- 719 Forms
- 353 Reports
- 3 Designer Extensions
- 48 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 8 Javascript Controls
- 189 Pages
- 5 Process Mining
- New Features
- 187 Datastructures
- 71 Repository
- 233 Integrations
- 30 Multi-Tenant
- 27 SDK
- 81 Modules
- 60 Settings
- 27 Active Directory
- 12 Version 7
- 36 Version 8
- 143 Lunch And Learn Questions