Centralize application data in a Procedure

From this version onwards, the information related to the application that is located in the Reports (ExportReportTemplate_Style1, ExportReportTemplate_Style2, ExportReportTemplate_Style3) used for the ExportReports, in the Report Templates, and in Master Page is centralized in a transaction named 'WWPParameter', and using the Procedure named ''WWP_GetSystemParameter' the information is obtained. This transaction is loaded initially by a Data Provider, but you could make changes to the data or add new parameters at runtime (or modify the Data Provider). This Parameter transaction will also contain information about other parameters of the application, like information for AI intent-based navigation if you have enabled it, etc.

In the Reports and Report templates, some block codes were added in order to assign the values of the variables.

 

GeneXus source editor for ExportReportTemplate_Style1 highlights in a red box the code block AssignAppInfo, which assigns &CompanyName, &Phone, &Mail, &Website, and address lines using WWP_GetSystemParameter calls with keys like AD_Application_Name and AD_Application_Phone; below it Header and Footer subroutines print printTitle and printFooter with Page and Date info.

 

GeneXus source editor for the WWP_GetSystemParameter procedure shows a For Each WWPParameter loop with a Where clause matching WWPParameterKey = &WWPParameterKey, and assigns &WWPParameterValue = WWPParameterValue inside the loop before EndFor.

 

GeneXus KB Explorer tree on the left shows the WorkWithPlus module expanded to Parameters > WWPParameter (highlighted in a red box) with children Associated Tables, WorkWithPlusWWPParameter, and WWPParameter_DataProvider; the right pane shows the open WWPParameter_DataProvider source defining a WWPParameterCollection with entries for keys like AD_Application_Name, AD_Application_Title, and AD_Application_Phone, each with Category, Description, Value, and DisableDelete properties.