LiveDocx 2.1 Beta released on free servers

by Björn Meyer 24. July 2012 10:42

Several weeks after the official release on the Premium servers, we are proud to announce the availability of LiveDocx 2.1 for all free accounts. As always, the free accounts are limited to 250 documents per day and some features are not available such as PDF/A export and the Adobe PDF document settings.

Feel free to use LiveDocx 2.1 by pointing to the new WSDL:

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

What is new in LiveDocx 2.1?

LiveDocx 2.1 is based on TX Text Control X8 - the latest version of our very own backend software to create and modify documents. The following template features are now supported in LiveDocx 2.1

  • Background images
  • Transparent text frames
  • Image merging
  • Colored page borders
  • Merged table cells
  • Overlapping objects (images, text frames)
  • Improved DOC and DOCX compatibility

You are welcome to provide your feedback about this new version in our support forum:

http://forums.textcontrol.com/forumdisplay.php?23-LiveDocx-Support

Happy coding!

Currently rated 1.5 by 125 people

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

Tags:

LiveDocx 2.1 released on Premium servers

by Björn Meyer 18. July 2012 09:34

During the last two weeks, Premium users were able to successfully test the final LiveDocx 2.1 version in a closed beta program. We are happy to announce that LiveDocx 2.1 is now available for all Premium users. New subscribers are getting a 2.1 account automatically. All LiveDocx 2.0 features including image merging are now available on Premium servers as well.

What is new in LiveDocx 2.1?

LiveDocx 2.1 is based on TX Text Control X8 - the latest version of our very own backend software to create and modify documents. The following template features are now supported in LiveDocx 2.1:

  • Colored page borders
  • Merged table cells 
  • Colored table lines
  • Background images
  • Transparent text frames
  • Overlapping objects (images, text frames)
  • EMF image support

Additionally, LiveDocx 2.1 can load more templates that were refused by older versions of LiveDocx.

If you are still using the free service and waited for LiveDocx 2.1, benefit from our 2 months for free campaign and order your Premium account today.

Currently rated 3.0 by 8 people

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

Tags:

LiveDocx 2.0 beta is up

by Lucas Mbiwe 17. September 2010 16:47

Hi all,

As announced earlier, we have set up a beta of LiveDocx 2.0. The URL, of course, is:

https://api.livedocx.com/2.0/mailmerge.asmx

If you are accessing LiveDocx using PHP, you probably need the link to the WSDL:

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

The new feature in this beta version is image merging. What this means is that you can have merge fields in your template replaced with image files during the merge process. Please read the following section for a detailed description.

Image merging

Prior to merging, make sure you have uploaded the image(s) you want to merge to the LiveDocx  server. The following, new methods allow for image handling. They work just like their counterparts for template handling.  Please note that GetImageExportFormats() replaces GetImageFormats():

public void DeleteImage(string filename) 
public string DownloadImage(string filename)
public string[] GetImageExportFormats() 
public string[] GetImageImportFormats()
public bool ImageExists(string filename)
public string[][] ListImages() 
public void UploadImage(string image, string filename)

Image merging works with standard merge fields. The only thing special about them is their name. It must start with the prefix image: followed by an arbitrary identifier. Here's an example to demonstrate this:

{ MERGEFIELD  image:ImageID  \* MERGEFORMAT }

In the merge data, finally, you use this identifier to assign the image's filename to the field:

string[][] mergeData = new string[][] {
    new string[] { "image:ImageID" },
    new string[] { "mypicture.png" } }; 

Like usually, the actual merging is done by calling CreateDocument(). No suprises here.

If you assign an empty string or the name of a file that is not on the server, the merge field is removed from the template and nothing is merged. This comes in handy, e.g., when the template you are using contains image fields for merging company logos and you want to produce a document that will be printed on pre-printed stationery.

Updates via Twitter

Since the beta is under development, it is bound to change frequently. In case we have some short-term updates, we will inform you via Twitter. The ID to follow is @livedocx, and for tweets concerning the 2.0 beta we will use the hashtag #v2beta. Of course, you can use this to send us your feedback as well. So, please feel free to play around with the beta and let us know what you think.

Currently rated 5.0 by 4 people

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

Tags:

Paying tribute to the "beta" in our logo

by Lucas Mbiwe 13. September 2010 15:01

Wow,

Our last blog post has generated quite some response. Thank you for all the positive feedback!

We will be attending quite a few trade shows in the next couple of months, so it is a bit tricky to come up with a realistic release schedule. Therefore, we have decided to pay tribute to the "beta" in our logo and do things a little different this time.

Instead of keeping you waiting till at least the second half of October, we will roll out the features as we finish them. This will give you the chance to play around with the new features immediately and let us know what you think. The website will remain the same, until we have finished implementing all of the new features. This means you will have to completely rely on the service API for things such as image handling. However, we think this is a small price to pay.

Next stop: image fields

We are using LiveDocx ourselves in our company to generate quotes, invoices and such. Thanks to image fields, we can now use the same templates to generate documents without logos that are printed on pre-printed stationery and documents including all logos that serve as email attachments. Because of some special requirements this was not possible using sub-templates.

In the next couple of days we will release a beta of the new LiveDocx version including image merging. Of course, we'll provide you with the necessary documentation to get you started.

Currently rated 3.0 by 2 people

  • Currently 3/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 3.0 by 6 people

  • Currently 3/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 1.7 by 6 people

  • Currently 1.666667/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 3.0 by 10 people

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

Tags:

Calendar

<<  June 2013  >>
MoTuWeThFrSaSu
272829303112
3456789
10111213141516
17181920212223
24252627282930
1234567

View posts in large calendar

RecentPosts