To support last mile manual provisioning we are setting up the ITSM Generic Connector to create a Jira ticket for any manual tasks.
We are having some issues trying to figure out what we can and cannot use from Velocity within the ticket creation part of the connector.
I have seen some pages that talk about the use of Velocity in the ITSM connector buts its a bit light on details and looking for any more detailed documentation that can provide a clear list of what is supported.
If that does not exist does anyone have any guidance on if any of the Velocity DateTool methods are supported?
We have tried using the date tool command from the documentation as well as the $sptools and version 2 template variables listed Using Email Templates - SailPoint Identity Services with no luck.
Anyone have experience working with Velocity within the ITSM connector or any ideas that could point us in the right direction?
Hello again!
During ticket creation, you can only access attributes/modules that would be in the provisioning plan as far as I know - this should include most you can use Working with Velocity Template Language in ITSM Ticketing - Compass.
In essence that constrains you to only information available in the context of a provisioning operation.
You could also set up a before provisioning rule to generate ticket fields according to some docs but I’ve no experience with that.
Hi Marten,
Thank you for the advice.
what we have landed on is we have added a DueDate attribute to the provisioning policy and then using a transform to calculate the due date at that point.
We then use a pre-provisioning rule to ensure it is passed on for all provisioning rules (create, update, etc) so if we need to change the calculation then we can do it without needing to update the pre-provisioning rule.