I’m having some trouble with the interface and user-defined fields. I added a new user-defined field to Autotask and it immediately showed up in the Update Ticket Action.
Thanks for reporting this. I’d like to narrow down the issue so we can fix it.
First, some background:
The output data of each step is calculated while that step is expanded.
Imagine you configure a step that outputs a ticket and then save the rule. You then add a new ticket UDF definition to Autotask. You then edit the rule in MSPi, add a new action (without expanding any existing steps), and look for the UDF in the output of the previous step. At that point, the new UDF won’t be present in the output data. If you expand the previous step (to view its details) and allow it to load, and then go back to the new step, the UDF should be present.
So, knowing that, does this problem resolve if you expand the previous step and allow it to load the updated ticket definitions?
We probably need to redesign this behavior in any case, but still let me know if this describes the issue you’re seeing.
I tried to follow the steps you outlined above. But the issue processes will always be processed as a video. Please let me know if I did what you were asking.