Dynamic Task Types in Engagement Designer

[ander548]

I got the correct archetypes loaded and now I can successfully create the scaffolding for a dynamic task, but I get several warnings and errors when I try to build. Attached is the command line output of me creating the scaffolding, changing to the directory of the mytask it created and running "mvn clean package". One weird error is this:

[ERROR] error reading C:\Users\canderson\.m2\repository\com\avaya\collab oration\
api\avaya-aura-collaboration-api-3.1.1\3.1.1.0.311008\avaya-aura-collaboration-a
pi-3.1.1-3.1.1.0.311008.jar; error in opening zip file

This file exists in this path with ".lastupdated" at the end, and it doesn't appear to be a real jar. It's contents are just this text:

#NOTE: This is an Aether internal implementation file, its format can be changed without prior notice.
#Mon Sep 19 08:41:30 EDT 2016
https\://repo.maven.apache.org/maven2/.lastUpdated=1474288890511
https\://repo.maven.apache.org/maven2/.error=

[agrace]

I just ran into this issue also. I solved it by installing the previous release of the Breeze SDK. (the 3.1.1 version, NOT the 3.1.1.1) There are some version mismatches when using the latest versions of each SDK.

That said, it builds, installs, and allows me to run it in a workflow but seems to have some issues still. I can't get it to log anything and it breaks when I try to play VXML

[ander548]

Thanks SO much for that tip! I've been beating my head against a wall for a week, and once I installed 3.1.1 it worked!! I was able to build a skeleton dynamic task and get it to show up in ED as a snap-in in my drawer. Thanks again!

[agrace]

Now I just need to figure out why my task stalls the workflow when I do anything more than return

[ander548]

I haven't gotten that far yet Do you happen to know the process for getting your dynamic task to show up in the EDP toolbar? I installed my svar and had it showing up in my drawer on the toolbar, but then deleted the old one and re-loaded a new svar and now I can't get it to show up. I saw somewhere it said to reboot the cluster, so I tried that and now a bunch of the standard drawers are missing! What controls what shows up in the toolbar? Also, any idea on how you can test the dynamic task without loading it into a workflow? I tried the Admin Console URL to create an instance of it, but it doesn't show up there. Thanks, and if I get that far I'll let you know if mine stalls the workflow!

[agrace]

Make sure that you have all of the following in your tasks.json file (specifically the mapping and properties) It seems like if this file doesn't follow the schema, Engagement Designer kinda just craps out.

Also, there is some significant lag between installing a version of a snap-in and the changes being reflected in the workflow editor. Rebooting the cluster seems to force the change to take but I've had better luck with just going for a short walk around the office and coming back.


[
{
"name": "Sample",
"mTypes":
[
{
"name": "Hello",
"snapinVersion": "3.0",
"displayName": "Hello",
"tag": "hello",
"svg": "hello",
"helpUrl": "hello.html",
"tile": "blue",
"serviceName": "CollabDesigner",
"custom": "true",
"nodeType": "activity",
"modelClass": "com.test.breeze.tasktype2.HelloModel",
"executionClass": "com.tes.breeze.tasktype2.HelloExecution",
"mapping": "[\"input\", \"output\"]",
"properties": [
],
"input_schema": "{
title: InputSchema,
type: object,
properties: {
ucid_var: {
type: string
}

}
}",
"output_schema": "{
title: OutputSchema,
type: object,
properties: {
title: {
type: string
}
}
}"
}
]
}
]


I'm really interested in seeing if you run into the same issue that I do...

[ander548]

I used a pretty basic tasks.json like you have when it eventually showed up in the editor (I tried all kinds of things and it just finally showed up so probably wasn't anything I did). But, now I've added some things to the schema and it builds and loads fine, but maybe that's why it won't show up now. Any idea where you'd find out what's wrong with it? I did notice that their basic json doesn't have quotes around things like type: string, but in my editor it liked things like this: "type": "string". I'll maybe check the logs to see if anything doesn't like that, but weird that it just wouldn't show up at all. I deleted it and am reloading just to make sure and I'll give it more time and see...

[agrace]

yeah, the schema parts "json" isn't actually json because the properties aren't quoted themselves. Probably because it would be a pain to escape all of the quotes in the already quoted schema.

That might be your issue

[ander548]

Yeah, I'm trying to test that now, so we'll see. Any idea how you can test the task directly somehow? It would be nice if it showed up with the workflows that you can create an instance of directly to test.

[ander548]

Thanks again! That was why my snap-in wasn't showing up in the toolbar (I assume). I removed the quotes in the fake json and that works. Is yours freezing the workflow in debug? Mine simply takes an input value, adds a string to it and outputs it, just to test the basics and it seems to work fine in debug mode.