| |
| eReview API Toolkit |
| |
eReview as a view and collaborative application uses applets at client’s browser to view documents and manage collaboration using server side servlet components placed in a web application server. Having both servlet and applet Application Programming Interfaces (APIs), exposed from both ends, achieves multilevel integration throughout the eReview application task processing. Each sample provided below is a
working link. |
| |
| Servlet-based APIS |
| |
| I. Integration using server-side document path |
| |
 |
View Only |
|
eReview can be used as a View-Only tool to just view files from a server-side, document repository. This means, that in a web-based interface, when a user clicks on a link to view files, the files are loaded in eReview applet and the user can view these files. The markup buttons are not shown. This is useful while integrating eReview with a document/content management system, where various kinds of users have various type of rights. The users with just View-Only rights can be presented with this mode of eReview.
View-only sample |
| |
 |
Redacted View |
eReview has the provision to redact sensitive portions of confidential documents. this means, a document can be launched with confidential portions pre-redacted for certain users who are not authorized to view those particular portions of the document.
Original view without Redaction
Redacted View
|
| |
 |
View and Markup |
eReview can be used as a View and markup tool to view and markup files from a server-side document repository. This means, that in a web-based interface, when a user clicks on a link to view and markup files, the files are loaded in eReview applet and the user can view and markup these files. The markups can also be saved in a server-side repository, using the "save markup" function within the applet.
View and Markup sample |
| |
 |
Start and Join Meeting |
eReview can be used as a document-centric collaboration system. This means, the users can start/join online, real-time, document review meetings, to collaborate on the content in any format supported by eReview. The user who starts these meetings is the "Chairperson" (CP) and the users attending these meetings are the "Attendees"
Start Meeting sample
Join Meeting sample
Note: The meeting can also be started with pre-defined documents or with multiple documents pre-loaded. |
| |
 |
Playback Meeting |
The previously saved meetings can be replayed back at any time. Only the path to the saved file is required to be passed through this API.
Playback sample |
| |
| II. Integration using Customized Business Rules: |
|
eReview can be integrated with external JSP pages. eReview session integrated via ereviewintegrate.jsp. All integration related business logic can be placed in an external jsp page.
External JSP-based integration sample
|
| |
 |
| |
| Applet based APIs: |
| |
| I. Embedding eReview Applet in another applet |
eReview applet can be embedded within another applet instance and the applet can pass the parameters to eReview applet using these APIs.
Embedding eReview Applet in another Applet sample
|
| |
| II. Embedding eReview Applet in a webpage |
|
| |
| III. Invoking applet APIs with JavaScript |
|
| |
 |
| |
| APIs and XML: |
| |
eReview view-markup and
meeting sessions can be set up with the help of XML. Documents can be anywhere and XML files can be used to define the user roles .Viewing/Meeting sessions can be defined within XML files. This makes the application extremely portable and user-friendly.
View and Markup sample
Synchronous Meetings sample
Asynchronous meetings sample
Note: The above samples are only a few of the entire set of APIs. For details on eReview APIs refer to the eReview API Toolkit documentation released by Web4.
|
| |
| |