What libraries do you have in the Build Path? The DSL classes are not in AgileAPI.jar or pxapi.jar. You will have to dig them out of the agileclasses.jar.

This the attribute change controlled–property of the field? If it is then it can only be modified if the item is on a change order and you modify it via the redline table.

If you are using a load balancer proxy you session can timeout without you getting a message. The result is a screen like you described. Clicking the refresh button send you to a login screen if that is the case.

Try the “Export” selection from the Tools menu

Update Title Block is a dangerous trigger. You can get into an infinite loop: an update triggers the px, that updates a field which triggers the PX…. etcetera. You can check the list of dirty attributes to see if any are fields you are interested in. That usually keeps an infinite loop from happening. Also, there is a Preference setting (trigger levels) that will keep an infinite loop from occurring.

Even if you get to the point where you no longer create an infinite loop, that kind of trigger is still dangerous. All it takes is a mass update from an Import to trigger the PX a massive number of times. Its a mess. I have since tried to stay away from Title Block Update triggers.

Not really. The pdx export would be your closest shot. It is basically a zip–you can rename the extension to .zip. But as you have discovered, the attachment filenames in the zip are coded. The .xml file in the zip has the mapping but you would want to create a script to parse the xml and rename the files. Other options to bulk download also would involve some form of coding.

Export into a pdx will grab the attachments as well. The resulting file is basically a zip; you can rename the extension to .zip.

Export is the closest you will get without custom coding.

There are two ways to see admin history, including who changed it. There is an overall admin history accessed from the icon button, second from left, next to the event trigger enable button. The other is a History tab on the class window. It will have just the changes that were made to that class.

Yes. On both the item. item.isFlagSet(ItemContants.FLAG_HAS_BOM);