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

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

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
87 26-Nov-2021 10:22 12 KB Karen Parrott to previous
86 26-Nov-2021 10:22 12 KB Lilia Urtan to previous | to last BECT and BECTM ==> BECTM
85 26-Nov-2021 10:22 12 KB Kevin Higgs to previous | to last
84 26-Nov-2021 10:22 13 KB Karen Parrott to previous | to last BDDB ==> BDDB and BDDBM
83 26-Nov-2021 10:22 13 KB Meg McFarland to previous | to last
82 26-Nov-2021 10:22 13 KB Karen Parrott to previous | to last BDDB and BDDBM ==> BDDB
81 26-Nov-2021 10:22 13 KB Meg McFarland to previous | to last

Page References

Incoming links Outgoing links
Business Intelligence Analytics Dashboard...nobody
Business Intelligence Analytics Dashboard

Version management

Difference between version and

At line 5 changed one line
The information contained in this document is subject to change without notice. All information in this document is based on the 5.03 release of Personality. High Line Corporation provides this material “AS IS” and makes no warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. High Line Corporation shall not be liable for errors contained in this document or for incidental or consequential damages (including lost profits in connection with the furnishing, performance or use of this material whether based on warranty, contract, or other legal theory). \\
The information contained in this document is subject to change without notice. All information in this document is based on the 5.03 release of Personality. High Line Corporation provides this material “AS IS” and makes no warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. High Line Corporation shall not be liable for errors contained in this document or for incidental or consequential damages (including lost profits in connection with the furnishing, performance or use of this material whether based on warranty, contract, or other legal theory). \\
At line 19 changed one line
High Line uses the word ‘Panel’ to describe any graph, table and/or report that is created by/within the Dashboard. A description of the available Panels is provided in later sections. \\
High Line uses the word ‘Panel’ to describe any graph, table and/or report that is created by/within the Dashboard. A description of the available Panels is provided in later sections. \\
At line 22 changed 2 lines
Static Dashboards are delivered as ‘home’ pages that cannot be edited by Users. They consist of 4 – 5 pre-defined Panels in a single page. The intent is to provide a simple ‘home’ page for various Users. A library of Static Dashboards (designed by Role) has been provided by High Line. \\
__Security:__ Users must be given security access for each of the panels included in the static dashboard, as well as to the related drill-into forms. For example, the “MyPayStub” Panel links to either pay stubs for printing or to disbursement information; the “Profile” Panel links to the Employment Profile and/or Leave Balances. If a drill-into form is available for the User, mouse-over and visual cues will indicate. \\
Static Dashboards are delivered as ‘home’ pages that cannot be edited by Users. They consist of 4 – 5 pre-defined Panels in a single page. The intent is to provide a simple ‘home’ page for various Users. A library of Static Dashboards (designed by Role) has been provided by High Line. \\
__Security:__ Users must be given security access for each of the panels included in the static dashboard, as well as to the related drill-into forms. For example, the “MyPayStub” Panel links to either pay stubs for printing or to disbursement information; the “Profile” Panel links to the Employment Profile and/or Leave Balances. If a drill-into form is available for the User, mouse-over and visual cues will indicate. \\
At line 26 changed 4 lines
__Security:__ Users must be given security access for any panels to be available, as well as to related drill-into forms. For example, the “DepartmentBudget” Panel drills to a report of Positions, and then to the Position (IDPS) form and/or the Posting (IRPO) form. If a drill-into form is available for the User, mouse-over and visual cues will indicate. The Dynamic Dashboard (BMDD) can also be turned on/off for Users/Roles based on function security.\\
Panels indicated as intended for Managers (see ‘audience’ in the Panels list) respect Manager Hierarchy (direct reports) as well as security defined on the IMSV (Assign Security Rights) form. \\
Panels indicated as intended for Administrators (see ‘audience’ in the panels list) respect security defined on the IMSV (Assign Security Rights) form. \\
Data Grids (BEDG – HR Data Grid)\\
__Security:__ Users must be given security access for any panels to be available, as well as to related drill-into forms. For example, the “DepartmentBudget” Panel drills to a report of Positions, and then to the Position (IDPS) form and/or the Posting (IRPO) form. If a drill-into form is available for the User, mouse-over and visual cues will indicate. The Dynamic Dashboard (BMDD) can also be turned on/off for Users/Roles based on function security.\\
Panels indicated as intended for Managers (see ‘audience’ in the Panels list) respect Manager Hierarchy (direct reports) as well as security defined on the IMSV (Assign Security Rights) form. \\
Panels indicated as intended for Administrators (see ‘audience’ in the panels list) respect security defined on the IMSV (Assign Security Rights) form. \\
Data Grids (BEDG – HR Data Grid)\\
At line 32 changed one line
!!!Static Dashboard (‘home’ pages)\\
!!!Static Dashboard (‘home’ pages)\\
At line 44 changed 2 lines
|Scheduler (SSS)|SSS_DASHBOARD|Profile, OT Warning, Incidents, Outstanding Approvals, Daily Work Schedule "Who’s Here"
* Note – names may change as additional boards are provided. Search Functions (IMFN, IMFDH) with the following: %Dashboard for updated names/options. \\
|Scheduler (SSS)|SSS_DASHBOARD|Profile, OT Warning, Incidents, Outstanding Approvals, Daily Work Schedule "Who’s Here"
* Note – names may change as additional boards are provided. Search Functions (IMFN, IMFDH) with the following: %Dashboard for updated names/options. \\
At line 47 changed 2 lines
The provided panels can be used for ''any role that a client has created – limited by the functionality within the dashboard (i.e. a Manager dashboard would not be appropriate for an Employee). \\ ''
__''Dashboards cannot be edited (other than the function’s Web Address field). __\\ ''
The provided panels can be used for ''any role that a client has created – limited by the functionality within the dashboard (i.e. a Manager dashboard would not be appropriate for an Employee). \\ ''
__''Dashboards cannot be edited (other than the function’s Web Address field). __\\ ''
At line 50 changed one line
!IMFN/IMFDH/IMEX – Security\\
!IMFN/IMFDH/IMEX – Security\\
At line 52 changed one line
!IMMU – Menus \\
!IMMU – Menus \\
At line 54 changed 8 lines
!IMUS – Users \\
Find the User’s Profile on IMUS, then drill to the Roles assigned to confirm the Menu used for the User Profile’s Role(s). User Profiles can have multiple Roles and therefore multiple menus; the highest Role sequence on the User Profile defines the default role. \\
For clients utilizing __Recruiting__: if an employee is linked to a Posting as a Recruiter, they will automatically be given the Recruiter Role (hidden), at sequence 999. Therefore, if you want the Recruiter role to show up as the employee’s default role (on access to Self Service), leave the other roles as sequence <999. If the preference is for Employee, Manager, or some other role be default, assign those Roles to the User Profile with a sequence >999. \\
!IMRO – Roles \\
The “Menus Assigned” tab is used to define the Menu to be used. For clients moving to NextGen from earlier versions, edits to existing menus will be required, to allow the Dashboards to be chosen and placed where preferred. \\
!IMSV – Security Rights\\
Users (i.e. Administrators and Managers) can be restricted to/from viewing Employee records via the Assign Security Rights form. Note that any panel listed as “Manager” will also have manager hierarchy automatically assigned. \\
!IMFN/IMFDH – Web Address (not commonly required)\\
!IMUS – Users \\
Find the User’s Profile on IMUS, then drill to the Roles assigned to confirm the Menu used for the User Profile’s Role(s). User Profiles can have multiple Roles and therefore multiple menus; the highest Role sequence on the User Profile defines the default role. \\
For clients utilizing __Recruiting__: if an employee is linked to a Posting as a Recruiter, they will automatically be given the Recruiter Role (hidden), at sequence 999. Therefore, if you want the Recruiter role to show up as the employee’s default role (on access to Self Service), leave the other roles as sequence <999. If the preference is for Employee, Manager, or some other role be default, assign those Roles to the User Profile with a sequence >999. \\
!IMRO – Roles \\
The “Menus Assigned” tab is used to define the Menu to be used. For clients moving to NextGen from earlier versions, edits to existing menus will be required, to allow the Dashboards to be chosen and placed where preferred. \\
!IMSV – Security Rights\\
Users (i.e. Administrators and Managers) can be restricted to/from viewing Employee records via the Assign Security Rights form. Note that any panel listed as “Manager” will also have manager hierarchy automatically assigned. \\
!IMFN/IMFDH – Web Address (not commonly required)\\
At line 63 changed one line
Web Address edits are rarely required – example provided:\\
Web Address edits are rarely required – example provided:\\
At line 68 changed one line
ESS Dashboard – no pictures, no twitter feed (ESS_DASHBOARD2 from section above)\\
ESS Dashboard – no pictures, no twitter feed (ESS_DASHBOARD2 from section above)\\
At line 73 changed one line
Each of the panels below is the ‘start’ form for one or more panels/reports; users drill into details/additional reports and potentially may drill into Personality forms. For the “Module Pre-requisite”, EMSS (Self Service) is required in all cases.
Each of the panels below is the ‘start’ form for one or more panels/reports; users drill into details/additional reports and potentially may drill into Personality forms. For the “Module Pre-requisite”, EMSS (Self Service) is required in all cases.
At line 81 changed 3 lines
|Daily Work Schedule (BTWS)|[Daily Work Schedule|][ (“Who’s Here”)|]|FD, TS|Admin, Scheduler
|Daily Leaves - Department (BADLM)|[Daily Leaves (“Who’s away”) – Department|] |FD, AT|Manager
|Daily Leaves - Admin (BADL)|[Daily Leaves (“Who’s away”) – All|] |FD, AT|Admin
|Daily Work Schedule (BTWS)|[Daily Work Schedule|][ (“Who’s Here”)|]|FD, TS|Admin, Scheduler
|Daily Leaves - Department (BADLM)|[Daily Leaves (“Who’s away”) – Department|] |FD, AT|Manager
|Daily Leaves - Admin (BADL)|[Daily Leaves (“Who’s away”) – All|] |FD, AT|Admin
At line 99 changed one line
|OutstandingWorkFlow (BWTD)|[Workflow to Complete|][ (was “Bottleneck Report”)|]|FD, WF|Admin
|OutstandingWorkFlow (BWTD)|[Workflow to Complete|][ (was “Bottleneck Report”)|]|FD, WF|Admin
At line 103 changed one line
|Profile-nopic (BEPN)|[Profile – no picture|] |FD|Employee
|Profile-nopic (BEPN)|[Profile – no picture|] |FD|Employee
At line 111 changed one line
|URL Embedding (BDUE)|[URL Embedding|][ – Sample|]|n/a|Manager, Employee
|URL Embedding (BDUE)|[URL Embedding|][ – Sample|]|n/a|Manager, Employee
At line 116 changed 2 lines
!!Absenteeism (BAAA / BAAAM) – Absenteeism Analysis\\
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
!!Absenteeism (BAAA / BAAAM) – Absenteeism Analysis\\
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
At line 119 changed one line
;Description: Bar chart – Leave hours taken by Department, Leave Type, Period of time. Allows drill to details.
;Description: Bar chart – Leave hours taken by Department, Leave Type, Period of time. Allows drill to details.
At line 125 changed 3 lines
;Description: Pie chart – Leave hours taken by Type, for the Department(s) and Leave Type(s) chosen in prior panel, for month chosen via drill-into. __Includes:__ Download to spreadsheet, e-mail with spreadsheet.
;Parameters: Departments (list of departments). May be restricted by User/Role security rights (IMSV), or user may choose from drop-down list – defaults from prior form and can be edited here.
;Leave Types: User may choose from drop-down list – defaults from prior form and can be edited here.
;Description: Pie chart – Leave hours taken by Type, for the Department(s) and Leave Type(s) chosen in prior panel, for month chosen via drill-into. __Includes:__ Download to spreadsheet, e-mail with spreadsheet.
;Parameters: Departments (list of departments). May be restricted by User/Role security rights (IMSV), or user may choose from drop-down list – defaults from prior form and can be edited here.
;Leave Types: User may choose from drop-down list – defaults from prior form and can be edited here.
At line 131 changed 3 lines
;Description: Table – Total Absent Days by Department, for the Department(s) and Leave Type(s) chosen in prior panel, for month chosen via drill-into. __Includes:__ Download to spreadsheet, e-mail with spreadsheet.
;Parameters: Departments (list of departments). May be restricted by User/Role security rights (IMSV), or user may choose from drop-down list – defaults from prior form and can be edited here.
;Leave Types: User may choose from drop-down list – defaults from prior form and can be edited here.
;Description: Table – Total Absent Days by Department, for the Department(s) and Leave Type(s) chosen in prior panel, for month chosen via drill-into. __Includes:__ Download to spreadsheet, e-mail with spreadsheet.
;Parameters: Departments (list of departments). May be restricted by User/Role security rights (IMSV), or user may choose from drop-down list – defaults from prior form and can be edited here.
;Leave Types: User may choose from drop-down list – defaults from prior form and can be edited here.
At line 135 changed 2 lines
!!Budget / BudgetMyDepartment (BDDB / BDDBM) – Department Budget\\
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
!!Budget / BudgetMyDepartment (BDDB / BDDBM) – Department Budget\\
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
At line 145 changed 2 lines
Restricted by Manager’s direct reports as well as Security settings\\
''Note – Security settings can cause totals displayed to differ by User.\\ ''
Restricted by Manager’s direct reports as well as Security settings\\
''Note – Security settings can cause totals displayed to differ by User.\\ ''
At line 149 changed one line
!Sub Panel 1 – Position Codes and Titles in Department\\
!Sub Panel 1 – Position Codes and Titles in Department\\
At line 151 changed 2 lines
Table – list of position codes based on the Department bar selected in the main Panel. This table includes, the Position Code, Position Title, Authorized FTEs, Actual FTEs, Variances and Requisitions. \\
''Note – Security settings can cause #’s/totals displayed to differ by User.\\ ''
Table – list of position codes based on the Department bar selected in the main Panel. This table includes, the Position Code, Position Title, Authorized FTEs, Actual FTEs, Variances and Requisitions. \\
''Note – Security settings can cause #’s/totals displayed to differ by User.\\ ''
At line 156 changed one line
!Sub Panel 2 (Form) – Drill to Positions (IDPS)\\
!Sub Panel 2 (Form) – Position For Department\\
At line 158 changed 3 lines
When any Position Code or Title is selected this will bring the user to the Position (IDPS) form. Respects form security (if user does not have access to sub-form used, cannot drill into via panel). \\
Note – clients must review the drill-into form and edit to match their requirements for Managers/Administrators viewing and/or editing. As with all forms, respects form/object security by User/Role.\\
!Sub Panel 3 – Requisitions for Department\\
When any Position Code or Title is selected this will bring the user to the Position (IDPS) form. Respects form security (if user does not have access to sub-form used, cannot drill into via panel).
||Column Name||Links To
|Position Code|IDPS
|Position Title|IDPS
|Authorized FTE| IDPS
|Actual FTE| Sub Panel - Budget Assigned For Position
|Variance| Sub Panel - Budget Assigned For Position
|Requisitions|Sub Panel - Requisitions For Department
\\
Note – clients must review the drill-into form and edit to match their requirements for Managers/Administrators viewing and/or editing. As with all forms, respects form/object security by User/Role.\\
!Sub Panel 3 – Requisitions for Department\\
At line 166 changed one line
!Sub Panel 4 (Form) – Drill to Postings (IRPO)\\
!Sub Panel 4 (Form) – Drill to Postings (IRPO)\\
At line 177 changed one line
Link to Candidate’s competencies via “% match” in the Candidate table. \\
Link to Candidate’s competencies via “% match” in the Candidate table. \\
At line 187 changed 2 lines
All denotes “All Competencies”; will return matches only where the Candidate has all of the required Competencies. Any returns Candidates with any of the required Competencies (the bar chart below includes % match). \\
!Sub Panel 1 (form) – Drill to View Candidate Profile (WRRCP)\\
All denotes “All Competencies”; will return matches only where the Candidate has all of the required Competencies. Any returns Candidates with any of the required Competencies (the bar chart below includes % match). \\
!Sub Panel 1 (form) – Drill to View Candidate Profile (WRRCP)\\
At line 196 changed one line
Displays Candidates’ existing Competencies; view only.\\
Displays Candidates’ existing Competencies; view only.\\
At line 198 changed one line
!Sub Panel 2 (form) – Drill to Maintain Candidate Resumes (WRRCR) \\
!Sub Panel 2 (form) – Drill to Maintain Candidate Resumes (WRRCR) \\
At line 209 changed one line
!!Daily Work Schedule (BTWS) – “Who’s Here”\\
!!Daily Work Schedule (BTWS) – “Who’s Here”\\
At line 212 changed one line
“Who’s Here”: Table of employees scheduled to work on the date selected, and clock in-out times if available. \\
“Who’s Here”: Table of employees scheduled to work on the date selected, and clock in-out times if available. \\
At line 218 changed one line
Based on the Date and the Work Area selected, the table will show employees in that Work Area with Shift start/end times, and clock-in times where provided (note – Work Rules/Time Rules for clock in-out, such as rounding, tolerance, etc., will be applied in the Timesheet). \\
Based on the Date and the Work Area selected, the table will show employees in that Work Area with Shift start/end times, and clock-in times where provided (note – Work Rules/Time Rules for clock in-out, such as rounding, tolerance, etc., will be applied in the Timesheet). \\
At line 220 changed 2 lines
!!Daily Leaves Department / Daily Leaves Admin (BADL / BADLM) – “Who’s Away”\\
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
!!Daily Leaves Department / Daily Leaves Admin (BADL / BADLM) – “Who’s Away”\\
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
At line 224 changed 3 lines
Defaulting to today’s date, the employees on leave will be displayed. The User is able to view the status of leave requests via icons, and drill to the Review Employee Leaves Calendar (WMALP) to approve/deny the Leave. \\
Leaves display an icon to indicate if they have been approved (check mark) or awaiting approval (question mark). Leaves that do not require approval (such as Sick – this is determined by Approvals logic) will display a check mark (i.e. they are inherently ‘approved’); mouse-over shows “not required”. \\
The Leaves shown are restricted by the Lexicon “X_DASH_LEAVE_TYPES”. The lexicon’s Saved Values = the Leave Type code(s) to be displayed (best practice – copy-paste the exact code from the Policy Type – IAPT form). \\
Defaulting to today’s date, the employees on leave will be displayed. The User is able to view the status of leave requests via icons, and drill to the Review Employee Leaves Calendar (WMALP) to approve/deny the Leave. \\
Leaves display an icon to indicate if they have been approved (check mark) or awaiting approval (question mark). Leaves that do not require approval (such as Sick – this is determined by Approvals logic) will display a check mark (i.e. they are inherently ‘approved’); mouse-over shows “not required”. \\
The Leaves shown are restricted by the Lexicon “X_DASH_LEAVE_TYPES”. The lexicon’s Saved Values = the Leave Type code(s) to be displayed (best practice – copy-paste the exact code from the Policy Type – IAPT form). \\
At line 228 changed 2 lines
!Sub Panel 1 (Form) – Leave Approvals\\
Clicking on a detail row in Sub Panel 1 takes the User to the Approvals form (W__M__ALP – Review Employee Leaves; assuming execution security allows for the User). \\
!Sub Panel 1 (Form) – Leave Approvals\\
Clicking on a detail row in Sub Panel 1 takes the User to the Approvals form (W__M__ALP – Review Employee Leaves; assuming execution security allows for the User). \\
At line 235 changed one line
Table, displays the Holiday Calendar applicable to the employee, based on their Work Rule Holiday Calendar (via Assignment to Work Rule to Holiday Calendar – IDHC). \\
Table, displays the Holiday Calendar applicable to the employee, based on their Work Rule Holiday Calendar (via Assignment to Work Rule to Holiday Calendar – IDHC). \\
At line 242 changed one line
!Sub Panel – Expired Certificates\\
!Sub Panel – Expired Certificates\\
At line 248 changed 3 lines
Displays the Employee’s Contacts (all contact types).\\
!Sub Panel (Form) – My Contacts\\
Clicking on a detail row in Main Panel takes the User to their Contacts form (WEECN – My Contacts; assuming execution security allows for the User). \\
Displays the Employee’s Contacts (all contact types).\\
!Sub Panel (Form) – My Contacts\\
Clicking on a detail row in Main Panel takes the User to their Contacts form (WEECN – My Contacts; assuming execution security allows for the User). \\
At line 255 changed 4 lines
Displays the Emergency Contacts for the Manager’s Employees (where the Contact’s Contact_type includes “Emergency”)\\
!Sub Panel (Form) – View My Employee’s Emergency Contacts\\
Clicking on a detail row in Main Panel takes the User to their Contacts form (WMEECN – View My Employee’s Emergency Contacts; assuming execution security allows for the User). \\
The WEECN form allows the User to view their direct and indirect employee’s emergency contacts. \\
Displays the Emergency Contacts for the Manager’s Employees (where the Contact’s Contact_type includes “Emergency”)\\
!Sub Panel (Form) – View My Employee’s Emergency Contacts\\
Clicking on a detail row in Main Panel takes the User to their Contacts form (WMEECN – View My Employee’s Emergency Contacts; assuming execution security allows for the User). \\
The WEECN form allows the User to view their direct and indirect employee’s emergency contacts. \\
At line 261 changed one line
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
At line 264 changed 2 lines
Displays a pie chart, counting the # of employees based on Group Details (IDGR) ‘Pay Type’. \\
Selection Parameters : a) Entity (multiple values) b) State (multiple values) c) Location (multiple days) d) No of Days (max 999): selects Active employees (based on Assignment – IEAS – status, prime assignment only), where ‘Last Worked Date’ from Employment (IEEI) is less than the # of days from the System Date. \\
Displays a pie chart, counting the # of employees based on Group Details (IDGR) ‘Pay Type’. \\
Selection Parameters : a) Entity (multiple values) b) State (multiple values) c) Location (multiple days) d) No of Days (max 999): selects Active employees (based on Assignment – IEAS – status, prime assignment only), where ‘Last Worked Date’ from Employment (IEEI) is less than the # of days from the System Date. \\
At line 272 changed one line
!Sub Panel – Postings for GL Fund Code\\
!Sub Panel – Postings for GL Fund Code\\
At line 287 changed one line
See also – Location Map (which utilizes the results of the “get Geo Codes” function). \\
See also – Location Map (which utilizes the results of the “get Geo Codes” function). \\
At line 297 changed one line
!Sub Panel 1 – Case Summary\\
!Sub Panel 1 – Case Summary\\
At line 300 changed one line
!Sub Panel 2 (Form) – Drill to Track Health Issues (IHHI)\\
!Sub Panel 2 (Form) – Drill to Track Health Issues (IHHI)\\
At line 309 changed 2 lines
Note – to work fully, this panel requires a licensed version of the Google API; in the demonstration version provided, it will resolve only a few addresses each time its run (this can appear to be a bug but is a restriction of the license; clients can arrange a Google API license). \\
See “Get Geo Codes” function in this document for additional details. \\
Note – to work fully, this panel requires a licensed version of the Google API; in the demonstration version provided, it will resolve only a few addresses each time its run (this can appear to be a bug but is a restriction of the license; clients can arrange a Google API license). \\
See “Get Geo Codes” function in this document for additional details. \\
At line 317 changed one line
!Sub Panel 1 – Location Details\\
!Sub Panel 1 – Location Details\\
At line 319 changed one line
!Sub Panel 2 – Location Map\\
!Sub Panel 2 – Location Map\\
At line 321 changed one line
Note – this form will be updated in upcoming versions, eliminating ID and Salary, and adding e-mail address. \\
Note – this form will be updated in upcoming versions, eliminating ID and Salary, and adding e-mail address. \\
At line 332 changed 3 lines
!Sub Panel (Forms) – Varies based on Main Panel contents\\
When a red rectangle is selected, the user is brought to an Admin Edition form. The specific form will depend on a date being within the month in view. For April there is a View Training / Course List and an employee’s birthday as an example. \\
When an employee name is selected the user is brought to the employee’s My Personal Profile form.\\
!Sub Panel (Forms) – Varies based on Main Panel contents\\
When a red rectangle is selected, the user is brought to an Admin Edition form. The specific form will depend on a date being within the month in view. For April there is a View Training / Course List and an employee’s birthday as an example. \\
When an employee name is selected the user is brought to the employee’s My Personal Profile form.\\
At line 341 changed one line
Pay Components displayed are based on Elements defined in the ‘Define Payrolls’ (IPPR) form and therefore will be the same as the Personality pay stub utilized. \\
Pay Components displayed are based on Elements defined in the ‘Define Payrolls’ (IPPR) form and therefore will be the same as the Personality pay stub utilized. \\
At line 344 changed 2 lines
Drop down list of Pay Period – Pay #s allowing an employee to select different pay periods from a list.\\
Print icon available – takes User to Print Paystubs (RESTUBD) or to a Pay Stub Details page (WEPDS).\\
Drop down list of Pay Period – Pay #s allowing an employee to select different pay periods from a list.\\
Print icon available – takes User to Print Paystubs (RESTUBD) or to a Pay Stub Details page (WEPDS).\\
At line 348 changed one line
!Sub Panel 1 – Pay details for Pay Period \\
!Sub Panel 1 – Pay details for Pay Period \\
At line 354 changed one line
!Sub Panel 2 – Pay Break down Chart\\
!Sub Panel 2 – Pay Break down Chart\\
At line 357 changed one line
Includes: Print – see Main Panel – same functionality.\\
Includes: Print – see Main Panel – same functionality.\\
At line 363 changed one line
!Sub Panel 2 (Form) – Payroll Deposits\\
!Sub Panel 2 (Form) – Payroll Deposits\\
At line 365 changed one line
The Print icon in the Main Panel and the Sub Panel 2 will open either the Payroll Deposit report for (RESTUBD) or a version of the View My Pay Stubs (WEPDS) form, which has its own ‘print’ icon. For RESTUBD, click on the ‘Launch’ icon to prepare the report. Once it completes a pdf file will open.\\
The Print icon in the Main Panel and the Sub Panel 2 will open either the Payroll Deposit report for (RESTUBD) or a version of the View My Pay Stubs (WEPDS) form, which has its own ‘print’ icon. For RESTUBD, click on the ‘Launch’ icon to prepare the report. Once it completes a pdf file will open.\\
At line 370 changed one line
Similar to the ‘messages’ function in the standard Self Service menus, displays Notes which confirm to the following:\\
Similar to the ‘messages’ function in the standard Self Service menus, displays Notes which confirm to the following:\\
At line 374 changed one line
!!Outstanding Approvals – All Users (BDATD)\\
!!Outstanding Approvals – All Users (BDATD)\\
At line 378 changed one line
Table – list of outstanding Approval tasks. \\
Table – list of outstanding Approval tasks. \\
At line 385 changed one line
Table – list of outstanding Approval tasks. \\
Table – list of outstanding Approval tasks. \\
At line 390 changed one line
!!Outstanding WorkFlow Events (BWTD) – formerly “Bottleneck Report”\\
!!Outstanding WorkFlow Events (BWTD) – formerly “Bottleneck Report”\\
At line 394 changed one line
Table – list of outstanding Workflow tasks for any User, due within 60 days of current date. \\
Table – list of outstanding Workflow tasks for any User, due within 60 days of current date. \\
At line 398 changed one line
Note: User can drill into the item to complete it, however, the table will not update/refresh simply by completing an edit (task does not ‘complete’), unless completion criteria outlined in the Workflow Action. The table is controlled by Action Status on the Workflow log (IMWA); if it does not change to ‘completed’, the item will continue to show on the list. \\
Note: User can drill into the item to complete it, however, the table will not update/refresh simply by completing an edit (task does not ‘complete’), unless completion criteria outlined in the Workflow Action. The table is controlled by Action Status on the Workflow log (IMWA); if it does not change to ‘completed’, the item will continue to show on the list. \\
At line 404 changed one line
Table – list of outstanding Workflow tasks. \\
Table – list of outstanding Workflow tasks. \\
At line 408 changed one line
Note: User can drill into the item to complete it, however, the table will not update/refresh simply by completing an edit (task does not ‘complete’), unless completion criteria outlined in the Workflow Action. The table is controlled by Action Status on the Workflow log (IMWA); if it does not change to ‘completed’, the item will continue to show on the list. \\
Note: User can drill into the item to complete it, however, the table will not update/refresh simply by completing an edit (task does not ‘complete’), unless completion criteria outlined in the Workflow Action. The table is controlled by Action Status on the Workflow log (IMWA); if it does not change to ‘completed’, the item will continue to show on the list. \\
At line 412 changed one line
!!Overtime (BPOW) – Overtime Warning\\
!!Overtime (BPOW) – Overtime Warning\\
At line 416 changed 3 lines
Colors indicate the level of “heat” – i.e. how much OT is acceptable for the Department, is determined by the following UDF’s that must be added to individual Departments: “Dash_OT_Green”, “Dash_OT_Yellow”, “Dash_OT_Red”. If not indicated for any department displayed, the system will default 14, 28, 35. Note that if OT exceeds the Dash_OT_Red value, it will adjust automatically.\\
Since the gauge can only show one value and one set of green, yellow and red gauge limits, it will use the highest value from the UDF’s. If a department doesn’t have one or more of these UDF’s set, it will use the defaults of 0 – 14 for green, 14 – 28 for yellow and 28 – 35 for red.\\
The Overtime Total Hours are shown in an ‘Overtime’ box.\\
Colors indicate the level of “heat” – i.e. how much OT is acceptable for the Department, is determined by the following UDF’s that must be added to individual Departments: “Dash_OT_Green”, “Dash_OT_Yellow”, “Dash_OT_Red”. If not indicated for any department displayed, the system will default 14, 28, 35. Note that if OT exceeds the Dash_OT_Red value, it will adjust automatically.\\
Since the gauge can only show one value and one set of green, yellow and red gauge limits, it will use the highest value from the UDF’s. If a department doesn’t have one or more of these UDF’s set, it will use the defaults of 0 – 14 for green, 14 – 28 for yellow and 28 – 35 for red.\\
The Overtime Total Hours are shown in an ‘Overtime’ box.\\
At line 422 changed one line
!Sub Panel 1 – Overtime by Department\\
!Sub Panel 1 – Overtime by Department\\
At line 425 changed one line
!Sub Panel 2 – Overtime Detail\\
!Sub Panel 2 – Overtime Detail\\
At line 432 changed one line
!!PA Scorecard (BDPAS) – Personnel Actions Scorecard \\
!!PA Scorecard (BDPAS) – Personnel Actions Scorecard \\
At line 441 changed 2 lines
!Sub Panel 1 – PA Scorecard details\\
Drill down from a chart’s bar to a table showing the PA details including the Person Code and name, PA Number, Create Date and Days to complete. The Indicator shows red for ‘not completed’ and green for ‘completed.’\\
!Sub Panel 1 – PA Scorecard details\\
Drill down from a chart’s bar to a table showing the PA details including the Person Code and name, PA Number, Create Date and Days to complete. The Indicator shows red for ‘not completed’ and green for ‘completed.’\\
At line 449 changed one line
!Sub Panel 2 (Form) – View personnel Actions\\
!Sub Panel 2 (Form) – View personnel Actions\\
At line 452 changed one line
!!Profile-NoPic / Profile (BEPN / BEPP) – Profile with/without Picture\\
!!Profile-NoPic / Profile (BEPN / BEPP) – Profile with/without Picture\\
At line 457 changed one line
The Policy Types shown in the Boxes are determined by a lexicon which contains the Leave Type to be displayed. Clients must create the lexicon and its values in the Maintain Lexicons (IMLN) form. The Lexicon Name must be “X_DASH_LEAVE_PROFILE”; the Saved Values = the Leave Type code to be displayed (best practice – copy-paste the exact code from the Policy Type – IAPT form). Two values can be used in the ‘Photo’ profile and three in the ‘No Photo’ profile (three can be defined in the Lexicon for clients who use both; the last will be ignored by the 2-panel profile form).\\
The Policy Types shown in the Boxes are determined by a lexicon which contains the Leave Type to be displayed. Clients must create the lexicon and its values in the Maintain Lexicons (IMLN) form. The Lexicon Name must be “X_DASH_LEAVE_PROFILE”; the Saved Values = the Leave Type code to be displayed (best practice – copy-paste the exact code from the Policy Type – IAPT form). Two values can be used in the ‘Photo’ profile and three in the ‘No Photo’ profile (three can be defined in the Lexicon for clients who use both; the last will be ignored by the 2-panel profile form).\\
At line 460 changed one line
!Sub Panel 1 – Leave Balances \\
!Sub Panel 1 – Leave Balances \\
At line 462 changed one line
!Sub Panel 2 (Form) – My Personal Profile (WEEPP)\\
!Sub Panel 2 (Form) – My Personal Profile (WEEPP)\\
At line 469 changed one line
Source is determined based on the Candidate_Source field on the Candidate form, based on the Candidate’s Submitted_On date value. \\
Source is determined based on the Candidate_Source field on the Candidate form, based on the Candidate’s Submitted_On date value. \\
At line 476 changed one line
Select a time period from the drop-down list. Defaults to “last 6 months”.\\
Select a time period from the drop-down list. Defaults to “last 6 months”.\\
At line 479 changed one line
!Sub Panel 1 – Candidates from Self-Service Web Source\\
!Sub Panel 1 – Candidates from Self-Service Web Source\\
At line 483 changed one line
!Sub Panel 2 – Cost for Posting Code\\
!Sub Panel 2 – Cost for Posting Code\\
At line 487 changed one line
!!Salary Survey (BSSU) – currently being updated – specifications below will change post 5.03.\\
!!Salary Survey (BSSU) – currently being updated – specifications below will change post 5.03.\\
At line 500 changed one line
!Sub Panel 1 – My Departments\\
!Sub Panel 1 – My Departments\\
At line 509 changed one line
!Sub Panel 1A – My Department Details\\
!Sub Panel 1A – My Department Details\\
At line 519 changed one line
!Sub Panel 2 – My Direct Reports\\
!Sub Panel 2 – My Direct Reports\\
At line 528 changed one line
!Sub Panel 2A – My Employees\\
!Sub Panel 2A – My Employees\\
At line 532 changed one line
From the Department Details table – links to forms: \\
From the Department Details table – links to forms: \\
At line 544 changed one line
Note that the values shown are for the current employment and display based on the “To Dates” tables, YTD (i.e. reporting on payroll results as stored in YTD pay component values). \\
Note that the values shown are for the current employment and display based on the “To Dates” tables, YTD (i.e. reporting on payroll results as stored in YTD pay component values). \\
At line 548 changed one line
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
There are two versions of this panel, one for managers and one for administrators. They function identically: the manager version is restricted to the employees that report to the User; the administrator version will see all employees (subject to IMSV security – i.e. can be used to restrict by Department). \\
At line 552 changed one line
Note that #’s/totals shown will differ based on User’s security settings (i.e. if provide only the Manager version, or to specific departments, will not see accurate information; clients may wish to provide Managers and Administrators with the Administration version, for accuracy in reporting). \\
Note that #’s/totals shown will differ based on User’s security settings (i.e. if provide only the Manager version, or to specific departments, will not see accurate information; clients may wish to provide Managers and Administrators with the Administration version, for accuracy in reporting). \\
At line 556 changed one line
!Sub Panel 1 – Turnover by Org level\\
!Sub Panel 1 – Turnover by Org level\\
At line 565 changed one line
!Sub Panel 2 – Turnover by Department\\
!Sub Panel 2 – Turnover by Department\\
At line 576 changed one line
Intended as a ‘group’ twitter feed – i.e. for a project team or organizational twitter account, for public messages / direct messages. \\
Intended as a ‘group’ twitter feed – i.e. for a project team or organizational twitter account, for public messages / direct messages. \\
At line 583 changed one line
URL’s can be embedded into a panel for quick access – a sample is provided. This is currently not editable at client sites. Clients with specific requests to use this functionality should contact High Line (via addition of Ccare case for the function).\\
URL’s can be embedded into a panel for quick access – a sample is provided. This is currently not editable at client sites. Clients with specific requests to use this functionality should contact High Line (via addition of Ccare case for the function).\\
At line 585 changed one line
Links to other web pages can be embedded into a panel for quick access – a sample is provided. This is currently not editable at client sites. Clients with specific requests to use this functionality should contact High Line (via addition of Ccare case for the function).\\
Links to other web pages can be embedded into a panel for quick access – a sample is provided. This is currently not editable at client sites. Clients with specific requests to use this functionality should contact High Line (via addition of Ccare case for the function).\\
At line 590 changed one line
Note that the values shown are for the current employment and display based on the “To Dates” tables, YTD (i.e. reporting on payroll results as stored in YTD pay component values). \\
Note that the values shown are for the current employment and display based on the “To Dates” tables, YTD (i.e. reporting on payroll results as stored in YTD pay component values). \\
At line 598 changed one line
No (see “edit the dashboards, below). Dashboards can be copied and re-named, and used for different Roles, but cannot be edited. This is due to the nature of the sub-license of the product used. \\
No (see “edit the dashboards, below). Dashboards can be copied and re-named, and used for different Roles, but cannot be edited. This is due to the nature of the sub-license of the product used. \\
At line 602 changed one line
Clients and their employees can add High Line-provided panels to the Configurable Dashboard – the system will remember each Users’ dashboard setup/preferences. \\
Clients and their employees can add High Line-provided panels to the Configurable Dashboard – the system will remember each Users’ dashboard setup/preferences. \\
At line 604 changed one line
See “request new panels/reports”.\\
See “request new panels/reports”.\\
At line 606 changed 3 lines
Each of the panels noted is a function within Personality, and can be secured by User/Role in the same manner as other functions (i.e. through IMFN, IMFDH, IMER…). The detail lists found in earlier sections include the function name.\\
!!Is Employee security/Manager Hierarchy/‘reports-to’ enabled?\\
Yes. In v.5.03+, a limited version of the manager hierarch logic has been enabled. For example, when your Managers see forms in Self Service, they can view direct reports as well as indirect. Due to performance limitations, in Logi, currently only direct reports-to employees are displayed for “Manager” roles. For panels that are intended for Administrators, all employees can be viewed, based on IMSV security settings; therefore, Clients can restrict Users’ access to different employee departments/groups/entities, etc., via the IMSV form. \\
Each of the panels noted is a function within Personality, and can be secured by User/Role in the same manner as other functions (i.e. through IMFN, IMFDH, IMER…). The detail lists found in earlier sections include the function name.\\
!!Is Employee security/Manager Hierarchy/‘reports-to’ enabled?\\
Yes. In v.5.03+, a limited version of the manager hierarch logic has been enabled. For example, when your Managers see forms in Self Service, they can view direct reports as well as indirect. Due to performance limitations, in Logi, currently only direct reports-to employees are displayed for “Manager” roles. For panels that are intended for Administrators, all employees can be viewed, based on IMSV security settings; therefore, Clients can restrict Users’ access to different employee departments/groups/entities, etc., via the IMSV form. \\
At line 610 changed one line
High Line will work with clients to add additional reports (being labelled as “panels” in order to avoid confusion with existing reports and elements). To request a new panel, please enter the request via CCare, including specifications for the initial panel and sub-panels/drill into’s. Include the fields that are required for each panel and sub-panel/drill-into’s, as well as any parameters required (parameters are the fields at the top of panels that allow users to changes dates, periods of time, etc.). High Line will review all requests and is very interested in developing new reports/panels that will be of interest to the client community. Cost may apply depending on the use/value of the item. Note that High Line will create new Panels and Dashboards assuming they are usable for the customer community; i.e. user-defined fields and user-defined columns are not supported as they are client-specific (new database fields will be considered that would replace a client-specific UDC/UDF). \\
High Line will work with clients to add additional reports (being labelled as “panels” in order to avoid confusion with existing reports and elements). To request a new panel, please enter the request via CCare, including specifications for the initial panel and sub-panels/drill into’s. Include the fields that are required for each panel and sub-panel/drill-into’s, as well as any parameters required (parameters are the fields at the top of panels that allow users to changes dates, periods of time, etc.). High Line will review all requests and is very interested in developing new reports/panels that will be of interest to the client community. Cost may apply depending on the use/value of the item. Note that High Line will create new Panels and Dashboards assuming they are usable for the customer community; i.e. user-defined fields and user-defined columns are not supported as they are client-specific (new database fields will be considered that would replace a client-specific UDC/UDF). \\
This page (revision-87) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop