Input does not look to be editable? What am I doint wrong?
We haven’t seen this yet. I’ll shoot you a DM to troubleshoot!
Evaluator does not work correctly: ISC Workflows JSONPath validator wrong fully marks expression as invalid - #11 by lukas_ceremeta
This is great! It’s really a nice one.
A quick suggestion here:
Like the same, if there is any discovery for testing transforms before pushing into the tenant will be more useful.
Even though there are ways, all those can be done only after pushing those transforms into the tenant.
1 Like
Update!!!
@LukeHagar made a major enhancement to the JSONpath evaluator. It now uses the exact same libraries used by our event triggers and workflows service. This means the outputs should be exactly the same as what you would find in our product. This change involves sending the input and JSONpath query to an API backend that SailPoint controls so it can execute against the correct library. You will now notice a “RUN” button, which you will need to click to run the JSONpath evaluation. As always, please submit a Bugs report if you encounter any issues.
2 Likes
Hi @colin_mckibben,
The Web Services Connectors both use JSONPath as well in the response mapping.
Which implementations do they use? Does either of them match the implementation of either workflow or even trigger, or neither and do they also use a different implementations? If so, are there any plans to add them to this evaluator?
In addition I notice that the evaluator output now returns values like \n and \r instead of prettifying the JSON if the path is just $. Is this new?
Kind regards,
Angelo
Connectors use jayway jsonpath, which is the same as event triggers. That’s something we can make more clear in the evaluator dropdown.
Can you please open an issue on GitHub · Where software is built for the formatting issue?