Pricefx Studio
Pricefx Studio helps you improve productivity when developing calculation logics during project implementation. With Pricefx Studio you can fetch calculation logics from remote partitions, test them and deploy them at remote partitions. Pricefx Studio runs as an IntelliJ IDEA plugin. You can use either IntelliJ IDEA Ultimate (paid version) or IntelliJ IDEA Community Edition (free version)
Advantages
With Pricefx Studio, you can:
Fetch calculation logics and other Pricefx objects from a selected partition.
Deploy calculation logics and other Pricefx objects to selected partition(s).
Develop the calculation logics in IDEA leveraging the integrated development environment (IDE):
Edit the Groovy logic elements using the rich Groovy editor.
Make use of autocomplete for Pricefx Public Groovy API.
Make use of Groovy documentation for Pricefx Public Groovy API.
IDEA further allows:
Groovy variables refactoring
Groovy code auto-formatting
Tracking logic elements changes on a code line level (requires GIT repository or other VCS)
Check the code quality while coding
Test calculation logics execution.
Test Groovy code snippets in Pricefx Groovy consoles.
Design Datamart / Data Source and QueryAPI queries using Groovy and SQL console and generate Groovy code out of it to be used in the logic.
Support
If you need immediate support, you can contact the development team via Studio Teams channel or via Helpdesk portal. The bug reports and new requirements can be logged under the projects PFAUT (Studio plugin related) or PFIM (Package tool related).
Next Sections
- How To (Studio)
- Install Studio
- Install Previous Versions (Pricefx Studio)
- Create New Project
- Connect to Pricefx Partition
- Code Quality in IDEA
- Fetch Logics
- Run Logic Test
- Deploy Logics
- Test Highcharts
- Test Rest API Calls
- Create Custom REST API Using Logics
- Important Changes in the Upcoming Studio Version
- Studio - Enhancements to UX in the Logic Editor
- Upgrade Studio Project Libraries
- Reference (Studio)
- Studio Landscape
- Pricefx Project Structure
- Groovy Consoles
- PfxFetch Toolbar
- PfxMetadata Toolbar
- PfxDeploy Toolbar
- Logics Editor
- Metadata Editor
- Message Templates Editor
- Publishing Templates Editor
- HTTP API console
- Components and Components Marketplace
- Export Schema
- Keyboard Shortcuts in Studio
- Supported Object Types
- Supported Logic Types
- Troubleshooting Pricefx Studio
- About Pricefx Studio
Comments
Actually that behavior was the desired one, the reason for this was to be able to release different objects at once. The filter was meant just to support the selection process and to indicate if all / some objects will be deployed, there is the 3-state checkbox next to calculation logics. But I will think about how user can be informed how many objects will get deployed.
The cancelling process should be really not harmful, since it finishes the currently deployed object to certain partition and just stops the next deployment of the other objects. So that error is not related to the cancellation. That error means that you have an element in the logic.json defined, but there is a missing groovy file (but could also be a false alert, since I received a bug related to that).
hello,
I’ve come up with an issue using the studio, if I want to upload Calculation Logics back after modifying them in IntelliJ, and I do a selection using the filtering input:
This will only filter the list in the view, not the selection itself, and all the Calculation Logics will be updated. Now once I realized all the logics where being updated, I cancelled the operation and this created a situation in the pricefx portal where some of the logics where there and the code was there, but the live logs on the partition showed warnings along the lines of “found a calculation logic without active logic element“ (can’t recall the exact message), the solution to this was to open the logics in the portal, save and close them. But it seems cancelling the operation from Pricefx Studio before it completed created this situation. Perhaps it would be good that the filter feature in the above image would clear the selection on the logics which aren’t part of the selection, that would be the behavior I expect.