This page (revision-10) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by rforbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
10 26-Nov-2021 10:22 4 KB kparrott to previous
9 26-Nov-2021 10:22 4 KB jaiken to previous | to last
8 26-Nov-2021 10:22 3 KB jaiken to previous | to last
7 26-Nov-2021 10:22 3 KB jaiken to previous | to last
6 26-Nov-2021 10:22 3 KB rforbes to previous | to last
5 26-Nov-2021 10:22 3 KB rforbes to previous | to last
4 26-Nov-2021 10:22 3 KB rforbes to previous | to last
3 26-Nov-2021 10:22 439 bytes rforbes to previous | to last
2 26-Nov-2021 10:22 399 bytes rforbes to previous | to last
1 26-Nov-2021 10:22 366 bytes rforbes to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 33 changed one line
The views provided with the application handle the decryption of data, so if you are creating reports using external tools with these views, there is nothing more to be done. If you are accessing the fields above directly, then you will need to modify your reports to handle the decryption of the data. A database function, [P2K_PMSEC.CHECKANDDECRYPT] (and for date columns P2K_PMSEC.CHECKANDDECRYPTDATE) is provided to help your external reports with the decryption of the data.
The views provided with the application handle the decryption of data, so if you are creating reports using external tools with these views, there is nothing more to be done. If you are accessing the fields above directly, then you will need to modify your reports to handle the decryption of the data. A database function, [P2K_PMSEC.CHECKANDDECRYPT] (and for date columns [P2K_PMSEC.CHECKANDDECRYPTDATE|P2K_PMSEC.CHECKANDDECRYPT]) is provided to help your external reports with the decryption of the data.