Announcing new mail merge features

by Lucas Mbiwe 29. August 2010 22:50

Hi all,

 A few months have passed since we almost released LiveDocx 1.3. But while it has been quiet here, we were busy working on new features in the meantime. Now it is time to prepare our next release, and this is a sneak preview of what to expect of it.

Image fields

Many of you have asked about this, and we think we have found an easy and clean way of doing it. The next LiveDocx release will enable you to merge images into fields. No need for a new or special field type required. This new feature works with plain, old merge fields.

Nested blocks

A fairly advanced feature not everybody has a need for. But those of you who do miss it badly. Hence, you will be pleased to hear that the next LiveDocx release will enable you to merge nested blocks.

Formatted input

Last but not least, the next LiveDocx release will enable you to merge formatted text (HTML) into your templates. This opens up new possibilities in application design. You could, e.g., provide your users with a simple rich text editor or let them merge hyperlinks, which will work in the resulting PDF documents, of course.

Currently rated 5.0 by 4 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

LiveDocx 1.0 and 1.1 will be discontinued on May 26, 2010

by Lucas Mbiwe 20. May 2010 16:36

Dear LiveDocx users,

We would like to inform you that as of May 26, 2010, LiveDocx 1.0 and 1.1 will no longer be available.

If you are still running any scripts or applications based on one of those versions of LiveDocx, please update them to use LiveDocx 1.2 before that date.

LiveDocx 1.2 will continue to run as before.

Thank you for using LiveDocx!

Currently rated 5.0 by 2 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

LiveDocx 1.2 updated – no need for LiveDocx 1.3

by Lucas Mbiwe 20. May 2010 16:01

Great news, everyone!

While preparing LiveDocx 1.3, which we were developing solely as a maintenance release, the compatibility tests revealed that is was possible to run it as an update to LiveDocx 1.2 without any side effects for existing applications. Therefore, we chose to update LiveDocx 1.2 instead of having all of our users have to update their applications to a new version.

Enjoy LiveDocx!

Currently rated 4.0 by 4 people

  • Currently 4/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

Change of plans

by Lucas Mbiwe 23. April 2010 17:13

LiveDocx 1.2 has been around for quite a while now. We think it's time for a new version. In fact, this thought is not new. Months ago, we thought about implementing and releasing LiveDocx 1.3 that should bring some small improvements. We have even given some hints in several forum posts and in some support emails indicating that the 1.3 release was imminent.

As you can all see, we have decided differently. This post is intended to give you some long overdue insight regarding our planning.

First things first

There has been a nasty bug in our server backend, which kept us quite busy for some weeks. The bug's existence became more and more apparent with the growing number of users accessing our services. We had to straighten out our priorities; making the current service more robust trumped releasing new features. Thus, we've put development on ice and went bug hunting.

Finally, we've been able not only to track it down, which alone was hard enough, but also to fix it. We have still some final testing to do to make absolutely sure the bug is gone, but it won't be too long before we apply the fix to our servers. We will inform you separately of the upcoming maintenance, of course.

Roadmap

As indicated in the introduction, this post means to give you an idea of what we are up to. Currently, we are working on two releases.

LiveDocx 1.3

The long promised version. This version is based on the above mentioned fix. Its sole purpose is to replace all previous versions of LiveDocx, 1.0, 1.1 and 1.2, all of which include the bug that has made our lives so hard for the past couple of weeks. LiveDocx 1.3 is completely backward compatible, so apart from swapping the old service URL with the new one, you shouldn't have to do anything to make it work with your existing code.

Obviously, the above means that shortly after releasing LiveDocx 1.3, we will discontinue the older releases. To make sure every user gets a chance to make the transition to the new version, we will send an email to every user and also wait an appropriate amount of time before we shut down the other versions.

LiveDocx 2.0

The long awaited features. Many users give us feedback regarding our service. Some of it is good, some of it not so much. We appreciate this. Feedback shows us what we have done right and also where there is room for improvement.

Regarding improvement, two features that users have constantly been asking for are nested merge blocks and formatted merge data. LiveDocx 2.0 will support these features. As the version number indicates, the interface will change—probably a lot. The new API is not finalized yet, we still have to figure some things out regarding cross-platform compatibility. For one, it's not always easy to use the built-in serialization of .NET data types, while at the same time remain, e.g., PHP friendly. Also, we are trying various authentication methods to reduce the number of API calls.

I am pretty sure we'll come up with a solution that will keep everybody happy. Of course we'll keep you posted.

Enjoy LiveDocx.

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

Patch Monday: LiveDocx Server Update Policy

by Björn Meyer 6. January 2010 16:24

Finding a good day and time for installing patches or updates on a server is always tricky. After analyzing our service statistics, we figured out that patching on Monday morning at 5AM (Central European Time) creates the least impact.

Up until now, we patched our servers manually after extensive testing, but we decided to automate this process. As such, you may find degradation in performance or a potential interruption of service on Mondays at the announced time.

Currently rated 2.3 by 3 people

  • Currently 2.333333/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

LiveDocx free service performance

by Björn Meyer 22. December 2009 17:31

We have been seeing some slowdowns in our document creation recently. And there were some requests in the last couple days where the free LiveDocx service was affected to the point of extreme slowness or temporary inaccessibility.

We apologize for any inconvenience and will work to avoid future issues.

We are very happy that LiveDocx is getting more and more popular, but as always, there is the famous other side of the coin. The more people are using this service the more server load we are experiencing. We already improved several parts of LiveDocx to avoid such a slowdown and we are very sure that we are prepared for the next wave.

