WDK Action Button disabled within TaskSpace Form

Dear All,

Within my taskspace application, I added a new basic action "rejectworkflowtask", by adding the following line to "ts_plain_actions.xml" file of my application

<plain-action id="rejectworkflowtask" desc="Reject a workflow task without calling form.save()" />

And added a new invoke button in my form that is calling this action, but, the issue is that the button is disabled.

I have also added in the input parameters of the invoke button a reference to the task ID to the parameter "objectId" but it still doesn't work.

Can any one elaborate on the cause/fix of this issue?

Thanks in advance.

Find more posts tagged with

Documentum

Comments

Haroon_A

Did you deploy your action in your taskspace, custom folder (action definition, JSP, class etc...)? I have noticed that if your custom component is not deployed on your app server, your action button is disabled.

Hosam Salem

Thanks a lot Ahmad for your quick reply.

Based on the following document (https://community.emc.com/docs/DOC-7640) and "TaskSpace configurable Actions Defintions", I can add a new basic action to my taskspace application that is referring to a custom or a built-in WDK action, and in my case, I'm referring to a built-in action (rejectworkflowtask).

Any other suggestions?

Haroon_A

If it is a built-in action, do you still need to modify ts_plain_action.xml? I believe -- please correct me if I am wrong -- modifying ts_plain_action.xml is for your custom actions?

Hosam Salem

Well, Referring to the document "TaskSpace configurable Actions Defintions":

The ts_plain_actions.xml file contains all of the WDK actions (standard or custom) that are available forconfiguration within a TaskSpace application. The list does not contain every WDK action as many of themare not applicable to use in TaskSpace.

You may be right, but, does this actually mean that the "rejectworkflowtask" action cannot be invoked within my application form or I'm missing something within action/button configuration?

Anyway, thanks a lot for your comment, it is really useful.

Haroon_A

Try this.

Extend the 'rejectworkflowtask' action under your 'cutsom' layer of your taskspace (You don't need to modify any behaviour or definition, except the action id, i.e. my_rejectworkflow), and then use that custom action in your ts_plain_action.xml.