The logs should contain more details, usually with a stack trace of the error/exception.
The line you mentioned doesn't have enough details to conclude what happened.

OK, that is good.
Did you attach the log? I can't see it.

Can you send the EngagementDesigner.log file so we can check why the undeploy is failing?
Also, which version of Breeze are you running? (you can run the command: swversion in an ssh terminal on Breeze to find out)

Could you please get us the ED logs of the deployment of your task?

ssh to the Breeze server and type: ce dlogon FINE EngagementDesigner
In ED Admin Console, under Bundles tab:
- check your task and click undeloy
- check your task and click deploy

In ssh terminal
- type ce dlogoff EngagementDesigner
- go to /var/log/Avaya/services/EngagementDesigner/
- send us the file EngagementDesigner.log

Thanks.

Your SampleTask-1.0.0.0.0.svar file needs to be installed on the ED Admin Console (not on System Manager) under the "Bundles" tab: upload the SampleTask-1.0.0.0.0.svar file , then deploy it. After that, go to the ED Designer page (refresh it if it was already open) and you will see your dynamic task in the palette.

The list is in the command prompt itself.
But apparently, there is an issue in your case: your screenshot shows this message :"Your filter doesn't match any archetype".

Can you try this:
1. Go to your local maven repository folder : C:\Users\<username>\.m2
2. You should see there a file named archetype-catalog.xml.
3. Copy the file archetype-catalog.xml to C:\Users\<username>\.m2\repository
4. Try the command again

Note: If you don't see archetype-catalog.xml file under C:\Users\<username>\.m2,

1. Go to C:\Users\<username>\.m2\repository
2. You should see a file named archetype-catalog.xml.
3. Copy the file archetype-catalog.xml to C:\Users\<username>\.m2
4. Try the command again

Thanks.

Hi katalin,

It would be great if you could also attach the WAS log file TextLog_<Date>_<Time>.log that can be found at /var/log/Avaya/sm/.
You could also upgrade to the latest GA version of ED: 3.3.
Let us know.

Thanks,
Eli.

Hi,

The functionality for publishing Engagement Designer Dynamic tasks to Snappstore was added in ED 3.2 Feature Pack 1, and is available in the ED SDK 3.2.1.0.00033 available on devconnect site.
ED SDK 3.2.1.0.00033 requires Breeze SDK 3.2.0.1 which is also available on devconnect.

Using the above mentioned ED SDK, generate a scaffolding project and update it with your code.
You will see a new folder “task-svar” in addition to the “tasks” folder.

The properties.xml file where you need to add the supplier id is located in tasks-svar/src/main/resources/.

You can then build your dynamic task svar using the command: mvn clean install –Psvar
You will find your dynamic task svar file in tasks-svar/target/, which can be published to Snapstore.
This svar file can only be uploaded and deployed on ED Admin Console the same way you did with the dynamic task jar file.

I hope this helps,
Eli.