326 lines
28 KiB
Plaintext
326 lines
28 KiB
Plaintext
<%@ Control Language="C#" Inherits="BaseContentUserControls" %>
|
||
<%@ Register Namespace="TeamLab.Controls" Assembly="__Code" TagPrefix="cc" %>
|
||
|
||
<script runat="server">
|
||
protected override void Init()
|
||
{
|
||
PageTitle = PageCaption = "Connectors FAQ";
|
||
MetaDescription = "ONLYOFFICE is a multifuntional portal for business collaboration and project management. Find answers to the frequently asked questions about ONLYOFFICE.";
|
||
MetaKeyWords = "";
|
||
}
|
||
</script>
|
||
|
||
|
||
<div class="MainHelpCenter FAQ">
|
||
<h1>Connectors</h1>
|
||
<%-- <div class="keyword_block">
|
||
<ul>
|
||
<li><cc:LocalizeContent runat="Server" ControlName="~/Controls/Help/Tags/file-formats/file-formats.ascx" /></li>
|
||
<li><cc:LocalizeContent runat="Server" ControlName="~/Controls/Help/Tags/html5-canvas/html5-canvas.ascx" /></li>
|
||
<li><cc:LocalizeContent runat="Server" ControlName="~/Controls/Help/Tags/onlyoffice-online-editor-features/onlyoffice-online-editor-features.ascx" /></li>
|
||
</ul>
|
||
</div>--%>
|
||
<h2>Nextcloud</h2>
|
||
<p class="fq_expand"><span>Expand all</span></p>
|
||
<p class="fq_collapse"><span>Collapse all</span></p>
|
||
<dl class="faq_block" id="nextcloud_1">
|
||
<dt>Can I edit one document from different Nextcloud servers?</dt>
|
||
<dd>
|
||
<p>If the document is shared using the <b>Federated Cloud Sharing</b> app, the co-editing among the servers will not be avaialble. The users from one and the same server can edit the document in the co-editing mode, but the users from two (or more) different servers will not be able to collaborate on the same document in real time.</p>
|
||
</dd>
|
||
</dl>
|
||
<dl class="faq_block" id="nextcloud_2">
|
||
<dt>I’m having issues with documents editing when using external storages.</dt>
|
||
<dd>
|
||
<p>Adding the storage using the <b>External storages</b> app has issues with the co-editing in some cases. If the connection is made using the same authorization keys (the <em>Username and password</em> or <em>Global credentials</em> authentication type is selected), then the co-editing is available for the users.<br />
|
||
If different authorization keys are used (<em>Log-in credentials</em>, <em>save in database</em> or <em>User entered</em>, <em>store in database</em> authentication options), the co-editing is not available. When the <em>Log-in credentials</em>, <em>save in session</em> authentication type is used, the files cannot be opened in the editor.</p>
|
||
</dd>
|
||
</dl>
|
||
<dl class="faq_block" id="nextcloud_3">
|
||
<dt>Will my Document Server be able to connect to Nextcloud if I’m using self-signed certificate?</dt>
|
||
<dd>
|
||
<p>If you are using a self-signed certificate for your <b>Document Server</b>, Nextcloud will not validate such a certificate and will not allow connection to/from <b>Document Server</b>. This issue can be solved the following way: locate the Nextcloud config file (<em>/nextcloud/config/config.php</em>) and open it.</p>
|
||
<p>Insert the following section to it:</p>
|
||
<pre><code>'onlyoffice' => array
|
||
('verify_peer_off' => true
|
||
)</code></pre>
|
||
<p>This will disable the certificate verification and allow Nextcloud to establish connection with <b>Document Server</b>, but you must remember that this is a temporary insecure solution and we strongly recommend that you replace the certificate with the one issued by some CA. Once you do that, do not forget to remove the above section from Nextcloud config file.</p>
|
||
</dd>
|
||
</dl>
|
||
<dl class="faq_block" id="nextcloud_4">
|
||
<dt>How it works?</dt>
|
||
<dd>
|
||
<ul class="howitworks">
|
||
<li>When creating a new file, the user navigates to a document folder within Nextcloud and clicks the <b>Document</b>, <b>Spreadsheet</b> or <b>Presentation</b> item in the <em>new</em> (+) menu.</li>
|
||
<li>The browser invokes the create method in the <em>/lib/Controller/EditorController.php</em> controller. This method adds the copy of the file from the assets folder to the folder the user is currently in.</li>
|
||
<li>Or, when opening an existing file, the user navigates to it within Nextcloud and selects the <b>Open in ONLYOFFICE</b> menu option.</li>
|
||
<li>A new browser tab is opened and the index method of the <em>/lib/Controller/EditorController.php</em> controller is invoked.</li>
|
||
<li>The app prepares a JSON object with the following properties:
|
||
<ul class="howitworks">
|
||
<li><b>url</b> - the URL that ONLYOFFICE Document Server uses to download the document;</li>
|
||
<li><b>callbackUrl</b> - the URL that ONLYOFFICE Document Server informs about status of the document editing;</li>
|
||
<li><b>key</b> - the UUID+Modified Timestamp to instruct ONLYOFFICE Document Server whether to download the document again or not;</li>
|
||
<li><b>title</b> - the document Title (name);</li>
|
||
<li><b>id</b> - the identification of the user;</li>
|
||
<li><b>name</b> - the name of the user.</li>
|
||
</ul>
|
||
</li>
|
||
<li>Nextcloud takes this object and constructs a page from <em>templates/editor.php</em> template, filling in all of those values so that the client browser can load up the editor.</li>
|
||
<li>The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the DocEditor configuration with the above properties.</li>
|
||
<li>Then ONLYOFFICE Document Server downloads the document from Nextcloud and the user begins editing.</li>
|
||
<li>ONLYOFFICE Document Server sends a POST request to the callback URL to inform Nextcloud that a user is editing the document.</li>
|
||
<li>When all users and client browsers are done with editing, they close the editing window.</li>
|
||
<li>After <a target="_blank" href="https://api.onlyoffice.com/editors/save#savedelay">10 seconds</a> of inactivity, ONLYOFFICE Document Server sends a POST to the callback URL letting Nextcloud know that the clients have finished editing the document and closed it.</li>
|
||
<li>Nextcloud downloads the new version of the document, replacing the old one.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
<dl class="faq_block" id="nextcloud_5">
|
||
<dt>What is Nextcloud Hub, how does it work and are there any differences with conventional Nextcloud server?</dt>
|
||
<dd>
|
||
<p>
|
||
Nextcloud Hub is a new solution from the Nextcloud team with the built-in MS Office compatibility which is provided with the help of ONLYOFFICE editors.<br />
|
||
Specifically created ONLYOFFICE Document Server this solution is called Community Document Server. Community Document Server uses the client-side code of our Document Server, but the server-side code was partially rewritten by the Nextcloud team using PHP to fit the whole platform.
|
||
</p>
|
||
<p>Here are some technical details:</p>
|
||
<ul>
|
||
<li>The new version was created to facilitate the installation and avoid using Docker. However, you still need it on the installation stage.</li>
|
||
<li>It supports <b>x86-64</b> Linux servers.</li>
|
||
<li>You still need our connector. Just get it from the App Store, everything else is pre-configured. Refer to this <a target="_blank" href="https://nextcloud.com/blog/how-to-install-onlyoffice-in-nextcloud-hub-and-new-integration-feature/">How-to</a> to install ONLYOFFICE in Nextcloud Hub.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
|
||
<h2>ownCloud</h2>
|
||
<p class="fq_expand"><span>Expand all</span></p>
|
||
<p class="fq_collapse"><span>Collapse all</span></p>
|
||
<dl class="faq_block" id="owncloud_1">
|
||
<dt>Can I edit one document from different ownCloud servers?</dt>
|
||
<dd>
|
||
<p>If the document is shared using the <b>Federated Cloud Sharing</b> app, the co-editing among the servers will not be avaialble. The users from one and the same server can edit the document in the co-editing mode, but the users from two (or more) different servers will not be able to collaborate on the same document in real time.</p>
|
||
</dd>
|
||
</dl>
|
||
<dl class="faq_block" id="owncloud_2">
|
||
<dt>I’m having issues with documents editing when using external storages.</dt>
|
||
<dd>
|
||
<p>
|
||
Adding the storage using the <b>External storages</b> app has issues with the co-editing in some cases. If the connection is made using the same authorization keys (the <em>Username and password</em> or <em>Global credentials</em> authentication type is selected), then the co-editing is available for the users.<br />
|
||
If different authorization keys are used (<em>Log-in credentials</em>, <em>save in database</em> or <em>User entered</em>, <em>store in database</em> authentication options), the co-editing is not available. When the <em>Log-in credentials</em>, <em>save in session</em> authentication type is used, the files cannot be opened in the editor.
|
||
</p>
|
||
</dd>
|
||
</dl>
|
||
<dl class="faq_block" id="owncloud_3">
|
||
<dt>Will my Document Server be able to connect to ownCloud if I’m using self-signed certificate?</dt>
|
||
<dd>
|
||
<p>If you are using a self-signed certificate for your <b>Document Server</b>, ownCloud will not validate such a certificate and will not allow connection to/from <b>Document Server</b>. This issue can be solved the following way: locate the ownCloud config file (<em>/ownCloud/config/config.php</em>) and open it.</p>
|
||
<p>Insert the following section to it:</p>
|
||
<pre><code>'onlyoffice' => array
|
||
('verify_peer_off' => true
|
||
)</code></pre>
|
||
<p>This will disable the certificate verification and allow ownCloud to establish connection with <b>Document Server</b>, but you must remember that this is a temporary insecure solution and we strongly recommend that you replace the certificate with the one issued by some CA. Once you do that, do not forget to remove the above section from ownCloud config file.</p>
|
||
</dd>
|
||
</dl>
|
||
<dl class="faq_block" id="owncloud_4">
|
||
<dt>How it works?</dt>
|
||
<dd>
|
||
<ul class="howitworks">
|
||
<li>When creating a new file, the user navigates to a document folder within ownCloud and clicks the <b>Document</b>, <b>Spreadsheet</b> or <b>Presentation</b> item in the <em>new</em> (+) menu.</li>
|
||
<li>The browser invokes the create method in the <em>/lib/Controller/EditorController.php</em> controller. This method adds the copy of the file from the assets folder to the folder the user is currently in.</li>
|
||
<li>Or, when opening an existing file, the user navigates to it within ownCloud and selects the <b>Open in ONLYOFFICE</b> menu option.</li>
|
||
<li>A new browser tab is opened and the index method of the <em>/lib/Controller/EditorController.php</em> controller is invoked.</li>
|
||
<li>The app prepares a JSON object with the following properties:
|
||
<ul class="howitworks">
|
||
<li><b>url</b> - the URL that ONLYOFFICE Document Server uses to download the document;</li>
|
||
<li><b>callbackUrl</b> - the URL that ONLYOFFICE Document Server informs about status of the document editing;</li>
|
||
<li><b>key</b> - the UUID+Modified Timestamp to instruct ONLYOFFICE Document Server whether to download the document again or not;</li>
|
||
<li><b>title</b> - the document Title (name);</li>
|
||
<li><b>id</b> - the identification of the user;</li>
|
||
<li><b>name</b> - the name of the user.</li>
|
||
</ul>
|
||
</li>
|
||
<li>OwnCloud takes this object and constructs a page from <em>templates/editor.php</em> template, filling in all of those values so that the client browser can load up the editor.</li>
|
||
<li>The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the DocEditor configuration with the above properties.</li>
|
||
<li>Then ONLYOFFICE Document Server downloads the document from ownCloud and the user begins editing.</li>
|
||
<li>ONLYOFFICE Document Server sends a POST request to the callback URL to inform ownCloud that a user is editing the document.</li>
|
||
<li>When all users and client browsers are done with editing, they close the editing window.</li>
|
||
<li>After <a target="_blank" href="https://api.onlyoffice.com/editors/save#savedelay">10 seconds</a> of inactivity, ONLYOFFICE Document Server sends a POST to the callback URL letting Nextcloud know that the clients have finished editing the document and closed it.</li>
|
||
<li>OwnCloud downloads the new version of the document, replacing the old one.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
|
||
<h2>Plone</h2>
|
||
<p class="fq_expand"><span>Expand all</span></p>
|
||
<p class="fq_collapse"><span>Collapse all</span></p>
|
||
<dl class="faq_block" id="plone_1">
|
||
<dt>How it works?</dt>
|
||
<dd>
|
||
<ul class="howitworks">
|
||
<li>User navigates to a document within Plone and selects the <b>ONLYOFFICE Edit</b> action.</li>
|
||
<li>Plone end prepares a JSON object for the Document Server with the following properties:
|
||
<ul class="howitworks">
|
||
<li><b>url</b> - the URL that ONLYOFFICE Document Server uses to download the document;</li>
|
||
<li><b>callbackUrl</b> - the URL that ONLYOFFICE Document Server informs about status of the document editing;</li>
|
||
<li><b>key</b> - the UUID+Modified Timestamp to instruct ONLYOFFICE Document Server whether to download the document again or not;</li>
|
||
<li><b>title</b> - the document Title (name).</li>
|
||
</ul>
|
||
</li>
|
||
<li>Plone constructs a page from a <code>.pt</code> template, filling in all of those values so that the client browser can load up the editor.</li>
|
||
<li>The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the docEditor configuration with the above properties.</li>
|
||
<li>Then ONLYOFFICE Document Server downloads the document from Plone and the user begins editing.</li>
|
||
<li>ONLYOFFICE Document Server sends a POST request to the <code>callback</code> URL to inform Plone that a user is editing the document.</li>
|
||
<li>When all users and client browsers are done with editing, they close the editing window</li>
|
||
<li>After <a target="_blank" href="https://api.onlyoffice.com/editors/save#savedelay">10 seconds</a> of inactivity, ONLYOFFICE Document Server sends a POST to the <code>callback</code> URL letting Alfresco know that the clients have finished editing the document and closed it.</li>
|
||
<li>Plone downloads the new version of the document, replacing the old one.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
|
||
<h2>Alfresco</h2>
|
||
<p class="fq_expand"><span>Expand all</span></p>
|
||
<p class="fq_collapse"><span>Collapse all</span></p>
|
||
<dl class="faq_block" id="alfresco_1">
|
||
<dt>How it works?</dt>
|
||
<dd>
|
||
<ul class="howitworks">
|
||
<li>User navigates to a document within Alfresco Share and selects the <b>Edit in ONLYOFFICE</b> menu option.</li>
|
||
<li>Alfresco Share makes a request to the repo end (URL of the form: <em>/parashift/onlyoffice/prepare?nodeRef={nodeRef}</em>).</li>
|
||
<li>Alfresco Repo end prepares a JSON object for the Share with the following properties:
|
||
<ul class="howitworks">
|
||
<li><b>url</b> - the URL that ONLYOFFICE Document Server uses to download the document (includes the <em>alf_ticket</em> of the current user);</li>
|
||
<li><b>callbackUrl</b> - the URL that ONLYOFFICE Document Server informs about status of the document editing;</li>
|
||
<li><b>onlyofficeUrl</b> - the URL that the client needs to respond to ONLYOFFICE Document Server (provided by the onlyoffice.url property);</li>
|
||
<li><b>key</b> - the UUID+Modified Timestamp to instruct ONLYOFFICE Document Server whether to download the document again or not;</li>
|
||
<li><b>title</b> - the document Title (name).</li>
|
||
</ul>
|
||
</li>
|
||
<li>Alfresco Share takes this object and constructs a page from a freemarker template, filling in all of those values so that the client browser can load up the editor.</li>
|
||
<li>The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the DocEditor configuration with the above properties.</li>
|
||
<li>Then ONLYOFFICE Document Server downloads the document from Alfresco and the user begins editing.</li>
|
||
<li>ONLYOFFICE Document Server sends a POST request to the callback URL to inform Alfresco that a user is editing the document.</li>
|
||
<li>Alfresco locks the document, but still allows other users with write access the ability to collaborate in real time with ONLYOFFICE Document Server by leaving the Action present.</li>
|
||
<li>When all users and client browsers are done with editing, they close the editing window.</li>
|
||
<li>After <a target="_blank" href="https://api.onlyoffice.com/editors/save#savedelay">10 seconds</a> of inactivity, ONLYOFFICE Document Server sends a POST to the callback URL letting Alfresco know that the clients have finished editing the document and closed it.</li>
|
||
<li>Alfresco downloads the new version of the document, replacing the old one.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
|
||
<h2>Confluence</h2>
|
||
<p class="fq_expand"><span>Expand all</span></p>
|
||
<p class="fq_collapse"><span>Collapse all</span></p>
|
||
<dl class="faq_block" id="confluence_1">
|
||
<dt>How it works?</dt>
|
||
<dd>
|
||
<ul class="howitworks">
|
||
<li>User navigates to a Confluence attachments and selects the <b>Edit in ONLYOFFICE</b> action.</li>
|
||
<li>Confluence makes a request to OnlyOfficeEditorServlet (URL of the form: <em>/plugins/servlet/onlyoffice/doceditor?attachmentId=$attachment.id</em>).</li>
|
||
<li>Confluence sends document to ONLYOFFICE Document storage service and receive a temporary link</li>
|
||
<li>Confluence prepares a JSON object with the following properties:
|
||
<ul class="howitworks">
|
||
<li><b>url</b> - the temporary link that ONLYOFFICE Document Server uses to download the document;</li>
|
||
<li><b>callbackUrl</b> - the URL that ONLYOFFICE Document Server informs about status of the document editing;</li>
|
||
<li><b>key</b> - the UUID to instruct ONLYOFFICE Document Server whether to download the document again or not;</li>
|
||
<li><b>title</b> - the document Title (name).</li>
|
||
</ul>
|
||
</li>
|
||
<li>Confluence takes this object and constructs a page from a freemarker template, filling in all of those values so that the client browser can load up the editor.</li>
|
||
<li>The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the DocEditor configuration with the above properties.</li>
|
||
<li>Then ONLYOFFICE Document Server downloads the document from Confluence and the user begins editing.</li>
|
||
<li>When all users and client browsers are done with editing, they close the editing window.</li>
|
||
<li>After <a target="_blank" href="https://api.onlyoffice.com/editors/save#savedelay">10 seconds</a> of inactivity, ONLYOFFICE Document Server sends a POST to the callback URL letting Confluence know that the clients have finished editing the document and closed it.</li>
|
||
<li>Confluence downloads the new version of the document, replacing the old one.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
|
||
<h2>HumHub</h2>
|
||
<p class="fq_expand"><span>Expand all</span></p>
|
||
<p class="fq_collapse"><span>Collapse all</span></p>
|
||
<dl class="faq_block" id="humhub_1">
|
||
<dt>How it works?</dt>
|
||
<dd>
|
||
<ul class="howitworks">
|
||
<li>When creating a new file, the user will be provided with Document, Spreadsheet or Presentation options in the <em>Create document</em> menu.</li>
|
||
<li>The browser invokes the index method in the <em>/controllers/CreateController.php</em> controller.</li>
|
||
<li>Or, when opening an existing file, the user will be provided with <em>View document</em> or <em>Edit document</em> depending on an extension.</li>
|
||
<li>A popup is opened and the index method of the <em>/controllers/OpenController.php</em> controller is invoked.</li>
|
||
<li>The app prepares a JSON object with the following properties:
|
||
<ul class="howitworks">
|
||
<li><b>url</b> - the URL that ONLYOFFICE Document Server uses to download the document;</li>
|
||
<li><b>callbackUrl</b> - the URL that ONLYOFFICE Document Server informs about status of the document editing;</li>
|
||
<li><b>key</b> - the random MD5 hash to instruct ONLYOFFICE Document Server whether to download the document again or not;</li>
|
||
<li><b>title</b> - the document Title (name);</li>
|
||
<li><b>id</b> - the identification of the user;</li>
|
||
<li><b>name</b> - the name of the user.</li>
|
||
</ul>
|
||
</li>
|
||
<li>HumHub takes this object and constructs a page from <em>views/open/index.php</em> template, filling in all of those values so that the client browser can load up the editor.</li>
|
||
<li>The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the DocEditor configuration with the above properties.</li>
|
||
<li>Then ONLYOFFICE Document Server downloads the document from HumHub and the user begins editing.</li>
|
||
<li>ONLYOFFICE Document Server sends a POST request to the <em>callbackUrl</em> to inform HumHub that a user is editing the document.</li>
|
||
<li>When all users and client browsers are done with editing, they close the editing window.</li>
|
||
<li>After <a target="_blank" href="https://api.onlyoffice.com/editors/save#savedelay">10 seconds</a> of inactivity, ONLYOFFICE Document Server sends a POST to the callback URL letting HumHub know that the clients have finished editing the document and closed it.</li>
|
||
<li>HumHub downloads the new version of the document, replacing the old one.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
|
||
<h2>SharePoint</h2>
|
||
<p class="fq_expand"><span>Expand all</span></p>
|
||
<p class="fq_collapse"><span>Collapse all</span></p>
|
||
<dl class="faq_block" id="sharepoint_1">
|
||
<dt>How it works?</dt>
|
||
<dd>
|
||
<ul class="howitworks">
|
||
<li>User navigates to a document within SharePoint and selects the <b>Edit in ONLYOFFICE</b> action on context menu or ribbon.</li>
|
||
<li>SharePoint ONLYOFFICE solution makes a request to the editor page (URL of the form: <em>/_layouts/15/Onlyoffice/editorPage.aspx?SPListItemId={SelectedItemId}&SPListId={SelectedListId}&SPSource={Source}&SPListURLDir={ListUrlDir}</em>).</li>
|
||
<li>SharePoint ONLYOFFICE solution prepares a JSON object with the following properties:
|
||
<ul class="howitworks">
|
||
<li><b>url</b> - the URL that ONLYOFFICE Document Server uses to download the document;</li>
|
||
<li><b>callback</b> - the URL that ONLYOFFICE Document Server informs about status of the document editing;</li>
|
||
<li><b>documentServerUr</b> - the URL that the client needs to reply to ONLYOFFICE Document Server (can be set at the settings page);</li>
|
||
<li><b>key</b> - the file identificator from SharePoint;</li>
|
||
<li><b>fileName</b> - the document Title (name);</li>
|
||
<li><b>userId</b> - the identification of the user;</li>
|
||
<li><b>userName </b> - the name of the user;</li>
|
||
</ul>
|
||
</li>
|
||
<li>SharePoint ONLYOFFICE solution constructs a page, filling in all of those values so that the client browser can load up the editor.</li>
|
||
<li>The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the DocEditor configuration with the above properties.</li>
|
||
<li>Then ONLYOFFICE Document Server downloads the document from SharePoint and the user begins editing.</li>
|
||
<li>When all users and client browsers are done with editing, they close the editing window.</li>
|
||
<li>After <a target="_blank" href="https://api.onlyoffice.com/editors/save#savedelay">10 seconds</a> of inactivity, ONLYOFFICE Document Server sends a POST to the callback URL letting SharePoint ONLYOFFICE solution know that the clients have finished editing the document and closed it.</li>
|
||
<li>SharePoint ONLYOFFICE solution downloads the new version of the document, replacing the old one.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
|
||
<h2>Liferay</h2>
|
||
<p class="fq_expand"><span>Expand all</span></p>
|
||
<p class="fq_collapse"><span>Collapse all</span></p>
|
||
<dl class="faq_block" id="liferay_1">
|
||
<dt>How it works?</dt>
|
||
<dd>
|
||
<ul class="howitworks">
|
||
<li>User navigates to a <b>Documents and Media</b> section within Liferay and selects the <code>Edit in ONLYOFFICE</code> action.</li>
|
||
<li>Liferay prepares a JSON object for the Document Server with the following properties:
|
||
<ul class="howitworks">
|
||
<li><b>url</b> - the URL that ONLYOFFICE Document Server uses to download the document;</li>
|
||
<li><b>callbackUrl</b> - the URL that ONLYOFFICE Document Server informs about status of the document editing;</li>
|
||
<li><b>key</b> - the fileVersionId to instruct ONLYOFFICE Document Server whether to download the document again or not;</li>
|
||
<li><b>title</b> - the document Title (name);</li>
|
||
</ul>
|
||
</li>
|
||
<li>The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the docEditor configuration with the above properties.</li>
|
||
<li>Then ONLYOFFICE Document Server downloads the document from Liferay and the user begins editing.</li>
|
||
<li>ONLYOFFICE Document Server sends a POST request to the <em>callbackUrl</em> to inform Liferay that a user is editing the document.</li>
|
||
<li>Liferay locks the document, but still allows other users with write access the ability to collaborate in real time with ONLYOFFICE Document Server by leaving the Action present.</li>
|
||
<li>When all users and client browsers are done with editing, they close the editing window.</li>
|
||
<li>After <a target="_blank" href="https://api.onlyoffice.com/editors/save#savedelay">10 seconds</a> of inactivity, ONLYOFFICE Document Server sends a POST to the callback URL letting Liferay know that the clients have finished editing the document and closed it.</li>
|
||
<li>Liferay downloads the new version of the document, replacing the old one.</li>
|
||
</ul>
|
||
</dd>
|
||
</dl>
|
||
|
||
</div> |