Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X
Hi Team,
Need some help from the community.
Unable to see the Actions list when click on Actions for the WTDocument in Infopage.
When select the WTDocument in folders page and click on Actions it does show all the list.
Any idea wht could be the probable causes.
Thanks in advance.
Solved! Go to Solution.
Hi Thanks for reply.
Digging further found the cause.
There was a issue with one of the tag in customactions.xml
After fixing this things are working fine.
Do you see anu erros in the logs ?
Nopes
Enable client customization and reload action :
1- Site > Utilities> Preference Management> Client customization :
2- client customization > tools > reload actions :
Sorry no success.
I guess need to check in custom-ActionModel.xml if something is wrong
if you have an issue with the action models , you should have some kind of errors prints in the log
Is it just the actions drop down on WTDocuments page? What if you select actions on a different object or that same object say in a folder browser or search results via right click? Does it appear there? WAG but since some of this might be javascript dependent, you might try clearing browser cache, especially if this is one user on one machine. Does this appear for other users with same access rights?
Lastly, are there any customized actions or actions filters added? One of those might be misbehaving.
Hi thanks for reply.
This is working for fine for all other objects.
Its failing only for WTDocument.
Strange thing is there are no logs generated in MS.
Tried replacing the customaction-models.xml from working server still the issue persists.
So you do have custom actions for WTDocuments menu? Could one of them be misbehaving or caught in a loop? For any of those customizations, filters, etc, turn on DEBUG logging to see what its doing. Or you coudl try removing them one by one to see which one is at fault.
Hi Thanks for reply.
Digging further found the cause.
There was a issue with one of the tag in customactions.xml
After fixing this things are working fine.