What is new on BDF Version 14.1

• Api_component.setEditable and Api_component.setVisible methods are modified(New parameter "in_primaryKey_tx" is added). This parameter specifies one row in dataset, it will be used to change editable/visible property of component in Grid.
• Min/Max values of Domains are added to validation operataions to validate number values.
• Api_recordlist.set/getRecordListColumnLabel and Api_recordlist.set/getRecordListColumnWidth methods are added.
• "backgroundColorColumn" attribute is added to specify background color of component which is in grid.

What is new on BDF Version 15

• Api_accordionPanel.getExpandedAccordion/getCollapsedAccordion methods are added.
• Api_application.export method is added (Export by specified object types)
• Api_component.setTransparent/isTransparent/getMaxFileSize/setMaxFileSize/getURL/getNumberMask/getGridColumnLabel/getGridColumnWidth/isGridColumnVisible methods are added
• Api_datasource.refreshCurrentRow/getRowId methods are added
• Attribute of api_dialog.print in_value_tx is renamed to in_printJob_tx
• Attribute of api_frame.print in_value_tx is renamed to in_printJob_tx
• Api_panel.print method is added.
• New attribute in_order_nr is added to api_xmleditor.addError
• Api_xmleditor.isMultiTab/addEditorInstance/setEditorInstanceTitle/setEditorInstanceValue/setEditorInstanceValue/removeEditorInstance/getEditorInstanceTitle/
  getEditorInstanceValueCL/getEditorInstanceValueTX/getCurrentOrder/removeAllEditorInstances/setCurrentEditorInstance/getClosedEditorInstance/isEditorInstanceDirty/
  setEditorInstanceDirty/getDismissedEditorInstance methods are added.
• Api_exception package is added
  • The api_exception.getLastException method: From now on, when error occurs specific exception will be raised. Developers can catch up the exception and
    can have knowledge about error by using this specified method. This method returns the listed information below with record.
    • message_tx
    • methodName_tx
    • exceptionCode_tx
    • errorBackTrace_tx
  • If exception is not handled by developer, BRIM-UI Engine is going to handle exception and show the error message at rigt upper corner as usual.
  • The behaviour of some api_datasource methods are changed. The list is below:
    • Api_datasource.getColumnValueTX/NR/DT/CL/BLByPK : Will return exception when specifed situation happens : duplicate PK, invalid PK, null PK
    • Api_datasource.setColumnValueByPK : Will return exception when specifed situation happens : duplicate PK
    • Api_datasource.deleteRowByID : Will return exception when specifed situation happens : invalid record ID, null record ID
    • Api_datasource.deleteRowByPK : Will return exception when specifed situation happens : duplicate PK, invalid PK
    • Api_datasource.setCurrentRowByPK : Will return exception when specifed situation happens : duplicate PK, invalid PK
  • Please check your code for probable exceptions.
    • For instance, api_datasource.setCurrentRowByPK was commonly used to check if there was a record with the desired primary key value.
      In such a case, you should replace your code
      • from
      • "if api_datasource.setCurrentRowByPK(...) is not null then"
      • to
      • "begin
        • ...
      • exception
        • when api_datasource.e_invalidpk then
          • ...
      • end;"