Problems starting an SLA from a business rule

[geek1]

Anyone have experience starting an SLA from a business rule?

What I'm doing is pretty basic:

//p1 = sysid of SLA
var sla = new GlideRecord('task_sla');
sla.sla = p1; // Priority 1 OLA Response
sla.task = getTask.sys_id;
sla.insert();

The above starts the SLA exactly when it's supposed to, there's no problem there. However, when I drill down into the SLA itself (from Task SLAs on the incident form) and click the reference icon for this specific SLA.. I click 'Show Workflow' and it loads an empty workflow. The workflow is named properly on top of the page but it loads empty.

I got worried so I added the Workflow field to the Task SLA form and sure enough, it loads shows the name of my workflow exactly how it is. When I click Show Workflow it loads an empty workflow, too! It's so strange. The SLA itself looks perfect, but the workflow doesn't fully attach to it.

When you manually load an SLA via a business rule do you need to do anything beyond what I did above to get the workflow to attach and run properly?

[Aaron40]

There are problems when you try to start SLAs from business rules. If you script it out, it'll start the SLA but it'll actually be empty (at least in Aspen and Berlin). You will see the SLA attached to your record but if you click on it, there isn't a workflow or anything behind it. It's like a shell.

I had a conversation with SN support at one point on trying to do this and they said it can't be done. I don't know if that's still the case in Calgary or will be in Dublin but I wasn't able to get an SLA to start properly from a business rule.