...
Python Engine version | Supported Pricefx Platform version | Note |
|---|---|---|
v1 | 9.4 | No longer maintained |
v2 | 9.4 | No longer maintained |
v3 | 10.0 | |
v4 | 10.1 | |
v5 | 10.2 | |
v6 | 10.3 | |
v7 | 10.3, 10.4 | |
v8 | 11.0 and later | |
v9 | 11.1 and latter | |
v10 | 12.0 |
For more details on the changes provided by each version, see the Changelog page.
...
See https://pricefx.atlassian.net/wiki/spaces/KB/pages/4346413172/Run+Python+Scripts#Script-sample for examples on how to declare and use these parameters.
See https://pricefx.atlassian.net/wiki/spaces/KB/pages/3862691926/Job+Trigger+Calculations#Parameters-size-limitation for limitation on script/parameters size.
Monitoring
Monitoring of a triggered job is possible in Grafana, after you filter by pricefx_heartbeat_task_id. For details see Job trigger calculation in /wiki/spaces/EN/pages/4120346722.
To add additional logs on model-by-model basis, attach to the model file
| View file | ||
|---|---|---|
|
| Code Block |
|---|
{
"rest_calls": true
} |
REST requests and responses will be logged to the console, meaning they can be found in Grafana.
To add the file, go to the model > click ... in the top right corner and select Attachments > Upload.
pyfx Python API
From inside the Python script, the pyfx module is available to interact with the partition. Attached is the complete documentation for the versions of the pyfx module.
Starting with version 9, the documentation for the latest Pricefx Python API version is available at https://developer.pricefx.eu/pricefx-api/pyfx/. Documentation for v8 is available here.
Here is the documentation for previous versions:
v1
| View file | ||
|---|---|---|
|
...