Database Reference
In-Depth Information
1. Locate, upload, and run the script
ch9_data_security_script.sql
. Re-
fer to
Chapter 4
if you need step-by-step instructions. You should see
three rows in the results report, all of which complete successfully.
2. Once the script completes, run the application and navigate to the
Analysis page. You should notice that only tickets or ticket details that
are assigned to the user you're logged in as appear.
Next, make changes to the source of several other pages so they reference the new
secure objects you just created:
3. Edit
Page 200
of the application.
4. Edit the
Tickets
report by double-clicking it.
5. Locate and open the file
ch9_report_p200.txt
, and copy its
contents into
Region Source
, replacing everything that is there. Click
Apply Changes
.
6. Run
Page 200
, and notice that you can only see the tickets that are
assigned to the current user.
You need to make a similar change on the Manage Multiple Tickets page:
7. Edit
Page 230
of the application.
8. Edit the
Manage Multiple Tickets
report by double-clicking it.
9. Locate and open the file
ch9_report_p230.txt
, and copy its
contents into
Region Source
, replacing everything that is there. Click
Apply Changes
.
10. Run
Page 230
, and notice that you can only see the tickets that are
assigned to the current user.
Next, modify the Calendar report:
11. Edit
Page 400
of the application.
12. Right-click
Ticket Activity Calendar
, and click
Edit Calendar
.
13. In the
Tasks
region on the right side of the page, click
Convert
to SQL Based Calendar
.
Figure 9-35
shows the location of the link.
Clicking the link generates a confirmation message and remains on the
same page.