GroupDocs.Signature for Java 19.5 Supports Rounded Corners for Stamp Signature

Many people use stamps as part of their documents to mark them as approved or completed. For example, when a document is to be signed by the concerned person at a company, he puts his signature as well as stamps the document as a proof that the document is signed by the authorized person. In other words, the stamps are used to seal the document that is being exchanged among multiple persons/parties.

Various companies use digital signatures to sign their document using automated systems. This way, they can avoid the efforts of manually signing a bunch of documents as well as they don’t have to print the document for signatures and then scan the signed copy for distribution. If such companies have the requirement to sign as well as stamp their documents then how would they do it digitally? Well, here comes the GroupDocs.Signature that allows digital stamping of the documents.

Digital stamping is one of the salient features of the GroupDocs.Signature API. We provide a wide range of options to control the placement and appearance of the digital stamps in the document. The following is a snapshot of the document which we have stamped using our API.

In the above snapshot, you can observe that the borderlines are flat. However, some of you may want to have rounded corners for the stamp. So keeping that in mind, we have provided the support of stamps with the round corners in GroupDocs.Signature for Java 19.5. For this, we have added a new public class SquareBorderLine that inherits BorderLine to implement square stamp with rounded corners. This is how you can achieve it using the code.

The following would be the output of the above written code.

So if you want to implement this feature in your e-signing application, just download that latest release and integrate it into your application. In case you would have any query or question, do write to us on our forum.

Share on FacebookTweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Signature Product Family | Tagged , , , , , , , , , | Leave a comment

Enable Pagination in WordProcessing Module

Yes, this is right. Paginal mode is now implemented in GroupDocs.Editor for .NET 19.5. How this mode will effect WordProcessing documents? As you know that previously, there was only float mode. When WordProcessing documents were converted to the page-less HTML, page division was absent. But in this release WordProcessing options class contains new paged (also called paginal) mode. When paged is enabled, it produces HTML markup, optimized and adjusted for per-page edit and it creates ease to enable paged editing in any of WYSIWYG-editors.

By default this mode is disabled. In order to enable it you need to set a boolean flag to true in the WordProcessingToHtmlOptions options:

Now, when document is edited in the WYSIWYG-editor and is passed back to the GroupDocs.Editor API for converting from HTML to the output format, you also have to set boolean flag to true (by default it is disabled) in the WordProcessingSaveOptions:

Aside this, various text effects are implemented in WordProcessing documents:

  • Shadow
  • 3D Effect
  • Outline
  • Glow
  • Engrave
  • Emboss

This feature doesn’t require any action, it is always enabled and can be observed, when the document with such text effects is processed.

Metered Credits is introduced in this release as well. As API already supports Metered Licensing. But now a new credits concept is implemented. Each document operation, along with consumed bytes, also consumes one credit. The amount of already used credits can be retrieved through new static method GetConsumptionCredit in the Metered class:

Grab the latest release here. Please communicate with us on forum if you face any issue.

Share on FacebookTweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Editor Product Family | Tagged | Leave a comment

Get Credit Consumption Information for Your Metered Licence

Hello everyone! I am back with another release announcement of GroupDocs.Redaction for .NET 19.5. This release has brought a quite useful feature for the developers who are using GroupDocs.Redaction with our Metered Licence. For those who are unaware of the Metered Licence, let me give you a brief introduction. Afterward, I will talk about the new feature and its usage.

Metered License is a type of license that allows you to pay for what you have used. You are charged only when you use any feature of the GroupDocs APIs in your application. It is useful if you want to be billed based on the usage of the API features. Your usage is reported to our servers and based on which we generate your monthly invoices.

The Metered License is supported for both .NET and Java APIs that we offer. Some major advantages that you can enjoy using Metered License are:

  • You pay only for what you have used.
  • Same monthly charges are applied regardless of the number of developers you engage to use our APIs.
  • Metered License is not specific for one product and you can use any product under this license type.
  • You can create applications providing the APIs for other developers to use.

Now you would have got a clear picture of the Metered License. So let’s move forward and check out what new we have for those who are already using the said type of the license.

In the latest release, we have added the feature of getting the credit consumption information against your Metered License. Which means that now you can be aware of how much credit you have consumed. Once you have got this information, you can use it for the further usage analysis.

To get the credits consumption information, we have added GetConsumptionCredit method to GroupDocs.Redaction.Metered class. This is how you can use this method.

Alright! So now you must have got the idea of how the latest release might be helpful for you. You can download the latest release and evaluate the features of the API using the examples project. For more details, please consult the API’s documentation.

In case you would have any questions or queries, do let us know via our forum.

Share on FacebookTweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Redaction Product Family | Tagged , , , , , , | Leave a comment

Generate Search Results from Filtered Documents

Sometimes, we have a lot of different formatted documents. We create index then perform search and API shows hits from all the indexed documents. Ever thought to get search results from desired documents only?

Let’s dig it further. Suppose, you have multiple TXT, XLSX and DOCX documents. What if you want to search a word or text only in TXT and DOCX files with specific word occurrence in file names? We’ve now improved ISearchDocumentFilter interface for such a purpose in GroupDocs.Search. This interface represents search document filter and it uses SearchDocumentFilter class for creation of a filter instances.

