MENU
A startup company is about have its Initial Public Offering (IPO) on the New York Stock Exchange.
This startup company has used Qlik Sense for many years for data-based decision making for Sales and Marketing efforts, as well as for input into Financial Reporting. The startup's Qlik Sense applications use variables that have different values at different points in time.
Due to the increased rigor required in record keeping for public companies, these variables must be clearly recorded in the script reload logs of the Qlik Sense applications. These logs are refreshed daily.
The data architect wants to have the variables names, with their current values, written into the script reload logs. Which script statement should the data architect use?
In the scenario where the startup company is preparing for an IPO, there is an increased need for meticulous record-keeping, including the recording of variable values used in Qlik Sense applications. The TRACE statement is the most suitable option for logging variable values during script execution.
TRACE: This statement writes custom messages, including variable values, to the script execution log. By using TRACE, you can ensure that every reload log contains the names and current values of all relevant variables, providing the necessary transparency and traceability.
For example, the script could include:
TRACE $(VariableName);
This command will output the variable's value in the script log, ensuring it is recorded for audit purposes.