Navigation:  3.45 > 3.45.7

Enhancement: New PM Control properties – 'Old value' and 'Is changed' - in Template

Two properties were added to Controls sheet:

Old Value – in column V – initial (stored) value of a control when displayed in detail/bottom panel
Is Changed – flag if current value is different than old (original/stored) value. It is result of this Excel function: = NOT(EXACT(currentvalue,oldvalue).

Enhancement: New PM Control variables – CONTROLNAME_VALUE, CONTROLNAME_OLDVALUE, CONTROLNAME_ISCHANGED – in Template

Three PM variables/Excel names were added for each control:

CONTROLNAME_VALUE – current control value, can be used in any formula instead of e.g. =$D$5$, this variable has value from column D (‘Value Read’ column) of corresponding row
CONTROLNAME_OLDVALUE - initial (stored) value of a control when displayed in detail/bottom panel, can be used in any formula instead of e.g. =$V$5$, this variable has value from new column V (‘Old value’ column) of corresponding row
CONTROLNAME_ISCHANGED - flag if current value is different than old (original/stored) value, can be used in any formula instead of e.g. =$W$5$, this variable has value from new column W (‘Is changed’ column) of corresponding row

These variables are not by default in your Template, but can be used as they are dynamically added by PM (to ensure correct names and references for controls). If you want to have them available in your Template during designing/testing your PM application in Excel, you can run Tools\Repair Template command in ‘PM Administration’ tool to add all these variables to your Template.

Note: it could happen that after some changes in Controls (adding/removing controls), the variables might not match due to changes, however they will be automatically replaced by correct variables in PM so you could see some differences in behaviour in your Template and in PM. You can resolve it if needed by running ‘Repair Template’ again to recreate the variables based on control changes in your Template.

Bug fix: Template having a Control with name which was sub name of another controls not validated succesfully

In case some control had name which was sub name of another control, the cell in projects/filters view was not associated properly and validation ‘error’ reported, e.g. having 2 controls TEXTBOX_OFFRE and TEXTBOX_OFFRE_A was not allowed, e.g. TEXTBOX_OFFRE had to be renamed e.g. to TEXTBOX_OFFRE2.
Note: it is possible that a control which worked so far, will fail validation after this change and its name in Controls sheet or its target cell will have to be corrected, e.g. TEXTBOX_OFFRE vs TEXTBOX_OFF.

Change: Connection settings dialog UI changes - removed not used slave/secondary server

The secondary server was always disabled as it is not supported in fact so it was removed.