Let’s now understand this with a use-case.
C#

Java

What we did in this example? We initiated a request to search occurrence of a word hobbit in all the TXT and DOCX files with word task in their file names. In this snippet, you can see a method CreateConjuction. It creates logical conjunction (logical and) of the specified filters.

Settings for Log Functionality

This improvement allows to set up log file name and maximum log file size. Below are the public API changes.
Following class has been added to GroupDocs.Search namespace and com.groupdocs.search package:

  • LogSettings
Following properties are added to GroupDocs.Search.LogSettings and com.groupdocs.search.LogSettings class: C#
  • string FileName
  • double MaxSize
Java
  • String getFileName()
  • void setFileName(String value)
  • double getMaxSize()
  • void setMaxSize(double value)
Below properties are added to GroupDocs.Search.Index and com.groupdocs.search.Index classes respectively:
  • LogSettings LogSettings
  • LogSettings getLogSettings()


Let’s go through the implementation:
C#


Java

Add English Synonyms

This improvement adds English synonyms to default synonym dictionary.
C#


Java

Above are the major improvements introduced in version 19.5. Please go through all the other changes in release notes:

Avail these exciting improvements now in your project. This release is available for download. Please share your feedback or concerns here.

Share on FacebookTweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Search Product Family | Tagged | Leave a comment

Save Assembled Word Processing, Presentation, Spreadsheet and Email Documents as HTML File with Resources

The HTML format is widely used for creating the webpages or, in other words, the HTML files. These days, every operating system, whether it be of desktop or mobile, contains the built-in web browser that supports viewing the HTML files. Other than that, many free web browsers are also available in the market. This means that any information or the content that is available in the form of HTML pages can easily be viewed just having installed a web browser.

Just imagine a scenario where you have some Word documents created in MS Word and you want to display them in your web application. So how would you view the content of the file? A suitable and easy solution is if you could get the HTML form of that Word document then it can be viewed within your application in the web browser.

Now, you could imagine the usefulness of the HTML format. So, let’s now find out how did we make use of HTML format in making GroupDocs.Assembly more powerful and useful for you.

Since version 19.5 of GroupDocs.Assembly, the assembled Word Processing documents, Spreadsheets, Presentations and Email files could be saved as HTML with resources. This means that the generated reports can now be saved as HTML files along with the resources such as images and, as I have mentioned before, you would be able to embed and view the content of the generated reports within your web application.

Let’s take the example of generating the report from the Word template and see how we can save the report as an HTML file. For saving the generated report as HTML with resources, we have added a new property ResourceSaveFolder to the LoadSaveOptions class to specify the folder that will be used to store the resource files. If no folder is specified, by default, external resource files will be stored to a folder having the same name as that of the HTML file (without extension) plus the “_files” suffix. The following code snippets demonstrate this feature:

C#


Java


Along with this feature, we have also added the facility of loading HTML template documents referencing external resource files to be assembled and saved to non-HTML formats. For this, the containing folder of the template file is used as a base URI to resolve external resource files’ relative URIs to absolute ones by default, as shown in the following code snippet:

C#


Java


Well, this would definitely be a really attracting release for you guys. So let’s not wait and download the latest version to check how these features can make your report generation applications more powerful.

For any questions or suggestions, have a conversation with us on our forum.

Share on FacebookTweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Assembly Product Family | Tagged , , , , , , , | Leave a comment

Cache Page Previews in GroupDocs.Annotation for Java

EnableCaching feature stores image representation of a document in a directory at the local drive. In case of repetitive processing/opening of a document, it uses cached data. This thing helps to avoid the processing of the same document again and again. You might be waiting for this feature. The wait is over now. API permits you to enable cache mode and cache page previews. Let’s take a overview of its code.

We also added possibility to display distance annotation caption for following file formats:

  • Slides
  • Cells
  • Diagrams

Following older formats for Slides, Cells and Words are now supported:

  • .ppt
  • .xls
  • .doc

Along with new features, this release also covers some improvements and bug fixes. As an improvement we refactored PdfToPngSaver and AnnotationHandler classes.

Moreover, we added additional parameters to ImageOptions for more flexible retrieval of pages.

  • Parameter for getting pages without annotation
  • Retrieve the range of pages
  • Retrieve only specific count of pages

Given below are some of the major bug fixes.

  • Line width not set in Slides
  • Issue when opening protected with password documents
  • Exception occurred while remove annotations from .xls file

Download our open-source example project here and explore API documentation here.

Share on FacebookTweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Annotation Product Family | Tagged | Leave a comment

Implement Conversion to WMF Format

WMF is a Windows MetaFile that can contain both vector and bitmap image information. We added support of WMF file format along-with few others in GroupDocs.Conversion for .NET 19.5. You can now convert any supported file format to WMF. Along-with WMF, convert supported documents to EMF.

Convert to EMF

Convert to WMF

Moreover, you can now pay royalties for the use of the API. Yes, metered licensing is now enabled.

New file formats you can convert from:

  • DIB
  • XLT
  • POT

In this release, we also removed obsolete property JpegQuality from ImageSaveOptions.

We’d recommend you to download latest version of the API and share your feedback.

Share on FacebookTweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Conversion Product Family | Tagged | Leave a comment