You've got nothing to loose if you bring the label when you cut and paste form controls. It would be no harder to type over the original label that it is to type over the dummy label. On the other hand, it can be very useful to keep the label, especially if you are copying lots of fields from one form (or version of one form) to another form (or copy of the same form). It would also be useful if the copied controls are going to have labels very similar to the original labels.

Hi

If you want to copy/past controls, you will lose translations. It will be realy great, if after paste translation for new controll will be saved. It's realy hard job to create multi language app without this feature.

Regards

Greg

It would nice to verify the version of BPM (or any other product) based on values in the database.  I know the version exists on the application server in the registry keys, but there should be a way to confirm versions on both ends.

For example, we are currently using BPM 7.6 SR3, but we do not have access to the move the database schemas from one environment to another (government contractor).  As we move out of our DEV environment onto QA or TEST, we have to configure and install BPM, but the database piece is out of our hands.  Therefore, with all the scripts that need to be run per SR, it would be nice to determine that the versions match with a simple query.