You are viewing limited content. For full access, please sign in.

Question

Question

What are the major changes needed to make custom actions in web access 10.2

asked on May 2, 2018

Is LFSO90 backwards compatible with WebAccess 10.2? I have some  CustomActions that were written using LFSO90 and also use the 9.0 WebAccess libraries. I understand that I will need to update the web access references so they use 10.2 references but will I also need to change LFSO90 so its using the 10.2 version?

0 0

Replies

replied on May 2, 2018

If your code uses the repository connection that WA has already established, then it does need to be using the same version of the libraries as WA.  Note that for version 10, Web Access has switched to Repository Access instead of LFSO.

0 0
replied on May 3, 2018

Ok, so if I was usingWASession =  WebAccessSession.GetSessionObject(Session);

and WARepo = WASession.ConnectionManager.GetLoggedInRepository(Session);

then I need to use RepositoryAccess instead to get the repository and session info for the users current web access session? I've used RA to connect via a workflow SDK but not to connect to a WebAccess session.  I'm really just trying to get the repository name of the current web access session.

0 0
replied on May 3, 2018

If all you need is the name, there is ConnectionManager.GetLoggedInRepositoryName().  Note though that Web Access does allow users to be logged in to multiple repositories, so you are better off passing this as a parameter from the browser to your action.

0 0
replied on May 7, 2018

Ok, so the CustomActions.xml and CustomTools.xml have been reworked to use the newer version 10.2 syntax but we are only seeing one of the custom actions tools show up in the document viewer even though two are listed. Can anyone look at the CustomActions file attached and tell me if something is wrong? 

0 0
replied on May 8, 2018

It looks ok to me.  I'd suggest the usual troubleshooting approach: make the one that doesn't work more and more like the one that does until it starts working.  I wonder if we have some assumption about the allowed characters in the id, or something like that.

0 0
replied on May 10, 2018

Thanks for the input. The custom actions are showing up now but the issue is that the icons are not showing up like they should be. Both of the custom actions now have the same generic "Custom Actions" icon on the toolbar. How can I change this so I can use the icons that were created specific to these actions? We have our own, custom logo icons we want to use.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.