Hi all,
Just wanted to run this past the community incase anyone has had a similar experience.
We have recently built a 67SP2 TaskSpace pointed at a 6.6 Content Server/Repo. Standard build with the 6.7SP2 dar files deplyed in the repo.
Seeing some strange behaviour where the Unassign task action is no longer available to non admin users via TaskSpace 6.7 SP2. We have a second app server running the original 6.6 TaskSpace and if the user logs in using that client the actions are available.
We dont have any custom actions relating to task unassign in either of the webapps.
Only thing I have noticed is the version lables on the actions in Cabinets/System/Applications/CLIENTAPPLICATION/Actions Client application is 6.6 (ActionVersion_6.6) but the core TaskSpace actions have been updated to 6.7 (ActionVersion_6.7)
Anyone know what might be causing this ?
many thanks
Hoo