It is our goal to offer you a stable and usable, free web service and we will improve this as best as we can.

To gain more information about the situations in which LiveDocx is getting slower, we would like to encourage you to send us your stack traces or any other information you can provide when you are not able to use the LiveDocx service.

Just send everything directly to: support@textcontrol.com

Thank you very much and happy holidays!

Currently rated 4.8 by 6 people

  • Currently 4.833333/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

Creating templates using OpenOffice.org

by Lucas Mbiwe 18. September 2009 19:10

A lot of people have asked us, if it is possible to use OpenOffice.org (OOo) to create templates that are compatible with LiveDocx. It actually is possible to do that. But because of OOo's approach to mail merge it is not as straightforward as in MS Word. OOo's mail merge philosophy needs a little getting used to. This post will help you understand this philosophy and get you started on creating templates with OOo.

Database-based mail merge

Mail merge in OpenOffice.org (OOo)—and this includes creating templates—cannot be done without first setting up a database. That database determines which mail merge fields can be contained in a template.

Luckily, we can use OOo Calc to setup the database, which makes the process almost effortless. The following image shows how to setup up a sample database using OOo Calc:  


Determining the mail merge fields for a template is as easy as setting their names as column headers. For the above sample this means, there will be the fields recipientsender available later on. Additional fields would go into the cells C1, D1 and so on. The best format to save this file is the default format, i.e. OpenDocument Spreadsheet (.ods).

Putting the database to work

Now that the "database" is in place, we can move to the actual template creation. For this step we need OOo Writer, of course, but please note that OOo Base also has to be installed, even though we won't use it directly.

To create our template we can use all of the "normal" text processing stuff. For inserting mail merge fields, however, we need to access the menu Insert → Fields → Other… or simply press Ctrl+F2 instead. In the dialog that opens we choose the Database tab. Then, we click on Browse…, navigate to the spreadsheet file we have created earlier, select it and click Open. OOo now creates a database based on the spreadsheet in the background.

Now, we select the type Mail merge fields on the left. Our database then shows up in the list as depicted below:

 

The database name is the same as the filename we have given the spreadsheet. The database tables correspond to the sheets in the spreadsheet file. Then again, the columns, read: fields, correspond to the cell contents we have inserted earlier.

We can now insert mail merge fields into our document. Of course, the fields are inserted at the current input position. So, we will be opening and closing the Fields dialog a lot.

Template specifics

There are a few things to bear in mind, when using OpenOffice.org (OOo) to  create templates:

  1. Templates must be saved as RTF 
  2. Field naming is rather special in OOo

The first one is simple. If we do not save our templates in RTF format, they will not work. It is that simple.

The second one is a bit more tricky. By choosing View → Field Names from the menu or by simply clicking Ctrl+F9 we can make the field names visible. This is quite convenient, since these will be the names we will have to use later on in our applications.


As we can see in the above image, the naming scheme is quite simple:

  • database.table.column

or from our spreadsheet perspective:

  • filename.sheet.column

There is just one big caveat. The dots in the field names are no full stop characters but ÿ characters which only look like dots in OOo. This means, we have to use the GetFieldNames() method, before we can use the fields. So, when using field names like LiveDocxÿletterÿrecipient in our code, we are able to put our templates, created in OOo, to work.

Currently rated 4.0 by 4 people

  • Currently 4/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

LiveDocx 1.2 released - Create images from documents

by Björn Meyer 10. August 2009 12:09

LiveDocx 1.2 releasedAbout 2 weeks ago, we already revealed the new amazing features of LiveDocx 1.2: 

What to expect of LiveDocx MailMerge API 1.2

We are glad to announce that LiveDocx 1.2 has just been released. The new features are:

  • Create images or thumbnails from document pages
  • Save documents as HTML
  • Create multiple documents in one run
  • Reduced file sizes
  • List of all available fonts

The new API 1.2 can be used right away with your already uploaded templates. You simply need to replace your service reference. The new WSDL can be found here:

https://api.livedocx.com/1.2/mailmerge.asmx?WSDL

The updated documentation is also available:

http://www.livedocx.com/pub/documentation/api.aspx

We would be glad to get your feedback on these new features. Feel free to post your comments and enjoy LiveDocx 1.2!

Currently rated 5.0 by 3 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

LiveDocx Premium Services Survey

by Björn Meyer 5. August 2009 16:46

LiveDocx is getting popular very fast. We are receiving more and more requests regarding a paid premium service for LiveDocx.

We thought that it is the best way to ask you – our users – what you expect from such a premium service. Therefore, we created a quick survey which doesn't take you more than 2 minutes to complete. We would be glad, if you can help us to find the best way to provide you with the best possible service plan.

Please find the survey below:

 

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

New Twitter feed: LiveDocx health status

by Björn Meyer 3. August 2009 10:51

We just set up a LiveDocx health checker on our servers that tweets the results directly to a new dedicated Twitter account. The health monitor checks the availability of the Web service definition (WSDL), the functionality of the database and the time it takes to login in order to send appropriate messages to the Twitter account.

The more users, the more traffic, the slower the connection. Generally, the performance is very good and stable, but when a lot of users are creating loads of documents at the same time, your experience might not be ideal.

Feel free to follow us on Twitter:

http://twitter.com/livedocx

Twitter

Currently rated 5.0 by 2 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

Calendar

<<  September 2010  >>
MoTuWeThFrSaSu
303112345
6789101112
13141516171819
20212223242526
27282930123
45678910

View posts in large calendar