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

Question

Question

Custom Toolbar Button

asked on December 14, 2016

Hi all,

I am trying to customize a toolbar button in Client that executes a command to open a web page in a third party web application corresponding to the currently selected entry.

The problem that I am having is that the information needed to be represented in a token for the command needs to pull field values from the currently selected file.

These are the standard tokens for custom toolbar buttons:

%(PID) %(UserName) %(RepositoryName) %(RepositoryGUID) %(HWND) %(DocumentID) %(DocumentPath) %(FolderID) %(FolderName) %(FolderPath) %(SelectedPages) %(SelectedEntries)

 

I have to capture particular field values from this token: %(SelectedEntries)

 

I welcome other suggestions as well! Maybe a business process is better suited?

 

Thank you in advance!

0 0

Answer

SELECTED ANSWER
replied on January 3, 2017

The field values can be retrieved using the Client Automation library, it requires writing a custom SDK application.  This post has sample code for retrieving the field values for the selected entries. There is more sample code in the CustomButtonManager project that is installed with the SDK (in ClientAutomation Samples.zip).

1 0

Replies

replied on January 2, 2017 Show version history

This sounds more like a job for the Connector Tool. Have you looked into that module from Laserfiche. I think it will be a lot easier to configure. 

0 0
replied on January 2, 2017

Hi Chynna,

Thank you for your response!

From what I have learnt about the connector tool, it only works to send information from an external page to Laserfiche.

We already have code that automates the flow of data between our external system and Laserfiche.

We are trying to have a tool in Laserfiche that launches the data in the external system. (Opposite of the connector)

 

I will look into the functionality further though!

 

Thank you

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

Sign in to reply to this post.