Enterprise Reporting & Business Insights Platform |
Intellicus now sorts out the problem of ambiguous columns or aliases during filter operations. Now a designer have an option to define a qualified name for the column which will be used while applying a filter using 'where' clause in a query. Intellicus Automatically generates (suggest) the possible Qualified Field name which designer can change if needed.
Intellicus has introduced this feature to help you to now use multiple query
objects as parameters within a single query object. This feature enables a
designer to reuse the existing query objects hence helps you
in saving your considerable amount
of time and effort.
As shown in figure we are using an existing Query object named as 'country' while creating a new Query object.
Designer can now re-use the java scripts created by them. If the designer have some common JavaScript methods which they plan to reuse in other queries than this version will allow them to do so. Designer need to keep the entire Java script code (Methods) in a file with extension '.js' and then upload that file into Intellicus as shown in the below figure.
The code in the .js file can look something like this.
function TestParam(value)
{
if (value=="abc")
{
if
(params("ParamTest") != null)
{
return "where JOB in (<%ParamTest%>)";
}
else
{
return "where JOB not in (<%ParamTest%>)";
}
}
else
{
return "where
JOB in (<%ParamTest%>)";
}
}
Now after uploading the '.js' file if designer wants to use that script in the query object than he/she need to write a code similar to the one shown below to use the methods.
select empno,empname from Employee
<@%
#include TestParam.js;
%@>
<@%
return TestParam("abc");
%@>