Invoke button (custom action) disable on TaskSpace 6.7SP1

Hello people,

We have application working on Documentum 6.5 SP2 and this application works fine. It is TaskSpace application with first generic form.

We have to move our application on 6.7 SP1 environments.

Everything works fine except one button (Invoke button who calls custom action).

This button is always disabled. It is a part of generic form (on initialization we get en error - in attach)

We tried to recreate new form in FB 6.7Sp1, create new action with no success.

Tomcat: 6.0.32. JRE 1.6.0.26

Have you any idea?

Thanks.

tomcat6-stdout.2013-04-17.log

localhost.2013-04-17.log

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Ela

Thank you Sakhi

Yes, ts_action_plain.xml was ok.

But, one thing very confused us: we have 3 versions of presets inside application: 6.5SP2, 6.0 and 6.7.

We deleted ts_application, recreate new one (including actions, importers, selectors etc), add custom actions to ts_action_plain.xml again and now it works.

All comments

shahi

Hi Ela,

Please check is there any required input parameter for that custom button.

May be you are missing to pass the parameter value.

Ela

Thank you shahi,

First of all we though that is something behind permission. but permissions on WF, cabinet and folders are OK.

then we changed to all fields required="false". As we can see Import action (TS embedded action) is also disabled.

We can start action over direct link: server:8080/taskspace/action/<action_name>.

AlanZ

Your question has been moved to the Documentum developer community where it has a better chance of being answered.

Haroon_A

Can you make sure that your ts_action_plain.xml for your app has the entry for your custom action?

Ela

Thank you Sakhi

Yes, ts_action_plain.xml was ok.

But, one thing very confused us: we have 3 versions of presets inside application: 6.5SP2, 6.0 and 6.7.

We deleted ts_application, recreate new one (including actions, importers, selectors etc), add custom actions to ts_action_plain.xml again and now it works.