When you integrate ONLYOFFICE Document Builder into your own application, there are two ways this can be done:
In case your application is a C++ or .Net one, you can embed the code for ONLYOFFICE Document Builder together with the script code for the document files to be created into your application. In this case you will need to recompile your application each time anything is to be changed in the output document files. This option is good when you need a faster native application and you are sure that the resulting document files will always stay the same or will only be changed when you recompile your application anyway.
For the integration of ONLYOFFICE Document Builder into any application, the C++ or .Net doctrenderer library is used.
If you are going to use ONLYOFFICE Document Builder with an application written in any other programming language, the second option is recommended: to run ONLYOFFICE Document Builder executable from your application and use the .docbuilder script file for the document to be created as a parameter to it. It is much more flexible and allows to change the document script files (especially if there are more than one of them) independently of your application in future. You will only need to recompile your application if you need to add more document script files to it.
To launch ONLYOFFICE Document Builder using the second option run the following command:
docbuilder.exe mydocument.docbuilder
Visit the .docbuilder file section for more information about the file structure and rules used when creating it.
See the examples in some of the most popular programming languages at this page.
If you use ONLYOFFICE Document Builder as both an application and a script, then you need to know some rules and limitations:
To run ONLYOFFICE Document Builder executable in the C++ application, use the CDocBuilder.Run method in the following way:
CDocBuilder::Initialize(sWorkDirectory.c_str());
CDocBuilder oBuilder;
oBuilder.Run("path-to-script.docbuilder");
CDocBuilder::Dispose();
Another way to do this is to use the docbuilder.exe executable file and run it with the .docbuilder file as an argument, where all the code for the document file creation will be written:
docbuilder.exe "path-to-script.docbuilder"
To set an argument to the builder class which can be trasferred to the program outside the CDocBuilder.ExecuteCommand method, add it as an additional property when running ONLYOFFICE Document Builder executable file or as a part of program JavaScript code, but not included into the document file script:
docbuilder.exe "--argument={\"company\":\"ONLYOFFICE\",\"product\":\"ONLYOFFICE Document Builder\"}" "path-to-script.docbuilder"
var sCompany = Argument["company"]; var sProduct = Argument["product"];
The builder object methods cannot be called with the JS variables. Wrap them with the jsValue instruction if necessary:
var jsVar = "123.docx";
builder.SaveFile("docx", jsVar); // Incorrect
builder.SaveFile("docx", jsValue(jsVar)); // Correct
For convenience, format types are replaced with strings.
For example,
builder.CreateFile("docx");
is the same as
CDocBuilder.CreateFile(AVS_OFFICESTUDIO_FILE_DOCUMENT_DOCX);
And
builder.SaveFile("docx", file_path);
is the same as
CDocBuilder.SaveFile(AVS_OFFICESTUDIO_FILE_DOCUMENT_DOCX, file_path);
| String | Format type |
| "docx" | AVS_OFFICESTUDIO_FILE_DOCUMENT_DOCX |
| "doc" | AVS_OFFICESTUDIO_FILE_DOCUMENT_DOC |
| "odt" | AVS_OFFICESTUDIO_FILE_DOCUMENT_ODT |
| "rtf" | AVS_OFFICESTUDIO_FILE_DOCUMENT_RTF |
| "txt" | AVS_OFFICESTUDIO_FILE_DOCUMENT_TXT |
| "pptx" | AVS_OFFICESTUDIO_FILE_PRESENTATION_PPTX |
| "odp" | AVS_OFFICESTUDIO_FILE_PRESENTATION_ODP |
| "xlsx" | AVS_OFFICESTUDIO_FILE_SPREADSHEET_XLSX |
| "xls" | AVS_OFFICESTUDIO_FILE_SPREADSHEET_XLS |
| "ods" | AVS_OFFICESTUDIO_FILE_SPREADSHEET_ODS |
| "csv" | AVS_OFFICESTUDIO_FILE_SPREADSHEET_CSV |
| "pdf" | AVS_OFFICESTUDIO_FILE_CROSSPLATFORM_PDF |
| "image" | AVS_OFFICESTUDIO_FILE_IMAGE |
| "jpg" | AVS_OFFICESTUDIO_FILE_IMAGE |
| "png" | AVS_OFFICESTUDIO_FILE_IMAGE |
The entire JavaScript context is a wrapper for its native CDocBuilder builderJS object. You need to work with it as with an ordinary JavaScript object. In this case, the jsValue instruction is not needed for the JS variables:
builderJS.OpenFile("path_or_url", "x2t_additons_as_xml");
builderJS.CreateFile(AVS_OFFICESTUDIO_FILE_DOCUMENT_DOCX); or builderJS.CreateFile("docx");
builderJS.SetTmpFolder("folder");
builderJS.SaveFile(AVS_OFFICESTUDIO_FILE_DOCUMENT_DOCX, "path", "x2t_additons_as_xml"); or builderJS.SaveFile("docx", "path", "x2t_additons_as_xml");
builderJS.CloseFile();
The Document Builder always works with one file. But there are cases when you need to be able to open another file not for adding its data to the content, but for some kind of manipulation (document comparison, mailmerge, etc). For such cases, the Document Builder provides the OpenTmpFile method:
var tmpFile = builderJS.OpenTmpFile("path_or_url");
| Name | Description |
| IsValid | Specifies if the temporary file is valid (true). |
| GetBinary | Returns Uint8Array with the doct/pptt/xlst binary content. |
| GetFolder | Returns the string path to the temporary folder with the temporary file contents. |
| Close | Closes the file (removes the temporary folder contents). |
| GetImageMap | Returns a dictionary object with the imageId -> imagePath key-value pairs (for inserting into the document). |
To make the code shorter, use the following type definitions:
typedef CDocBuilderValue CValue; typedef CDocBuilderContext CContext; typedef CDocBuilderContextScope CContextScope;