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.3K All Categories
- 70 General
- 11 Training
- 206 Installation / Setup
- 1.1K Flows
- 109 Rules
- 268 Administration
- 212 Portal
- 496 General Q & A
- 708 Forms
- 338 Reports
- 3 Designer Extensions
- 48 Example Flows
- 56 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 184 Pages
- 5 Process Mining
- New Features
- 182 Datastructures
- 69 Repository
- 228 Integrations
- 28 Multi-Tenant
- 27 SDK
- 81 Modules
- 57 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 130 Lunch And Learn Questions