reports:how_to
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| reports:how_to [2024/10/07 15:23] – antonio.andriychuk | reports:how_to [2024/10/08 09:01] (current) – Added Images and minor changes antonio.andriychuk | ||
|---|---|---|---|
| Line 215: | Line 215: | ||
| * __queue_time or pending_time__: | * __queue_time or pending_time__: | ||
| * __talk_time__: | * __talk_time__: | ||
| + | |||
| + | |||
| + | {{: | ||
| After developing the query, we can move to Jasper to continue with building the front-end of the report. \\ \\ | After developing the query, we can move to Jasper to continue with building the front-end of the report. \\ \\ | ||
| Line 230: | Line 233: | ||
| {{: | {{: | ||
| - | Be aware that sometimes, you have to partially alterate some fields functionalities, | + | Be aware that sometimes, you have to partially alterate some fields functionalities, |
| + | Also, it may happen that once you finish with the report and launch it in the admin page you will not see some fields. To fix this you have to select the column, go to " | ||
| + | |||
| + | |||
| + | ===== Developing the report: Front-end ===== | ||
| + | After creating the back-end (with queries and construction of fields and parameters) it's time to develop the front-end, so the web-page that an user will see once launching the report. \\ | ||
| + | In this topic, we're going to: | ||
| + | * Change the hyperlink from " | ||
| + | * Streamline the query to run a 'lil faster; | ||
| + | * Creating parameters fields and link them to the query; | ||
| + | |||
| + | {{: | ||
| + | |||
| + | \\ \\ | ||
| + | ==== Change the Hyperlink ==== | ||
| + | To change the Hyperlink, you must first select the Brightpattern in the "Main report" | ||
| + | \\ Then, procceed with changing the value of the field from " | ||
| + | |||
| + | {{: | ||
| + | |||
| + | \\ \\ | ||
| + | ==== Streamline the query ==== | ||
| + | This step is more easier than expected, this step is also important to make the report able to only take the tenant dataset and not every tenant. In order to apply this explaination in query terms, open the DataSet of the first page and change the FROM call_detail (as an example, change the table to the interested one or where you've been requested to develope a look-alike report) to FROM (tenant dataset).call_detail . | ||
| + | \\ As an example, if I have to make a report on the beincontact.it tenant you must insert: "FROM test_com.call_detail"; | ||
| + | Another worth mention is that, in order to create a more streamline and fast query, if it is requested to only extract the query on a single service, add this service on the WHERE condition. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | \\ \\ | ||
| + | ==== Parameters and Link ==== | ||
| + | In order to create a better-streamlined-work I suggest to copy the created parameter from the " | ||
| + | \\ As per the provided example, we're going to select " | ||
| + | |||
| + | {{: | ||
| + | |||
| + | Next, another thing worth to do in order to require an input from the User is to navigate on the " | ||
| + | |||
| + | {{: | ||
| + | |||
| + | \\ \\ | ||
| + | ====== Conclusions ====== | ||
| + | Once done this small report as an example, save it and upload the report on the " | ||
| + | \\ As you could' | ||
reports/how_to.1728314627.txt.gz · Last modified: by antonio.andriychuk
