I wasn’t sure I could actually blog about this update due to licensing issues but hey, they just did on the LiveCyle Blog. I guess it’s all in the wording.

In particular, this 8.2.1 SP2 update resolves a nasty bug where your form would grow to multiple megabytes in size due to a processing instruction (PI) being repeated thousands of times for a particular field. The PI looks like this (though the value, ‘aped3’, may differ):

<?templateDesigner StyleID aped3?>

Thankfully, this bug doesn’t occur often but when it does, the most common symptoms are:

1. reduced performance when working in Designer;
2. form file bloat (into the multiple MBs); and
3. crashes when working in Designer with the form open.

If you can’t update Designer due to your licensing agreement and you come across this bug, you’ll need to go to the XML Source and look for a processing instruction like the one quoted above. It’ll be there many, many times. Just delete all occurrences. If your form is saved as an XDP, then you can exit Designer and open it in Notepad (or some other text editor) and delete it that way as well. Then re-open it in Designer.

Updated: March 28, 2009

---

Posted by Stefan Cameron on March 17th, 2009
Filed under Bugs,Designer,LiveCycle

---

Have you ever wondered which LiveCycle components you would need to build your solution? There is a vast array of tools at your disposition within LiveCycle so how do you figure-out which ones you’ll need? Furthermore, they’re not all included in the package — some are part of LiveCycle Foundation while others are purchased “a la carte”. To make sure you purchase/install only what you’ll need, check-out this post on Avoka’s LiveCycle Blog. It’s a very useful list to have.

---

Posted by Stefan Cameron on March 4th, 2009
Filed under LiveCycle

---