Hi Colin, thank you for the API reference on Workflows!
Currently we’re not seeing the ‘Visual Builder’ in our IDN Beta as mentioned in the documentation.
Will the Visual Builder be launched in the coming days?
@BartCoolsUpright, please reach out to your Customer Success Manager or Account Executive to check the status of your request. It likely has been approved but not activated yet, and one of those two persons should be able to move it along.
Is there a place to get more updates on Workflows other than the documentation page? Our tenant has the beta but I am trying to find more information or examples of how to use the various triggers and actions.
The Workflows Beta team also prefers any feedback inside the tool itself. You should be able to go into the tool and give feedback there as well if you have questions. They have a team monitoring that as well.
@colin_mckibben I was unable to see a way to leave feedback in Tool itself, however I did import one of the examples provided and I get “output was not a valid map”. Same thing I got when I tried to create my own. Obviously this is a very bad first impression and the message is not even remotely helpful to understanding what this occurred, where to fix. I’m hopeful others will join the beta in order to encourage SailPoint to put more examples up and enrich the documentation as we want to be activity engaged so that a viable solution is available for us all.
“error”: “output was not a valid map”
I was getting that same error for “Send Email” until I put a $ into the Templating Context. It would be nice to have a better understanding of how to work with the Templating Context. I understand the JSON path, but how Templating Context should be formatted to be used in the Body, Subject, etc., is what I am missing.
Further, if I include a $ in the Body, rather than getting the JSON object formatted the same as it went in, it’s formatted differently, with a lot of map interspersed throughout. Perhaps that’s a result of what I put in the Templating Context, but it’s not intuitive.
Some basic examples in the documentation would go a long way, in my opinion.