Action Not Working in Workspace

Difficult to say as there isn't a list of what is not implemented in Workspace.  I suggest you try it in webaccess first.

If it works in WebDesk/WebAccess but not in Workspace, then I suspect when you log this as an issue with support they will say that it isn't a bug.  They will probably encourage you to raise an ER for this to be supported in Workspace.  You might then ask for the list of features that are not implemented in Workspace and it is likely that you will be told no such list is publicly available.

I'm not saying I agree with this approach by LANDESK, just setting the scene for the most likely answer you will get.  (I hope to be wrong in a good way!)

I had noticed this behavior on earlier versions of workspaces.

What version are you on Motaz?

Also, the Contract opens fine but the actions to create the related object are the issue, correct?

Something else you might try...

Setup a window rule for the related object you're creating from the action.

I have seen errors in workspaces from something as silly as a label with just a space in it.  Any chance you have any labels where you just put a space in effort to hide the label on your contracts window?  Self Service/Web Desk will recognize the space but workspaces will though an error.  Interestingly enough you can put a space in a group box title and workspaces will work fine with that.  Let me know if you have any questions.

Regards,

Will McCoid | Lead ITSM Consultant | Network Consulting Services, inc. | Desktop, Network & Internet Security

I'd report this to support if I were you, just keep in mind my previous thoughts on the likely response.

Did you find a solution to this?  I'm awaiting a response from support on a similar issue and just came across this post.

Thanks,

Tom

Thanks for getting back to me.

We're on 2016.2 and seeing this issue on an action I've created - will see what support have to say!

Tom

Very similar to what you were experiencing...

I'm creating a signature capture solution using LANDESK and a web application we've developed to record the signatures.  There's a collection on incident called 'Signature Capture' with an action 'Add Signature'.  No problems invoking this action in Workspaces.

From the Signature Capture collection there is another collection 'Signature Capture Item' where the items that we're collecting a signature for are recorded.  This collection has an action 'Add Item'.  This is where the error occurs.

Again as you found, this works no problem in web access and console.