A populator populates field values based on the user currently running the report. For example, if an organization owner with succession planning responsibilities for Org A, Org B, and Org C runs a report with a succession planning org populator, he or she will only see Orgs A, B, and C in the Organization drop-down list. If another organization owner with succession planning responsibilities to Organizations 1, 2, and 3 runs the report, that user will see organizations 1, 2, and 3.
Populators work in either end-user or administrator reports, but they are intended to be used for supervisors and organization owners in the end-user environment.
Read general information about end user report security.
Plateau.rptlibrary contains parameters that match to Talent Management populators. All populator parameters are in the populator parameter group.
Open the Plateau.rptlibrary in the Resource Explorer.
Find the Populators parameter group, and in it, find the populator you want to use. See the Populator Parameter List to understand individual Populator parameters.
Drag the parameter into the Report Parameters of your report.
Modify the SQL query in the data set to use the populator parameter. You call the parameter using the bracket syntax, as you call any Talent Management parameter. For more information about bracket syntax, see Plateau Report Designer SQL Syntax.
Always test your changes. To test populator changes, you must import the report to Talent Management. Because you cannot unpublish user-side reports, import to a test or staging Talent Management environment to test. Trouble with populators often appears as an empty list. For example, if you include an organization populator in a report for a user who has access to no organizations, then the list will appear empty.
The following is a list of the populators available in the Populator parameter group in the Plateau.rptlibrary file.
| Parameter Name | Usage |
|---|---|
| GapThreshold | Populates the Gap Threshold list, which is the gap that must exist between the previous review's supervisor rating and the current review's supervisor rating before the employee shows up on the report. See the Employee Dropoff report for an example. |
| PotentialRatingMinimum/PotentialRatingMaximum | Populates the Potential Ratings lists (minimum and maximum). The rating scale for potential rating is set in Talent Management Administration: System Admin > Configuration > Performance Management. See the Employee Dropoff Report for an example. |
| StrengthSelector | Populates the Maximum Number of Strengths list. A strength is a competency in which the user has a gap between current rating and required rating and the user's peers have rated the user higher than the user himself or herself. See the Close Fit Jobs report for an example. |
| JobsSelector | Populates the Maximum Number of Jobs list. It is the maximum number of close fit jobs that a report returns. For an example, see the Close Fit Jobs report. |
| CompleteStatusID | Populates the Completion Status list. Completion Status is managed in Talent Management Administrator: Learning > References > Completion Status. For an example, see the Item Status report. |
| CascadeSteps | Populates the Maximum Number of Cascade Steps list. Cascade steps are the levels of subordinates removed from a supervisor for goal alignment. For an example see the My Alignment report. |
| SubordinatesOrg | Used for supervisors' reports, the OwnedSuccessionOrgs parameter returns the organizations that subordinates belong to. For example if a supervisor has three subordinates, each of whom belongs to a different organization (OrgA, OrgB, and OrgC), that supervisor's Organization drop-down list is populated with OrgA, OrgB, and OrgC. For an example, see the Performance Review Comparison report. |
| OwnedSuccessionOrgs | Used for Organization owners. Returns the list of organizations to which the user has succession planning privileges, as defined on the user's record. For an example, see the User Succession Plan. |