 |
ELO add-on modules – installation overview |
This page contains a list of add-on modules for ELO. You need to be logged on as an administrator to install them in the ELO Java Client. The modules are then installed automatically.
If you want to customize scripts, we recommend that you refer to the ELO Java Client documentation.
If you have any comments about the individual modules or would like us to integrate functions, please create a post on the topic ELOscripts in the ELO Community.
Keep in mind that the elodms protocol handler must be enabled for installation. This is usually installed automatically. To register it later, you can call EloActivateJC.exe with the parameter -RegServer.
This script installs all required JavaScript files for ELOas. If a script folder already exists, it is renamed before the update and not overwritten.
Install module now (20.00.000)
Download module (20.00.000)
Install module now (23.00.000)
Download module (23.00.000)
Install module now (23.03.000)
Download module (23.03.000)
This script uses a stamp to forward a workflow. The process corresponds to a built-in function in the ELO Windows Client.
This script generates two buttons in the "Approval" group on the "Document" tab. The first button shows the latest version (not the working version) of an approval document for review. The second button sets the latest version as the working version.
This script allows you to batch assign metadata for multiple documents. The metadata fields for multiple documents with the same metadata form can be changed at once. Placeholders can be used with this function as well.
The ELO Click&Find module allows you to search for text selected in an external program from within the ELO repository.
The "DocumentCompare" script registers as a call event for the "Compare" button in the "Document versions" dialog box. When called, it checks the file extension and then calls the associated compare function. For DOC and DOCX files, the Microsoft Word comparison function is activated via the COM interface. For TXT and JS files, a command line version of "WinMerge" is called.
This script shows a dialog box for entering a logical object ID, an object GUID, or a file ID. After confirming the dialog box, the corresponding entry is displayed in the ELO client.
This script hides the extra text tab if the entry is a dynamic folder and the user is not a main administrator.
This script shows a dialog box for outputting various repository parameters. To determine these values, an Indexserver script is installed that reads out the database.
This script creates a new button in the "Organize" group on the "View" tab that transfers all links of the current entry to a search view filter.
This script monitors the CheckIn script event. If the ELO Outlook macro is used to check in an MSG file, it also checks whether the e-mail contains attachments. These will be filed as additional individual documents and linked to the e-mail document.
The Business Solutions Productivity Tools contain a newer version of the script.
The ELOas library "notify" helps users to automatically send e-mail messages from a workflow or for a workflow. It also automatically generates feed entries.
This script enables communication between ELO Macros for Microsoft Office applications and the ELO Java Client.
This allows you to file Word, Excel, PowerPoint, and Outlook documents to the ELO repository.
Install module now (21.00.014)
Download module (21.00.014)
The "OfficeToPDF" script checks during PDF conversion whether the format of the Microsoft Office document is DOC, DOCX, XLS, XLSX, PPT, or PPTX. In this case, the document is not converted by the ELO PDF Printer, but via the "SaveAs-PDF" function of the Microsoft Office COM interface.
The "OutlookSync" script provides a simple connection between ELO folders and Microsoft Outlook folders. The user can select any folder in the ELO client and display it in an Outlook folder. Additionally, it determines whether e-mail messages are imported from the folder into ELO, whether ELO documents are transferred as e-mail messages into Outlook, or whether to perform two-way synchronization.
The "PrintMarginNotes" script enables you to print margin notes. It creates a button named "Print margin notes" in the "Print" group on the "Output" tab of the ribbon.
The "Print to repository" script enables you to print files to the ELO repository. You can specify which output directory to monitor in the script.
This script creates a button called "Search notes" in the "Search logic" group on the "Search" tab and allows you to search for a term in all existing annotations and margin notes.
This script allows you to search for document version comments.
This script generates a button named "Set default form" in the "Edit" group on the "File" tab to select a metadata form for new documents.
This metadata form is used if no other metadata form has been assigned for that document type.
The script generates a report on the current system settings. It returns lists of current metadata forms, users, ELOix or ELOdm options, workflows, forms, and more. If ELOwf or ELOas are not at the default location in the repository, you need to modify the file "sysinfo_config.json" before using the script.
This script creates a new work area named ToDo in the ELO Java Client. In this work area, you can create projects that contain different areas for tasks. You can prioritize these tasks; their status changes during processing from "Idea" and "Prioritized" through "Processing" to "Completed".
The "TransferWordFields" script transfers values from text boxes, form fields, and control elements in Microsoft Word files to ELO metadata fields that have the same name.
The "TransmittalLetter" script enables users to create an e-mail with a transmittal letter containing information about the documents being sent.
With the "FillWithLastSord" script, the F3 function (use recent metadata) from ELO Java Client 21 can be used in older ELO Java Client versions.
The Indexserver script "RF_existsWorkflow" provides an optimized database for determining the workflows of an entry. The minimum requirement is the ELO Java Client version 10.17, 11.11, 12.06, 20.02, or from ELO 21.
The script provides an interface that allows the Integration Client to send a "Go to" command in the Java Client. See configuration parameter "useJcHAIGoto" in the Integration Client documentation.
Show instructions