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

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
6 26-Nov-2021 10:22 2 KB jmyers to previous
5 26-Nov-2021 10:22 2 KB jmyers to previous | to last
4 26-Nov-2021 10:22 2 KB jmyers to previous | to last
3 26-Nov-2021 10:22 1 KB JMyers to previous | to last
2 26-Nov-2021 10:22 1 KB RForbes to previous | to last
1 26-Nov-2021 10:22 755 bytes RForbes to last

Page References

Incoming links Outgoing links
DISCOVERER
DISCOVERER

Version management

Difference between version and

At line 7 changed one line
Discoverer can be hooked in to work with the [{$applicationname}] software. For information on how Discoverer works, or to arrange training, please contact your sales representative.
Discoverer can be hooked in to work with the Personality software. For information on how Discoverer works, or to arrange training, please contact your sales representative.
At line 9 changed one line
Discoverer can be used to report from tables or views within the P2K schema, which is the structure that [{$applicationname}] uses. Discoverer users are also data base users, and should be set up on [IMUS] with appropriate roles granted to them.
Discoverer can be used to report from tables or views within the P2K schema, which is the structure that Personality uses. Discoverer users are also data base users, and should be set up on [IMUS] with appropriate roles granted to them.
At line 11 added 7 lines
!!Notes on Security
#Discoverer only respects data security not object security. (E.g. The role has access to only specific departments ([IMRO]/[IMFOS] – Data Security/Form Object security) and has no access to the wage rates ([IMOS]-Object security). The user/viewer will only be able to see the specific departments within the report but will not be restricted from the wage rate.)
#P2K_PEDPR secures the user to only areas they are allowed to access. This is set up by the Discoverer Admin role and uses the i.d. of the table that is being passed in and the alias of the table being passed to.
#Security is no longer based on the Views (e.g. [P2K_HR_Vassignments]). That was true prior to the implementation of P2K_PEDPR.
#The report must be built specific to the user. (e.g. If the user should not be able to view the wage rate in the report then don’t include it.)
#It is currently not possible to create sets of reports in separate views. (e.g. You cannot create a payroll section with only payroll reports or a benefit section with only benefit reports, etc.)
At line 13 changed 4 lines
[{InsertPage page='Internal.DISCOVERER' default='Click to create a new discussion page'}]
}]
[{InsertPage page='Internal.DISCOVERER' default='Click to create a new notes page'}]
This page (revision-6) was last changed on 26-Nov-2021 10:22 by jmyersTop