SuccessionPlanning_VSN30_SP3_Admin_En[1].pdf

Nakisa SuccessionPlanning™Nakisa SuccessionPlanning for Managers™Nakisa TalentFramework™

Components of Visualization Solutions by Nakisa 3.0 SP3

Administrator Guide

2

Nakisa SuccessionPlanning VSN 3.0 SP3 Administrator Guide

Table of Contents

About Nakisa 6Welcome 7 Nakisa SuccessionPlanning 7 About this Guide 8 Typographic Conventions 9 Related Documentation 10 Technical Support 11Nakisa AdminConsole 12 About the Nakisa AdminConsole 12 Access the Nakisa AdminConsole 13 Serial File 14 Manage Nakisa AdminConsole Users 15 Using the Interface 17 Application Files and Builds 18 Loading a Build 19 Submit, Save, Save As, and Publish 20 Adding Comments to a Build 22 Launching the User Console 23SAP Connection and Authorization 24 Connection String 24 User Types 25 Authorization Objects 26 Emergency User 32 Authorization Profiles 33 Area of Responsibility 34User Authentication 35 Authentication Overview 35 Logon Screen 36 Single Sign-On with User ID and Password 37 Single Sign-On with Logon Tickets 39 Anonymous Access 40 Roles 41Application-Wide Settings 42 Portrait Images 42 Company Logo 43 Technical Support 44 Print and Export Defaults 45 Field Validations 46 Application Error Message 48 Profile Match 49 Succession Wizards 50 Application Modules 51 Caption Editor 52 Export and Import Captions 53

3


Using the RFC Trace 54 Writeback Refresh 57 Viewing and Exporting System Information 58User Preferences 59 User Preference Storage 59 Set Available Languages and Themes 62 Org Chart Mode 63Data Center 64 Data Center Overview 64 Manage Data Connections 65 Create Data Elements 69 Data Element Connecting to SAP RFC 70 Data Element for Single SAP Table 74 Data Element for Multiple SAP Tables 78 Data Element for Listings 86 Data Element for RDBMS Structure 91 Manage Nakisa ABAP Add-On Parameters 93Build Management 94 Export a Build 94 Import a Build 95 Upload Content 96 Reset the Build 97 Delete a Build 98Add-On Manager 99 Add-On Manager Overview 99 Activate an Add-On 100 Create an Instructions File 102 Enable an Inactive Add-On 103 Disable an Add-On 104 Remove an Add-On 105 Export a Configuration 106Org Charts and Hierarchies 108 Org Chart Overview 108 Enable/Disable 109 Data Connection 110 Fields 111 Hierarchies 112 Sub Category Groups 115 Activate Menu Links 116 Selected Items Fields 117 Sort Fields 118 Profile Window 119Listings and Searches 120 Listing Overview 120 Enable/Disable 121 Data Connection 122 Fields 123

4


Directory Filter 124 Selected Items Fields 125 Listing Columns 126 Search Form 127 Advanced Search Form 128Details Designer 129 Details Designer Overview 129 Access the Details Designer 130 Create New Detail 131 Details Title 132 Table Layout 133 Panels 135 Tabs 136 Sections 137 Move Controls 139 Remove Controls 140 Style Properties 141Views Designer 142 Views Designer Overview 142 Access the Views Designer 143 Create New Detail 144 Enable/Disable Views 145 Default View 146 Preview Mode 147 Condensed Style 148 View Caption 149 Table Layout 150 Panels 152 Sections 153 Box Size 155 Box Color 156 Color Mapping 157 Image Mapping 158 Hidden Sections 159 Move Controls 160 Remove Controls 161Analytics 162 Analytics Overview 162 Dashboard on Entry 163 Succession Planning 164 Competency 168 Holder/Successor 169 Potential/Performance 171Tasks 172 Task Overview 172 Enable/Disable 173 Data Connection 174 Fields 175

5


Form Fields 176Application Maintenance 177 Resetting Builds 177 Deleting Builds 178 Application Log Overview 179 Enabling Administrator and Error Logs 180 Change Log Settings 181 Viewing Error Logs 184 Exporting Error Logs 185 Generating Performance Reports 186 Creating Error Logs 187 Find and Trace Application Errors 188 Remote Support Procedure 189 Back Up and Restore 190Troubleshooting 191 Troubleshooting Overview 191 Unable to upload serial file, to log in, or to navigate 192 Error Message: Could not read properties file 193 Error Message: Invalid JAVA_HOME 194 User login screen does not load 195 User interface does not display correctly 196 Cannot load the Printing Wizard 198 Error Message: Internal Error 199 Org chart diagram is missing 200 Talent Profile Details window is blank 201 Session timeout in Flash Grid 202 Changes to a published build are unavailable to users 203Glossary 204

6


About Nakisa

Nakisa’s goal is to empower organizations with in-depth visibility into the enterprise so they can v iew, update,model, and analyze their talent inventory to make faster and better decisions. Nakisa applications transformhuman capital data into strategic business intelligence, giving companies the insight they need into their talentand organizations to support overall corporate objectives.

Visualization solutions by Nakisa are fully interoperable with the major Enterprise Resource Planning (ERP)platforms on the market and provide a single point of access to critical HR data for succession planning,organization charting and workforce modeling. The only Talent and Organization Management vendor fullycertified by SAP, Oracle, and Microsoft, Nakisa offers proven solutions that have been deployed to millions ofusers globally. Customers benefiting from Nakisa’s visualization solutions include Coca-Cola, Kohler, Motorola,Michelin, Airbus, RBC Financial Services, Wrigley, Carrefour, Statoil, Merck, and Alstom. For more information,visit: www.nakisa.com.

Successfully Implement SAP Visualization Solutions by Nakisa

Choose a Nakisa Certified Professional. Achieve a successful implementation of your SAP VisualizationSolution by Nakisa with a Nakisa Certified Professional. Only implementation partners that offer NakisaCertified Professionals are equipped with the expertise, tools and techniques to:

deliver innovative, best practice solutions that meet your needs and minimize your risk save you money, resources, and time by deploying your solution the right way, first time ensure the highest quality implementations

Find out more about our certification program here: www.nakisa.com/partners/nakisa-certification.htm

Thank you for choosing software by Nakisa.

Copyright Nakisa Inc. 2012. All rights reserved.

The information contained in this document represents the current view of Nakisa on the issues discussed as of the date of publication.Because Nakisa must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Nakisa, andNakisa cannot guarantee the accuracy of any information presented after the date of publication.

This document is for informational purposes only. NAKISA MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THEINFORMATION IN THIS DOCUMENT. This document should be read in conjunction with any applicable Professional Services Agreement that may be in effect.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of thisdocument may be reproduced, stored in or introduced into a retrieval system, or transmitted in any f orm or by any means (electronic,mechanical, photocopying, recording, or otherw ise), or for any purpose, without the express written permission of Nakisa Inc.

Nakisa may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in thisdocument. Except as expressly provided in any w ritten license agreement from Nakisa, the furnishing of this document does not profferany rights (license or otherw ise) to these patents, trademarks, copyrights, or other intellectual property.The example companies, organizations, products, people and events depicted herein are f ictitious. No association with any real company,organization, product, person or event is intended or should be inferred. Nakisa, Nakisa OrgManagement Series, Nakisa Talent Management Series, OrgChart, Directory, FloorPlan, OrgModeler, Edit,SelfService, SuccessionPlanning, HCM Dashboard, are either registered trademarks or trademarks of Nakisa Inc. in the United Statesand/or other countries.

SAP Talent Visualization by Nakisa is a trademark of SAP AG. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

http://www.nakisa.com

http://www.nakisa.com/partners/nakisa-certification.htm

7


WelcomeNakisa SuccessionPlanning

Nakisa SuccessionPlanning is used by a small group of human resource (HR) specialists who view andmaintain successor information in the organization. Succession planning is the process of identifying andassigning potential successors for job families and positions to ensure that key and critical positions are filled.The application provides tools for managers, talent management specialists (TMS), and senior managementthat help in each step of the process.

The application includes the Dashboard module that provides a real-time summary of overall workforceperformance. The analytics track vital succession planning information, such as the number of key positionsand successors, employee competencies, and staffing statistics.

8


About this Guide

The Administrator Guide is intended for administrators who configure, customize, and maintain Nakisaapplications.

This guide applies to the following products:

Nakisa SuccessionPlanning™ Nakisa SuccessionPlanning™ for Managers Nakisa TalentFramework™

This guide contains the following sections:

Nakisa AdminConsole provides an overview of the console, and lists the tasks the administrator performsto set up and customize the end-user application.

SAP Connection and Authorization contains information for connecting the application to the SAPsystem, setting up the remote function call (RFC) authorization objects, and creating user types for roles.

User Authentication describes how to define roles and set the way business users access the application. Application-Wide Settings describes how to set up the main application interface. User Preferences describes how to set the languages and themes available to end-users. Data Center describes how to access information from external sources by creating custom data elements. Build Management provides instructions for importing or exporting all the configurations for a build and

reseting or deleting builds. Add-On Manager describes how to manage customizations using the add-on feature. Org Charts and Hierarchies describes how to create organization hierarchies based on the organizational

chart information stored in the SAP data source. Listings and Searches describes how to set connections to the directories stored in the SAP data source,

design the listing grid, and set the directory behavior and search forms. Details Designer describes how to design the application details panel. Views Designer describes how to design org chart box views. Analytics describes how to set up metrics and alerts, and enable specific pages displayed in the Analytics

module. Tasks describes how to set up the edit forms available in Nakisa TalentFramework. Application Maintenance describes how to maintain the application, log errors, and the remote support

and backup/restore procedures. Troubleshooting identifies and solves common problems administrators may encounter as they set up

and maintain the application. Glossary contains a list of specific terms and definitions that relate to the Nakisa AdminConsole and its

tasks.

The information provided in this guide may not correspond exactly to the current application if it is customized.

9


Typographic Conventions

The following conventions are used in this guide.

Visual Cue Meaning

Connect The name of an interface element the user has to act on (button names, keys they need to press, the value of an element).

connection_name Text that is replaced by a user-supplied value, variable content,important notes, and references to other documents.

CTRL + ALT + DEL Key combinations.

C:\Program Files Command or file names, directory paths, text that appears on ascreen.

#!/usr/local/bin/perl

print "Hi there!\n";

Examples.

10


Related Documentation

The following supporting documents are available in addition to this guide:

The Release Notes describe new features and list known issues. The Master Guide provides general information about each application, the available licenses, and overall

implementation sequence. The Environment Checklist provides all the software, hardware, and SAP requirements, and supported

RDBMS databases The Nakisa ABAP Add-On Installation and Specifications Guide provides details about implementing the

custom function modules used to integrate Nakisa applications with the SAP system. The Nakisa Transport Package Installation and Specifications Guide provides details about implementing

the SAP HR Interface for Organizational Charting (HR-OCI) configurations on the SAP server. The Feature Checklist and Field Mapping spreadsheet lists all the features included in the application, and

the SAP tables and fields that are called for each feature. The User Guide includes information on application features and end-user tasks.

11


Technical Support

Consult the SAP Service Marketplace Web site at http://service.sap.com, or contact the SAP Global SupportCenter if you require standard product support for Nakisa applications.

http://service.sap.com

12


Nakisa AdminConsoleAbout the Nakisa AdminConsole

The Nakisa AdminConsole is used to select and customize what is presented to the end-user according to theirrole. The process includes the following main tasks:

Select how users are authenticated on the application serverSet connections to the SAP data sourceSet application defaultsTurn features on or offCustomize the basic graphical-user interface and user preferencesSet up object counts and alerts for HCM DashboardSet the data fields to call organization and human resource information used by the applicationDesign how this information is presented in the organizational charts and record detailsDefine the company hierarchy for the org chartSet up listing directories and search forms Set up user task forms for write-back operationsSave and publish settings and customizations

The Nakisa AdminConsole has different feature sets to configure, depending on the application instance:

SuccessionPlanning is used to set up the listings, org charts, and hierarchies for Employee and Position,and the analytics for HCM Dashboard.

TalentFramework is used to set up the listings, org charts, hierarchies, and task forms for NakisaTalentFramework.

Manager is used to set up the listings, org charts, and hierarchies for Nakisa SuccessionPlanning forManagers.

13


Access the Nakisa AdminConsole

The Nakisa AdminConsole is launched from a Web browser using the manager URL.

Each application instance has its own URL, as follows:

http://[hostname]/SuccessionPlanning/manager.jsp

http://[hostname]/TalentFramework/manager.jsp

http://[hostname]/Manager/manager.jsp

To access the console:

1. Enable JavaScript, cookies, and pop-up windows in the browser Internet options.

2. Open the manager URL. The Nakisa AdminConsole login screen is displayed.

3. Enter the default User name and Password: admin/admin, then click Login.

4. Select the required build from the list, then click Load. The Nakisa AdminConsole opens.

Information about the build is displayed in the top frame, and the administrator user name is displayed inthe top-right corner.

5. Click the user name to log out.

14


Serial File

The application Serial file is required to use Nakisa SuccessionPlanning. The serial specifies the modules,languages, and the total number of records available to the application according to the current license. This fileis implemented when the application is deployed on the server, or the administrator uploads it using the NakisaAdminConsole at first login, if required.

The Serial file is saved under ../XML in the main application directory:

/usr/sap/[system_name]/J00/j2ee/cluster/apps/Nakisa/[EAR]/servlet_jsp/[WAR]/root

To upload the Serial file:

1. Access the Nakisa AdminConsole. A message appears on the page indicating that the license is expired.

2. Click Upload.

3. Enter the administrator User name and Password, then click Login.

4. Click the Browse link, then navigate to the directory where the Serial file is stored.

5. Select the Serial file, then click Upload.

6. Close the browser window, then restart the application server.

7. Re-launch the Nakisa AdminConsole. The application reads the Serial file, and the required modules,features, and license are activated.

15


Manage Nakisa AdminConsole Users

Manage Administrator Console Users is used to perform the following tasks:

Add administrative users with read and write access Add administrative users with read-only access Change an administrator password Remove users

Access to the Nakisa AdminConsole is secured using the default user name 'admin' and password 'admin'.Nakisa recommends securing the AdminConsole by changing the default password for the 'admin' user.

To change the administrator password:

1. Access the Nakisa AdminConsole, then load the required build.

2. Click Security Settings > Manage Users.

3. Select the check box next to the required user, then click Change password. The Add or modify user formloads.

4. Enter a new Password.

5. Click Confirm. The password is changed.

Administrators must log out and then log back in if they change their own password.

This procedure adds a new administrative user with read and write access to the Nakisa AdminConsole.

To add an admin user:


2. Click Create new user. The Add or modify user form loads in the wizard.

3. Enter the User name and Password.

4. Click Confirm. The user is created and can access the Nakisa AdminConsole using the credentialsprovided.

16


Read-only access is configured for remote support of Nakisa applications. The following actions are disabled inthe Nakisa AdminConsole when a read-only user logs in:

Submit in all setup wizards Save As, Save, and Publish build Create new admin user Change admin password Delete admin users

To add a read-only user:


2. Click Create new user.

3. Add the prefix 'ro_' to the User name, for example: ro_admin.

4. Enter the Password.

5. Click Confirm. The user is created and can access the Nakisa AdminConsole in read-only mode.

This procedure removes a user. The default 'admin' user cannot be deleted.

To remove a user:

1. Select the check box next to the required user, or click to select all users in the list (click to clear all thecheck boxes).

2. Click Delete selected user(s). The user is removed from the Existing users list and can no longer accessthe Nakisa AdminConsole.

17


Using the Interface

The Nakisa AdminConsole is used to configure Nakisa SuccessionPlanning according to companyrequirements. This section provides an overview of the Nakisa AdminConsole interface.

Nakisa logo: Accesses the Nakisa website.

Build panel: Displays information on the current build. An arrow button may appear here. It is used toexpands/collapse the Menu panel (6) to extend the Wizard panel (7).Navigation bar: Indicates the path taken to arrive at the current setup wizard, and provides access tocontext-sensitive help .Export Changes, Save As, Save & Publish buttons: Used to export, create, modify and publishbuilds. These buttons will only appear after you click the Submit button after completing a wizard, or ifyou click the Save & Publish current build link (see 8 below).Comments/User: Button to bring up a comment form, the user name of the administrator who islogged in (click this link to log out).

Menu panel: Displays the application and modules menus.

Wizard panel: Displays the application and module setup wizards.

Save & Publish current build: Displays the Nakisa AdminConsole start page, with the Save As,Save, and Publish buttons on the top-right of the console. If you click this link before the final Submitstep in a Wizard, you will lose your changes.

Wizard buttons: Used to navigate through the wizard steps, and to submit changes once done.

18


Application Files and Builds

The resources and settings used by the application are localized in a specific build under the .system/Admin_Config/ directory. The build name corresponds to an ID number and application instance(for example: ___001___SuccessionPlanning ).

Application data is stored in resource files so the administrator can change configurations without recompilingthe entire application. Resource files are arranged according to a defined configuration type in the followingdirectory:

.system/Admin_Config/[build_name]/AppResources/[config_name]

A typical example is the SAP data connection string in the SAPConnection.xml file. This file is stored in thedataconnectionconfiguration directory under ../AppResources .

The settings used by the interface components are stored in a series of text files named according to thesetting type in the following directory:

.system/Admin_Config/[build_name]/SettingsResources/

A typical example is the name of your organization in the CDSCompanyTitle.txt file.

Note: Changes made in the AdminConsole are written to the corresponding files under ../AppResourcesand ../SettingsResources when you click Save, Save As, or Publish. Refer to the topic Submit, Save,Save As, and Publish.

19


Loading a Build

Application settings are stored in specific builds that can be loaded, modified, saved and published by usingthe Nakisa AdminConsole. Nakisa applications come with one or more default builds that have pre-definedsettings. Administrators can also create and save customized builds. Refer to the Application Files and Buildstopic for more information about builds.

To load a build:

1. Log in to the Nakisa AdminConsole.

2. From the list of available builds that appears, select the build you wish to publish.

3. Click Load. The selected build is loaded, and the following information appears in the Build Panel at thetop of the Nakisa AdminConsole:

Item Description

Build Name The name of the currently loaded build. If it is not one of the default builds, "usersaved" is appended to the name.

Last Modified The date and time the build settings were last modified.

Published The date and time the build was last published.

Comments Comments, if any, related to the build.

[admin] The user name of the currently logged in administrator.

20


Submit, Save, Save As, and Publish

The Confirm step at the end of each Nakisa AdminConsole wizard has the Submit action that temporarilystores the application settings to the browser session memory.

Save your changes to the current build as new application settings are submitted in each wizard. There are twosave actions available: Save and Save As.

Refer to the Application Files and Builds topic for more information about Nakisa AdminConsole builds.

Save

Save the changes made to the current build at any time.

To save the current build:

1. Click Finish and Submit in any Nakisa AdminConsole wizard.

The Export Changes, Save As, Save, and Publish actions load in the top frame.

Refer to Export a Build for information about the Export Changes action.

2. Click Save.

The settings are written to the application files stored in the directories of the current build.

Save As

Save a new version of an existing build using the Save As option.

Tip: Save As is useful for creating test builds and back-ups. Only custom builds saved in this way can be deleted.

To save the settings under a new build :

1. Log in to the Nakisa AdminConsole, then load the required build.

2. Click Save & Publish current build in the menu bar.


3. Click Save As. The Save build as dialog box appears.

4. Enter a name for the new build in the field provided.

5. Click Save As.

The build selected at login is copied to a new directory under .system/Admin_Config/ . The new buildappears in the build list the next time the Nakisa AdminConsole is accessed.

21


Publish

The Publish action performs these tasks:

Changes made to the current build are saved (written to the application files stored in the directories of thecurrent build).

Configuration files and directories of the administrator build are deployed to the main application directory. Add-ons are deployed in the main application directory. All application settings saved in the administrator build are applied to the live client accessed by end-users.

Prior to publishing a build to the live client, it is recommended to verify that the application settings in the NakisaAdminConsole are complete and correct.

The typical settings to check before publishing include:

Test the required data connections in the Data Center Verify the security authentication settings Ensure the required modules are enabled Test the data connections for the org chart hierarchies and application listings Verify the org chart root selected for each hierarchy

To publish a build:

1. Log in to the Nakisa AdminConsole, then load the required build.

2. Click the Save & Publish current build link in the menu bar.


3. Click Publish.

4. Log out of the Nakisa AdminConsole when the " Publish was successful" message appears.

Note: Any changes made to a build are immediately available to connected users when a build is published. It isnecessary, however, for the user to initiate an action (such as choosing a menu item) that w ill prompt the serverto refresh the current contents of his or her browser window. Refer also to the troubleshooting article Changesto a published build are unavailable to users.

22


Adding Comments to a Build

The Build panel provides the name, last-modified date, and last-published date for the selected build by default.Administrators can include their own comments about configuration changes made to a build in this panel.

To add comments:

1. Click next to Comments in the build panel. The Modify dialog box appears.

2. Enter text describing the build in the field provided, then click OK.

3. Click Save. The comment is added to the build panel, and the build selection frame.

23


Launching the User Console

Changes made to the application using the Nakisa AdminConsole appear in the user interface after theadministrator publishes the build.

To access the User Console:

1. Enable the following Internet options in the Web browser:

JavaScript Cookies Pop-up windows

2. Open the one of the following URLs to access the required application instance:

http://[hostname]/SuccessionPlanning/default.jsp

http://[hostname]/TalentFramework/default.jsp

http://[hostname]/Manager/default.jsp

The login frame is displayed.

3. Enter your User name and Password.

4. Select the required Language from the drop-down list if the application is available in multiple languages.

5. Select Accessibility Mode to access the text-only interface.

6. Click Log In. The application loads in the Web browser and displays the selected language.

Note: The login frame is omitted when the application is set up for Single Sign-On or anonymous access.

24


SAP Connection and AuthorizationConnection String

The application connects to the SAP data source using a connection string.

The following is an example connection string:

ASHOST=SAPSERVER SYSNR=0 CLIENT=800 USER=user PASSWD=password

This string has the following attributes:

Attribute Description

ASHOST SAP server name

SYSNR SAP system number

USER SAP user name

PASSWD SAP user password

CLIENT SAP client number

The ASHOST, SYSNR, and CLIENT attributes connect to the SAP server. Use these attributes for SingleSign-On (SSO) authentication. The connection is established using the credentials entered in the log-in form orSSO ticket.

The USER and PASSWD attributes contain the user credentials retrieved by the log-in form or SAP portal.

The MYSAPSSO2 attribute replaces USER and PASSWD when Single Sign-On with Logon Tickets authenticationis used.

Use all connection attributes if the application is set for Anonymous Access.

A service account may be used with single sign-on authentication to retrieve data from the SAP server. Thisreduces the overhead created when new user server connections are set. The service account securitypermissions are applied instead of user permissions. Enter values for USER and PASSWD in this scenario.

25


User Types

Create the following user types, and assign the roles required for minimum authorization to the application:

User Type Roles

Talent Management Specialist(TMS)

SAP_TMC_TALENT_MANA_SPECIALIST

Manager SAP_TMC_MANAGER

Human Resource Manager IDES_HR_MANAGER

26


Authorization Objects

Roles are used to group employees and assign those groups a specific set of rights and priv ileges to theapplication. New roles should be created using the authorization objects provided in the tables that follow.

Authorization Check for Remote Function Call Access and underlying HR module objects

Object Field Value

S_RFC ACTVT 16

RFC_NAME /NAKISA/*HCM_ORG_PUBLISH_XMLHRMSS_OCIHRTMC_SERVICESHRWPC_EMPLOYEEPROFILE_45FFHRWPC_GENERAL_INFOTYPESHRWPC_GENERAL_ORGSTRUCTUREHRWPC_OADP_GENERALPERSRFC1RH65RHPD_SEARCHRHPE_PDOTYPE_Q_BAPI (qualification and qualification type attributes)RHPHRHPKRH_ORGPUB_APPRH_PDOTYPESSDIFRUNTIMESDTXSYSTSYSU (required for RFC connection)

RFC_TYPE FUGR

Authorization for File Access

Object Field Value

S_DATASET ACTVT 33

FILENAME *

PROGRAM *

27


Archive Link: Authorizations for Access to Documents

Note: Depending on the client's setup, multiple values for the OADOKUMENT field may be required.

Object Field Value

S_WFAR_OBJ ACTVT 03

OAARCHIV *

OADOKUMENT HRIBMPFOTOHRICOLFOTOHRIEMPFOTOHRIPCXFOTOHRIPDDFOTOZHRICOL614

OAOBJEKTE PREL

CO-CCA: General Authorization Object for Cost Center Accounting

Object Field Value

K_CCA CO_ACTION 0003

KSTAR *

RESPAREA *

CO-CCA: Cost Center Master

Object Field Value

K_CSKS ACTVT 03

KOKRS *

KOSTL *

Authorization for Table Maintenance (using standard tools such as SM30)

Object Field Value

S_TABU_DIS ACTVT 03

DICBERCLS KAPAPC06SCSS (required for single sign-on)

28


HR: Master Data (used for HR infotype authority checks)

Refer to the SAP Library article "P_ORGIN (HR: Master Data)" for additional information.

Object Field Value

P_ORGIN AUTHC R (for display only)W (to enable write-back)

INFTY 0000-000200060007 (planned working time)00080016003200410077 (additional personal data)0105

PERSA * (Personnel area)

PERSG * (Employee group)

PERSK * (Employee Subgroup)

SUBTY * (Subtype are subdivisions of info types)

VDSK1 * (Organizational Key)

HR: Master Data - Personnel Number Check (configuration for display only)

Note: This check is not performed if the user has no personnel number assigned, or if the user accesses apersonnel number other than his or her own.

Object Field Value

P_PERNR AUTHC R

INFOTYPE 0000-000200060007000800160032004100770105

PSIGN * (Interpretation of assigned personnel number)

SUBTY * (Subtypes are sub-divisions of info types)

http://help.sap.com/erp2005_ehp_03/helpdata/en/3e/b8b83b5b831f3be10000000a114084/content.htm

29


HR: Master Data - Personnel Number Check (configuration to enable write-back)

Object Field Value

P_PERNR AUTHC W

INFOTYPE 0000-0002000600080016003200410105

PSIGN * (Interpretation of assigned personnel number)


Personnel Planning (configuration for display only)

This object is used to perform authorization checks for fields in Personnel Management components, such asOrganizational Management and Personnel Development.

Object Field Value

PLOG INFOTYPE 1000-100210031007101110281033

ISTAT * (Planning Status)

PLVAR * (Plan Version from Structural Authorization)

PPFCODE DISP (Function Code)HITWLISDSIMU

OTYPE * (Object Type)


30


Personnel Planning (configuration to enable write-back)

Object Field Value

PLOG INFOTYPE 1000-10021003100710111028103374007406-7410742098009806-9814

ISTAT * (Planning Status)

PLVAR * (Plan Version from Structural Authorization)

PPFCODE AENDDELDISP (Function Code)HITWINSELISDSIMU

OTYPE * (Object Type)


HR: Master Data - Extended Check (configuration for display only)

Object Field Value

P_ORGXX AUTHC R

INFOTYPE 0000-000200060007000800160032004100770105

SACHA * (Payroll Administrator)

SACHP * (HR Master Data Administrator)

SACHZ * (Time Recording Administrator)

SBMOD * (Administrator Group)


31


HR: Master Data - Extended Check (configuration to enable write-back)

Object Field Value

P_ORGXX AUTHC W

INFOTYPE 0000-0002000600080016003200410105

SACHA * (Payroll Administrator)

SACHP * (HR Master Data Administrator)

SACHZ * (Time Recording Administrator)

SBMOD * (Administrator Group)


The following authorization objects require configuration if Context Sensitive Structural Authorization is set up inthe SAP system:

Object Description

P_ORGINCON HR: Master Data with Context

P_ORGXXCON HR: Master Data - Extended Check with Context

32


Emergency User

Emergency users can access the SAP system in the rare case where all administrative users are locked due toincorrect configuration and/or forgotten passwords.

The application relies on the emergency user concept (SAP* system super user or DDIC data dictionary andsoftware logistics super user) for the back-end ERP system or HR system.

Refer to the "Activating the Emergency User" article in the SAP Library for related procedures.

http://help.sap.com/saphelp_erp2004/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/frameset.htm

33


Authorization Profiles

Create authorization profiles for users in the organization plan:

1. Run the 'RHPROFL0' report using the default parameters.

2. Use the 'PROFL0' evaluation path.

3. Enter the Object type (S or P) and the corresponding ID.

Note: It is recommended to run the in 'Test Session' before executing in real time.

34


Area of Responsibility

Define structural authorizations for the user's area of responsibility:

1. Create the Organization Plan (PPOM_OLD or PPOME).

2. Create personnel master records (PA40).

3. Create the User ID (SU01).

4. Create the Infotype 0105 (PA30), and assign the user to the personnel number.

5. Create Structural Authorization Profiles (OOSP).

6. Create the PD Profiles Infotype (PO13 for the Position, or PO10 for the Organizational Unit).

7. Assign users to a structural authorization profile (OOSB).

8. Set up security as required (SU01 or PFCG).

Create the manager's area of responsibility for the positions:

1. Use transaction code PO13 (Maintain Position).

2. Enter the required Position.

3. Click Relationships, then create a new record.

4. Create the A741 relationship between the manager position and the organizational unit.

Wait until the TREX indexes are generated as scheduled, or schedule one immediately to verify the area ofresponsibility.

35


User AuthenticationAuthentication Overview

Nakisa SuccessionPlanning supports the following authentication methods:

Basic authentication with logon screen Single Sign-On with User ID and Password (used for SAP systems that do not support SAP logon tickets) Single Sign-On with Logon Tickets Anonymous access

Access to the end-user application is set in the Nakisa AdminConsole.

36


Logon Screen

The user provides an ID and password when the authentication mechanism is set to Logon Screen. Log-incredentials are transmitted to the server over the HTTP connection using HTTP POST. This mechanism isused when the application is deployed independently.

Consult the "Using Basic Authentication (User ID and Password)" article in the SAP Portal for more information.

To enable logon screen access:


2. Click Security Settings > Authentication Settings.

3. Select Logon Screen.

4. Click Authentication Source.

To set the authentication source :

1. Enter the SAP Application Server Host name. This value is used for the ASHOST attribute in theconnection string.

2. Enter the appropriate two-digit SAP System Number. This value is used for the SYSNR attribute in theconnection string.

3. Enter the Client number assigned by SAP. This value is used for the CLIENT attribute in the connectionstring.

4. Click Finish, then click Submit.

http://help.sap.com/saphelp_nw04s/helpdata/en/f3/a193e2f6ee1b45ac2e386468d3c272/content.htm

37


Single Sign-On with User ID and Password

The user is authenticated when they access the application after logging in to the SAP portal. This mechanismis used for SAP systems that do not support SAP logon tickets, typically when the application is embedded inthe SAP portal using iView.

Consult the "Single Sign-On with User ID and Password" article in the SAP Portal for more information.

The following conditions apply when this mechanism is selected:

The application server must be on the same domain as the SAP portal server. Cookies must be enabled on the client browser.

To enable single sign-on access:



3. Select Single Sign-On with User ID and Password.

4. Click Credentials.

The default values in the Credentials form correspond to the iView content supplied by Nakisa.

To set the credentials:

1. Leave the defaults if no changes were made to the iView content, then click Authentication Source, orproceed to step 2 to update the iView if required.

2. Select the required Source. Credentials are typically transmitted to the server over the HTTP connectionusing HTTP POST or HTTP GET.

3. Enter the Parameter name that holds User ID. The parameter used in SAP connection strings is user.

4. Enter the Parameter name that holds Password. The parameter used in SAP connection strings ispasswd.


http://help.sap.com/saphelp_ep50sp2/helpdata/en/1c/22afe6b26011d5993800508b6b8b11/content.htm

38



1. Enter the SAP Application Server Host name. This value is used for the ASHOST attribute in theconnection string.




39


Single Sign-On with Logon Tickets

The user is issued an SSO2 ticket after successful authentication on the SAP server. SSO2 is stored in thecookie, and supplies access to the application using single sign-on. The cookie value is MYSAPSSO2. Thismechanism is the most secure, as it uses SAPSSOEXT to extract the user ID from the logon ticket, andverify.pse to verify the portal certificate.

The following conditions apply when the Single Sign-On with Logon Tickets mechanism is selected:

The SAP system and SAP portal are configured to accept logon tickets. The application server are on the same domain as the SAP portal server. Users have the same user ID in all SAP systems that are accessed using SSO with logon tickets. Cookies are enabled on the client browser.

Refer to the "Using X.509 Client Certificates" article in the SAP Portal for more information on using singlesign-on with logon tickets.

To enable single sign-on access:



3. Select Single Sign-On with Logon Tickets.



1. Enter the SAP Application Server Host name (for example, SAPONE.dev.nakisa.net ). This value isused for the ASHOST attribute in the connection string.




http://help.sap.com/saphelp_nw73/helpdata/en/43/85496b532f2673e10000000a1553f7/frameset.htm

40


Anonymous Access

The user accesses the application in anonymous mode, without providing any form of authentication, when theauthentication mechanism is set to Anonymous. This mechanism is used if the company wishes to makeanonymous content available through the Internet on an external portal.

Consult the "Using Anonymous Logon to Access the Portal" article in the SAP Portal for more information.

To enable anonymous access:



3. Select Anonymous.


http://help.sap.com/saphelp_nw04s/helpdata/en/cd/1aad4abcb98c4597f9e395a6b62f43/content.htm

41


Roles

Roles are used to group employees and assign those groups a specific set of rights and priv ileges to theapplication and sensitive data resources.

Note: This feature is not enabled by default. For more information, please contact your Nak isa representative.

42


Application-Wide SettingsPortrait Images

The administrator sets the directory path and file extension (GIF or JPG) for the employee portraits. Theseimages appear in the Details panel when users access employee records.

Employee portraits are stored as separate files in a folder under the main application directory. The directory Images/Portraits/ is the default.

To set up employee portraits:


2. Click Application-wide Settings > General Settings.

3. Enter the Portraits Path to the folder that stores the image files.

4. Select GIF or JPG as the Portraits Image Extension type. The application adds the specified extension tothe field value used for the portraits.

5. Alternatively, select None if the data source contains a field linking employees to their portrait files.

6. Click Submit.

43


Company Logo

The administrator sets the image for the company logo that appears in the print header.

To set up the company logo:



3. Enter the Company Logo Image path to the directory that stores the image files. The directoryimages\logo.gif is the default. The fields Company Title and Company URL are not currently used inthe User Console. You do not need to set these fields.

Note: Nakisa recommends using GIF images that are no larger than 150 x 150 pixels for the company logo.

4. Click Submit.

44


Technical Support

Note: The Technical Support Configuration section is nonfunctional in VSN 3.0.

Make technical support information available to end-users:



3. Go to the Technical Support Configuration section.

4. Enter the Telephone Number users can call when help is required.

5. Enter the E-mail Address to contact technical support.

6. Click Submit.

45


Print and Export Defaults

The administrator sets the following print and export settings:

Default paper size and page orientation for printing Unit of measure for the header and footer size Text for the header and footer disclaimer Available export formats for org charts and listings

To set up print and export:


2. Click Application-wide Settings > Print / Export Preferences.

3. Configure the default print and export settings:

a. Select the default paper Size.b. Select Portrait or Landscape as the default paper Orientation.c. Select the Units of measure for the header and footer in inches (in.) or centimeters (cm.).

4. Set up the Top (header) disclaimer area:

a. Select Enabled to activate the disclaimer for the header.b. Enter the Disclaimer Area Height. The unit of measure is defined in step 3-c. The height is measured

from the top of the page for headers, and from the bottom of the page for footers. Text appears on thefirst line in the defined area.

c. Type the Disclaimer Area Text for the header. d. If the application is configured for multiple languages, click and enter translated text; click to

accept the changes. e. Align the header (Top) Left, Center, or Right.f. Click to preview the disclaimer.

5. Set up the Bottom (footer) disclaimer area. This disclaimer is set up using the same procedure as theheader.

6. Set up the Export Settings:

a. Under Export Settings - Chart, enable or disable one or more export options to allow users to exportorg charts in the specified format.

b. Under Export Settings - Listings, enable or disable one or more export options to allow users toexport listings in the specified format.

Note: The ability to export org charts to Microsoft Visio format is available with some customization.Please contact Nakisa Support for more information.

7. Click Submit.

46


Field Validations

The fields in the search, advanced search, and task forms use specific validation settings to help users enterand select correct values when they search for records in a directory or perform an edit.

There are two validation types:

Validation Description

User Input The user enters data in the form field.

Fixed List The user selects a value from a pre-defined list.

Note: The "date" and "string" fields are used by the application, and are unavailable for edit.

This procedure adds a user-input validation to the application.

To add a validation:


2. Click Application-wide Settings > Configure Validations.

3. Click Add New. The Create New Validation form loads on the page.

4. Enter the Validation Name, then select User Input from the drop-down list.

5. Enter the Min length and Max length for the validation.

6. Create a regular expression, if required:

a. Enter the Regular Expression syntax.b. Enter the Regular Expression Caption.c. Enter the Regular Expression Error Message. This is the error message that displays to users when

the validation fails.d. If the application is configured for multiple languages, click and enter translated text; click to

accept the changes.

7. Add Valid and Invalid Characters for the user input:

a. Enter a text character in the field provided, then click Add Character.b. Select a text character from the list, then click Remove Selected Character, if required.

8. Click Save.

9. Select a Validation Type at any time to modify existing user-inputs.

47


This procedure adds a fixed-list validation to the application.

To add a fixed-list validation:

1. Click Application-wide Settings in the menu panel, then click Configure Validations to load the setupwizard.

2. Click Add New. An empty validation form loads in the wizard.

3. Enter the Validation Name, then select Fixed List from the Validation Type drop-down list.

4. Create the fixed list values:

a. Click [+] to add list items.b. Enter the Value for the list item.c. Enter the captions for each list item in the language fields.d. Click [-] to remove list items individually, or Clear all to remove all items.e. Click Load from file to add list items from an external file.

5. Click Save.

6. Select a Validation Type at any time to modify existing fixed lists.

Note: The Delete button is non-functional.

48


Application Error Message

The error message is displayed to end-users when an internal error occurs. The administrator writes thismessage and may provide a phone number or an e-mail address for users to contact if the problem persists.

To set the error message:


2. Click Application-wide Settings > Configure Error Message.

3. Enter the Error Heading.

4. Enter the Error Message Line. Three lines are provided.

5. If the application is configured for multiple languages, click and enter translated text; click to acceptthe changes.

6. Click Submit.

49


Profile Match

This procedure enables or disables Profile Match in the application.

To enable Profile Match:


2. Click Application-wide Settings > Enable/Disable Profile Match.

3. Select or clear Enable Profile Matching.

4. Click Submit.

50


Succession Wizards

This procedure enables or disables a succession wizard in the application.

To enable a wizard:


2. Click Application-wide Settings > Enable/Disable Wizards.

3. Select the check box next to the wizards to enable.

4. Clear the check box next to the wizards to disable.

5. Click Submit.

51


Application Modules

Nakisa applications consist of self-contained components, called “modules”, that are used to combine featuresspecific to a particular set of data. The listings and hierarchies that pertain to positions are grouped in thePositions module, for example.

The module (and the feature set it contains) is added to the application menu bar in the end-user interfacewhen it is enabled in the Nakisa AdminConsole.

To enable a module:


2. Click the required module. The module, and its features, load in the interface.

3. Select Enable Module in the side panel. Alternatively, clear this check box to disable the module.

Note: The application Preferences are unavailable to users when the Preferences module is disabled.

4. Repeat the process for the required modules.

52


Caption Editor

Administrators can change captions displayed in the User Console in one or more languages using the CaptionEditor. All application captions are stored in XML files located in the Languages folder of the main applicationdirectory. Language files contain caption keys that define where that caption is displayed in the application. Anycaptions that are modified are stored as custom captions in the AdminCustom.xml language file.

Note: Caption keys cannot be modified.

To change application captions:


2. Click Application-wide Settings > Caption Editor. The editor loads in the interface and displays a table ofall application captions in the available languages with their respective language keys.

3. If required, modify the display settings of the editor:

a. To change the vertical size of the text boxes, select the TextArea check box, enter the number ofvertical Lines. Click anywhere outside the text box to refresh the display.

b. To change the horizontal size of the text boxes, click the Chars field and enter the text box width incharacters.

c. Select the Custom Captions Only check box to display modified captions only. Any captions that aremodified in other wizards, such as listing or org chart captions, are included in the custom captions.

d. Select the number of Entries Per Page from the drop-down menu in the top-right corner of the page.e. Click the arrow icons at the bottom-right corner of the page, or select a Page number to view additional

entries.

4. To search for a specific caption, type a term in the Enter Search text box and click Search. The applicationdisplays entries containing the search term in any language. Click Reset to display all language entries.

5. To discard all caption changes made in the current session, click Reset Changes.

Note: Captions are reset to the values they had the last time Submit was clicked.

6. Click Submit to temporarily save the changes.

7. Click Publish to update the application language files.

53


Export and Import Captions

Administrators can export or import captions using a comma-separated values (CSV) file to modify captions inother applications such as Microsoft Excel. Captions are exported to the LanguageCaptions.csv file inUTF-8 format to support special character sets in multiple languages. The LanguageCaptions.csv file issaved in the [application directory]/.system/Admin_config/[build] directory. A copy of thesame file is also saved in the LanguageCaptions.zip file found in the same directory.

Note: As CSV files use commas (,) to separate values, any commas contained in captions are exported as",". Similarly, when modifying captions in another application, ensure that "," is used for anycommas to be displayed in the application, otherwise the file cannot be imported into the Nak isa application.

Exporting Captions

To export application captions:



3. Modify any required captions using the editor.

4. To export only modified captions, select the Custom Captions Only check box. Otherwise, all captions areexported.

5. Click Generate CSV. The LanguageCaptions.csv file is created in the [applicationdirectory]/.system/Admin_config/[build] directory.

6. Click the Download link to open or save the CSV file to a location of your choosing.

Note: Although the CSV file is updated every time Generate CSV is clicked, the Download link is notrefreshed; consequently, the link will open the first CSV file generated in the current session. If you havealready exported a CSV file and then make additional caption changes in the same session, publish the build,close the browser, and access the Nakisa AdminConsole before exporting the new changes.

Importing Captions

To import application captions:



3. Click Browse..., then locate the CSV file to import.

4. Click Import from CSV. The captions are updated in the editor.

5. Modify any required captions using the editor.

6. Click Submit to temporarily save the changes.

7. Click Publish to update the application language files.

54


Using the RFC Trace

The RFC Trace tool allows you to measure the performance of Remote Function Calls (RFCs) to the SAPsystem and data calls to RDBMS databases, as well as the accuracy of the received and processedinformation. When the tool is enabled, for every user action performed in the User Console, you can view thetime it took to retrieve and process the information, and the input and output parameters in the related RFCs (ifan RFC was used to retrieve the data). This tool logs standard SAP RFCs, custom Nakisa RFCs, andcustomer-specific RFCs.

The RFC Trace logs the following event types:

ControllerAction (green): The action that the user performed in the User Console. GenericDataAction (blue): The data calls to the SAP or RDBMS database. SapDataCommand (orange): The command processor (i.e.integration class) that performs read, write, or

modify operations against the SAP database by calling one or more RFCs, and then processes the fetcheddata. This event type is only displayed for data calls to SAP systems.

RFC (red): The Remote Function Call that fetches data from the SAP server and performs basicprocessing. This event type is only displayed when an RFC is used to retrieve data.

The RFC Trace results can be displayed in nested view (as shown in the following example), or in table view.

55


The RFC Trace provides the following information for each event type (with examples based on the prev iousscreenshot):

RFC TraceInformation

Description Example

Date The date and time that the event occurred. Mon Dec 12 12:01:20 EST 2011

Name The name of the data action, user action,integration class, or RFC. The name alsoincludes whether it was the start or end of anevent.

start chartviewdetails

Type The type of the event: ControllerAction GenericDataAction SapDataCommand RFC

ControllerAction

Stage In table view, the start or end stage is identifiedagain.

start

Level In table view, the level indicates how nested theevent is.

Note that there may be events (for example,SapDataCommands) nested within other eventsof the same type.

Refer to the example screenshot.

Time The time (in ms) it took to perform the task: RFC: The time it took to fetch the data and

perform some basic processing in the RFC. SapDataCommand: The time it took to fetch

data using the required RFC(s), and toprocess the data (i.e. to construct theresulting datasets). The time for theSapDataCommand is therefore the sum ofthe RFC times (if there is more than oneRFC) and the processing time.

GenericDataAction: The time it took toconstruct all of the datasets.

ControllerAction: The time it took to parse theserver response.

Refer to the example screenshot.

Sum RFC The total time (in ms) it took to fetch and processdata in the RFCs for one ControllerAction. Thistime is calculated by adding all of the RFC times.

For the chartviewdetailsControllerAction, the Sum RFCis: 338+352+327+51+353=1421

Sum SAP Data The total time (in ms) it took process the fetcheddata. This time is calculated by adding all of thefirst level SapDataCommands.

For the chartviewdetailsControllerAction, the Sum SAPData is:415+392+463+107+384=1761

The majority of the information listed in the previous table can also be found in the Error log. On the other hand,the RFC Trace tool allows you to view more detailed information about each event by clicking on the events:

ControllerAction details:

56


The name of the action The total time (in ms) it took to perform the action

GenericDataAction: The filter (SQL "where" clause) used to retrieve the data The SAP or RDBMS table from which the data is retrieved The data connection type used to retrieve the data. The data connection name corresponds to the data

connection configured in the Data Center. The dataset that was created. If more than one integration class is used for the data call, the merged

dataset is displayed.

SapDataCommand details: The name of the command processor or integration class The dataset that was created

RFC details: The name of the RFC Total time (in ms) Date and time that the RFC took place Input parameters Output parameters Table parameters

Note: Using the RFC Trace impacts performance in the User Console. The overhead of enabling the traceresults in the higher times in the Error log compared to the RFC Trace for the same event. You should onlyenable this tool for testing purposes.

To use the RFC Trace tool :

1. In the menu panel, click Application-wide Settings > RFC Trace.

2. Click Trace is disabled - Click to enable. The RFC Trace tool is running when the button displays Traceis enabled - Click to disable.

3. Access the User Console and perform your required actions.

4. Return to the Nakisa AdminConsole, and access the RFC Trace feature again.

5. Click Refresh. The RFCs are listed in the window below the buttons.

6. To view the RFCs in table format, select the Table view checkbox.

7. To view more information about each signal, click on the signal itself.

8. To clear the RFCs currently displayed, click Clear.

9. When you are finished using the RFC Trace tool, click Trace is enabled - Click to disable.

57


Writeback Refresh

Changes made within the application are immediately made in the connected SAP database, in a processcalled writeback. In order to view these changes reflected within the application in real-time as they areimplemented, Writeback Refresh must be enabled. Writeback Refresh is only available for changes made tothe following UI items:

Org Charts Details panels Listings

Note: Enabling Writeback Refresh may have an adverse effect on performance. If you disable WritebackRefresh, you can refresh the desired UI item by clicking to another item then back again.

To enable Writeback Refresh:


2. Click Application-wide Settings > Enable/Disable Writeback Refresh.

3. Select the boxes for the UI items for which you want to enable Writeback Refresh.

4. Click Submit.

58


Viewing and Exporting System Information

System information is available to view important information about the build, connections and computer in use.The available information includes:

Product name, release, edition and build number Database connection information Hardware specifications Security settings Enabled languages

In addition to viewing system information, error logs and system information can be exported. Note that theerror logs can be exported on their own.

To view and export logs and system information:

1. In the menu panel, click Application-wide Settings > System Information.

2. Click Export Logs and System Info at the bottom-right of the scrren. The application creates a ZIP filecontaining the system information (in HTML format) and the log files.

3. Click the Download System Info link that appears, then save the file to a location of your choice.

59


User PreferencesUser Preference Storage

The User Preferences panel defines the method of storing user preferences, such as preferred language,theme, listing settings, and saved listings. This allows users to quit and return to the application without hav ingto recreate their personal settings.

The application provides three options to store user preferences:

No session storage: User preferences are maintained while the browser is opened, but are discardedonce the session is closed.

Store user preferences in cookie: User preferences are stored as a cookie in the user's browser settings.The cookie is updated each time the user changes preference settings, and retrieves the preferences whenthe user logs in to the application with the same computer and browser.

Store session in DB: When a user logs in to the application, their login credentials are mapped to a uniqueID in a separate database. Each time that user logs in, their preferences are retrieved, even if they log infrom a different computer or browser. If the application is set to anonymous login, a unique ID is created inthe database and stored as a cookie in the user’s web browser settings. If that user quits and returns (usingthe same computer with the same browser), the cookie is read, and the preferences retrieved. To use thisoption, you must have access to a database application on a server other than the Nakisa Applicationserver. See the Environment Checklist for a list of supported database applications.

The procedure to set each option is outlined below.

No Session Storage

To disable user preference storage:


2. Click Application-wide Settings > User Preferences.

3. Select No session storage, then click Submit.

Store User Preferences in Cookie

To store user preferences in cookies:



3. Select Store user preferences in cookie. The cookie setting form loads in the wizard.

4. Enter the Cookie duration. The duration is reset each time the user changes a preference setting.

5. Select the required Storage criteria. There are four available options:

Preferences: Stores all settings from the Preferences panel, including date format, default language,application theme, and org chart mode.

OrgCharts: Stores user-saved org charts. Note that users cannot save org charts if this setting isdisabled.

60


Listings: Stores user-saved listings. Note that users cannot save listings if this setting is disabled, Shortcuts: Saves any icons that are moved from the org chart or listings Actions menu to the panel top

bar.

Note: The maximum size for cookies is 4 KB. Consequently, the maximum size can be reached orexceeded if users save multiple org charts, listings, and/or shortcuts. Users must then delete some of theirsaved settings to save new ones. To prevent the cookie from reaching its maximum size, select the Preferences option only.

6. Click Submit.

Store Session in DB

User preferences are saved in a "swap file", which is a database table with one row per unique user. Each rowcontains fields for each of the settings a user can save from the User Console. Each row also has a date/timestamp field that is updated every time the user logs in. Any changes to his or her preference settings arereflected in changes within the existing table row. The database table grows as the number of unique usersincreases. You can reduce the size of the table by deleting rows with date/time stamps earlier than a specifieddate.

To store user preferences in a separate database :



3. Select Store session in DB. The storage database form loads in the wizard.

4. Select the Server Type, then enter the Server Name.

For Oracle databases, use one of the following syntaxes to enter the Server Name:

Server name/service name For example: PRODSRV/ORA92 where PRODSRV is the server name and ORA92 is the service name.

Fully qualified server name/port number/SID For example: ora92.hq1.nakisa.net:1521:ora92

IP address/port number/SID For example: 192.168.0.148:1521:ora92

TNS entry name For example: ORA92.HQ1

Note: If the TNS entry name is used, the oracle.net.tns_admin system property in yourenvironment must be set to the location of the TNSNAMES.ORA file, typically found in the$ORACLE_HOME\network\admin\ directory.

5. Enter the Initial Catalog to specify the database that will be used to store user preferences. Skip this stepfor Oracle databases.

6. Enter the User Name and Password for accessing the database.

7. Click Test Connection. A message indicates the success or failure of the connection. You must have asuccessful connection to continue.

8. Click Recreate Structure to define the table structure and fields needed to store user preferences.

61


WARNING : If the database already exists, this operation will remove and replace any existing tables. Alluser preference settings will be permanently deleted !

9. Click Submit.

Clean the swap file every two months to reset the user storage database. User preferences that have not beenaccessed since the specified date are deleted.

To clean the swap file:


2. Select the required month, day, and year from the calendar, or enter the date in the field provided using thefollowing syntax: MM/DD/YYYY.

3. Click Clean Swap File.

4. Click Submit.

62


Set Available Languages and Themes

Application menus, dialog boxes, headings, and other user interface elements are displayed in the languageselected as default in the Nakisa AdminConsole. Client data remains in the language set in the sourcedatabase.

The application includes two color themes:

Classic Theme (blue) Gray Theme

This procedure enables the languages and themes that the user can select in the application Preferencesdialog box, and sets the default settings that load when users log in.

To set up user preferences:


2. Click Preferences > Preference Settings.

3. Select the check box to enable the required languages.

4. Select the radio button to set the default application language.

5. Select the check box to enable the required themes.

6. Select the radio button to set the default application theme.

7. Click Submit.

8. If user preferences are stored in a separate database, clean the swap file to reset the defaults.

63


Org Chart Mode

The application supports two org chart modes:

Basic Mode uses HTML to render the org chart diagram. Standard Mode uses Flex to render the org chart, and offers additional features for users (Adobe Flash

Player 10 or higher is required). This mode is only available to users when enabled by the administrator.

When enabled, users can switch between the two modes in the Application Preferences. The administrator setsthe default org chart mode, and enables the setting in the Application Preferences.

To set the org chart modes:


2. Click Preferences > Preference Settings.

3. In the Org Chart Mode Configuration section, select the default org chart mode:

Select Set Standard Mode as Default to display Standard org charts when users access theapplication.

Clear the check box to display Basic org chart by default.

4. Set the modes available to users:

Select Allow Switching Between Modes to enable users to change modes. Clear the check box to enable the default mode only.

5. Click Submit.

The following table outlines the settings for the required result in the User Console:

User Console Result Setting Selection

Both modes are available to users, and Standardorg charts are displayed when users access theapplication.

Allow Switching Between Modes

Set Standard Mode as Default

Both modes are available to users, and Basic orgcharts are displayed when users access theapplication.

Allow Switching Between Modes


Only Standard org charts are available to users. Allow Switching Between Modes


Only Basic org charts are available to users. Allow Switching Between Modes


64


Data CenterData Center Overview

The Data Center is the central location in the Nakisa AdminConsole that is used to manage data connectivity inthe application.

Use the Data Center to:

Create the mandatory data connections to servers that provide new data information Modify existing data connections Create and modify data elements that are used in org chart box views, searches, and the Details panel Test connectivity to ensure the server is responding Test the performance time required to process a request

The following tools are available:

Data Connections: Create and manage multiple connections to SAP and/or external data warehouses. Data Element Management: Create and modify data elements using standard SAP remote function calls

(RFC) or custom NakisaRFCs. Nakisa ABAP Add-On Settings: Manage the parameters used by the Nakisa ABAP Add-On.

65


Manage Data Connections

Create and manage multiple connections to SAP and external data warehouses in the Data Center. Any newconnections can then be used to create org chart box views and Details panels.

A connection must exist to facilitate data exchange to the client. The following data connection types aresupported:

SAP ERP Server SAP MaxDB IBM DB2 Microsoft SQL Server Oracle

The supported versions are provided in the Environment Checklist.

Data Connection

To add a new data connection:


2. Click Application-wide Settings > Data Center.

3. Click Data Connections.

4. Click Create New.

5. Enter a unique Name for the connection.

6. Enter a Description.

7. Select the required Data Connection.

8. Click Confirm.

The new connection is added as the last item the Select a connection list.

66


SAP ERP Server Connection

To establish the connection to the target SAP server :

1. Go to the Select a Connection list.

2. Use the page controls to find the required connection.

3. Select the check box next to an SAP connection and click Configure.

4. Click and enter the Connection String for the SAP data source in the field provided. Refer to theConnection String topic for information about the SAP data connection.

Warning: The USER and PASSWD attributes must be defined in the connection string in order to create dataelements. Once all data elements using the current SAP connection are created and submitted, repeatsteps 1 through 4 and remove the USER and PASSWD attributes from the connection string. Failure toperform this step will grant any user access to all data allowed by the user name entered in the connectionstring.

5. Click Test Connection.

6. Click to confirm the connection.

7. Click Save.

8. Click Submit.

Relational Database Management System

To establish the connection to the target server and database :



3. Select the check box next to a database connection and click Configure. The Server Type is selected bydefault.

4. Enter the Server Name.

For Oracle databases, use one of the following syntaxes to enter the Server Name:

Server name/service name For example: PRODSRV/ORA92 where PRODSRV is the server name and ORA92 is the service name.

Fully qualified server name/port number/SID For example: ora92.hq1.nakisa.net:1521:ora92

IP address/port number/SID For example: 192.168.0.148:1521:ora92

TNS entry name For example: ORA92.HQ1

Note: If the TNS entry name is used, the oracle.net.tns_admin system property in yourenvironment must be set to the location of the TNSNAMES.ORA file, typically found in the$ORACLE_HOME\network\admin\ directory.

67


5. Enter the Initial Catalog property for the required database in the data source. Skip this step for Oracledatabases.

6. Enter the User Name and Password for the server.

7. Click Test Connection.

8. Click Save when the connection is successful.

9. Click Submit.

68


Remove Connection

Note: Remove all field sections that point to a specific connection from the details panels, listings, or org chartviews before proceeding.

To delete a connection that is no longer used:



3. Select the connection Name.

4. Click Delete.

69


Create Data Elements

Nakisa applications use data elements to retrieve and filter information displayed in the User Console. Dataelements are instances of one or more database tables, and have their own attributes—such as databaseconnection, table name, and fields—that are used by other configurations within the application. Standard SAPremote function calls (RFC) or custom NakisaRFCs filter or process the retrieved data.

Note: Creating data elements requires knowledge of data elements, SAP tables, SAP RFCs, and Nak isaRFCs.Contact your implementation partner if you need assistance.

The Data Element Management section of the Data Center provides the following options for creating dataelements:

Edit/Create new data element connecting to SAP RFC sets the import parameters to retrieve data froma standard SAP RFC.

Edit/Create new data element for SAP table reads data from one table. Edit/Create new data element joining multiple SAP tables reads data from a maximum of 18 SAP

tables. Edit/Create new data element for a report (listing) is used specifically for listings. Edit/Create new data element for an RDBMS structure reads data from a table stored in a relational

database management system (RDBMS).

70


Data Element Connecting to SAP RFC

The SAP system contains the function modules that can be called from any ABAP program. The remotefunction call (RFC) is the standard interface for communication between SAP systems and the client system.

The Edit/Create new data element connecting to SAP RFC wizard is used to configure the import and exportparameters that call data from an SAP RFC. This process involves the following steps:

Create a data elementEnter the RFC nameSet the import parametersReview the exported tables and fieldsPreview the loading time for the selected data

SAP Requirements

The function module must be remote enabled on the SAP server. The authorizations required by the RFC must be applied to the user account(s) used by Nakisa.

Prerequisites

Establish a connection to the SAP data source in the Data Connections screen. Ensure the connection string has a defined user name and password so the SAP system can authorize the

connection.

RFC Compatibility

Restrictions apply to the types of RFCs that are compatible for use in the Nakisa AdminConsole Data Center.

Compatible Incompatible

The query is specified entirely in the importparameters.

RFCs that do not have import parameters aresupported.

RFCs with table parameters that have a direction of'import'.

The import parameters are "simple", for example:the import parameter has a single value:

Employee ID

First Name

The import parameters are structures or tables, forexample:

HRTMC_GET_POSITION_ATTR

HRTMC_GET_JOB_FAMILY_ATTR

The filter in the import parameter has a sequence ofconditions with the AND operator:

OBJID = '00000100' AND OTYP = 'O' AND

PLVAR ='01'

The filter in the import parameter has a sequence ofconditions that combine AND and OR operators:

(OBJID = '00000100' AND OTYP = 'O' AND

PLVAR = '01') OR (OBJID = '50000005'

AND OTYP = 'O' AND PLVAR = '01')

RFCs with export parameters must have simplestructures, for example: the structure is like a tablewith a single row.

HRWPC_RFC_EP_READ_PERSONALDATA

HRWPC_RFC_EP_READ_GENERALDATA

The export parameter has nested structures, forexample, the attributes of the structure arethemselves structures or tables.

HRTMC_GET_POSITION_ATTR

HRTMC_GET_JOB_FAMILY_ATTR

Data Element

71


Create the data element for the transaction.

To create a data element:


2. Click Edit/Create new data element connecting to SAP RFC .

3. Click Create New Data Element.

4. Enter a unique Name that represents the data type. The syntax is Object, Property and the Representationterm.

5. Enter a Description to identify how the data element functions.

6. Select the Data Connection to the required SAP application server host.

7. Click Create. The data element is added to the list.

8. Select the new Data Element, then click Next.

RFC Name

The remote function call (RFC) must exist in the SAP data source. Enter the RFC Name for the specific datarequest and click Next, or perform a search.

To search for an RFC:

1. Enter a partial Name followed by the wildcard character '*'.

2. Click Search.

3. Select the required RFC from the list. The RFC Name field is populated with the selected item.

4. Click Next.

72


Import Parameters

The required and optional (x) parameters are available for selection.

To fetch the import parameters of the RFC from the function builder :

1. Select at least one of the required parameters needed to link the details. Typically, the parameter that holdsthe ID is selected.

2. Select an optional (x) import parameter for the data request.

3. Click and enter a new Caption in the field provided. Selected parameters must have a caption name toproceed to the next wizard step.

4. Select a different Source from the drop-down list and enter a Value for the import parameter (optional).

The following source options are available:

Source Use Example

Filter Retrieve information after a transaction. Import_BUSINESSAREAID

Constant Retrieve information that is constant and pass it to theRFC.

EN

User Call specific information from the User Population atlogin.

Role

Session Read session information for the user roles establishedin the portal.

CLIENT

DateTime Set an effective date. NOW

5. Click to confirm your changes.

6. Click Next.

Exported Tables

The table structures listed represent the export parameters generated by the remote function call. Select thetables that hold the required fields, then click Next.

This optional procedure is for existing builds. Set a table alias in cases where the configurations rely on specifictable names in order to load.

To set an alias:

1. Click next to the required table.

2. Enter a new table name as the Alias.

3. Click to confirm the table alias.

73


Field Mappings

Review the table fields exported by the remote function call. The primary table is set automatically, and tells thedata element the exact table to use in the application.

Set a different primary table (optional) when the RFC exports more than one table.

To set a primary table:

1. Select a table from the drop-down list.

2. Review the fields in the table.

3. Click Set as Primary when the table that holds the required fields is found.

Set the field alias and caption to use in the section details.

To set an alias:

1. Click and enter a new field name as the Alias.

2. Enter a Caption for the field.

3. Click to confirm.

4. Click Next.

Preview

The Preview displays the query that is sent to the data source.

Call the RFC function to preview the loading time of fields for each record generated in the application.

To generate a preview:

1. Click and enter a Test Value for the parameter. For example, enter an org unit ID.

Note: The preview generates all rows in the table when the Value is left blank.

2. Click to set the test value.

3. Click Call RFC Function.

A preview loads on the screen. The loading time for one record is presented.

4. Select a new table from the drop-down list, if required.

5. Test the value again.

6. Click Finish when the time is satisfactory.

7. Click Submit to save the data element.

74


Data Element for Single SAP Table

The Edit/Create new data element for SAP table wizard is used to define the data and table structurespassed between the SAP server and the application.

Configure the Nakisa ABAP Add-On to read one source SAP table using generic Nakisa remote function calls.The process involves the following steps:

Create the data element used in the transactionDefine the source table returned from the SAP serverDefine the fields to use in the applicationPreview the data loading time

Prerequisite

Establish a connection to the SAP data source in the Data Connections screen.

Data Element

To create the data element for the transaction:


2. Click Edit/Create new data element for SAP table.




6. Select the Data Connection to the SAP system where the required table is stored.

7. Click Create.

8. Select the Data Element from the list.

9. Click Next.

75


Table Details

To define the table to be downloaded from the SAP source :

1. Click Add.

2. Enter the table Name (must not contain spaces). This name identifies the table throughout the wizard.

3. Enter the SAP Table name from which data is retrieved.

4. Enter the active Plan Version of the current valid organizational plan. Typically, use the default value,[PlanVersion] , as this value references a keyword defined by the application.

5. Select YES when an infotype-based Authority Check is required.

6. Enter the Object Type on which the authority check is performed. If the SAP table does not have an objecttype (OTYPE) field, leave this blank.

7. Enter the Language code. It is recommended to use the default value, [LanguageKey] , as this valuereferences a keyword defined by the application.

8. Enter a Condition to be applied to the table. Use a space character between operators, for example:LANGU = 'E'.

9. Enter a Description for the table, then click Add. The table is created and added to the list.

10.Click Next.

76


Table Fields

The following tasks are performed in this step:

Add the required fields from the SAP tablesSpecify the fields that hold date format dataDefine structural authorization checks for fields

To select the fields to be downloaded from the table :

1. Click Add to open the Add Fields form.

2. Select the SAP Field Name for the required columns, then click Add.

3. Use the page controls provided to find and add the required fields.

4. Click Done when all the fields are added.

Perform this task to identify when the field stores a date.

To set a date field:

1. Click to activate the required field.

2. Select Date as the Type.

3. Click to accept the changes.

Structural authorization checks are performed during the processing of HR master data. These checksdetermine the hierarchy scope and fields individual SAP system users can process in the client.

To define a field for the authorization check:


2. Select YES to perform a structural authorization check on the field.

3. Enter the Object Type defined for the field.

4. Select the required Action to perform when the object type and ID fails the structural authorization.

Two actions are available:

Delete Row removes the entire row in the return table. Delete Unit removes the ID unit in the row.


6. Click Next.

77


Preview


Read the SAP table to preview the loading time of fields for each record generated in the application.


1. Click and enter a Value for the parameter. For example, enter an org unit ID.



3. Click Preview.

A preview loads on the screen. The loading time for the value is presented.



78


Data Element for Multiple SAP Tables

The Edit/Create new data element joining multiple SAP tables wizard is used to define the data and tablestructures passed between the SAP server and the application.

Configure the Nakisa ABAP Add-On to read a maximum of 18 source SAP tables. The process involves thefollowing steps:

Create the data element used in the transactionDefine the source tables and join conditionsDefine the tables and fields returned from the SAP serverDefine the required operations to be applied to tables returned to the applicationPreview the data loading time

Prerequisite


Data Element



2. Click Edit/Create new data element joining multiple SAP tables .




6. Select the Data Connection to the SAP system where the required tables are stored.

7. Click Create.


9. Click Next.

79


Table Details

To define the SAP tables to be downloaded from the data source:

1. Click Add.









10.Repeat the process to add the required tables, then click Next.

80


Table Fields


Add the required fields from the SAP tablesDefine structural authorization checks for fields


1. Select the Table Name.






To define the field for the authorization check :








6. Click Next.

81


Join Details

The following joins are available:

Inner Join combines the column values of two tables. The rows returned have at least one columnmatching the fields in both tables.

Left Join returns all rows from the "left" table, and the matching rows from the "right" table. Right Join returns all rows from the "right" table, and the matching rows from the "left" table.

To define the join conditions that control how the SAP tables are combined :

1. Click Add.

2. Select the From Table and From Field.

3. Select the required Join Type.

4. Select the To Table and To Field.

5. Click Add.

6. Repeat the process join additional tables, when required.

7. Select a join in the list, then click Move Up or Move Down to set the table join order.

8. Click Next.

Output Table Details

Create additional output tables to return multiple tables without modification, then set the SAP table as theoutput source. Note that only one joined table can be returned in this configuration.

To define the output table returned from the processor :

1. Click Add.

2. Enter the output table Name.

3. Leave the Joined Table as the Source, or select the required source SAP table.

4. Enter the output table Description.

5. Click Add.

6. Click Next.

82


Output Table Fields


Select the fields for the output tableSet a new alias for field namesSpecify the fields that hold date format dataSet a new primary table

To add the required fields for the output table:






The output table fields are given an alias that identifies the source table.

Perform this task to use a new alias.

To set an alias:


2. Enter a new Alias for the field name.

3. Optional: Modify the field Description.


Perform this task to identify when the field stores a date.

To set a date field:


2. Select Date as the Type.


83


Set a different primary table (optional) to specify the table to process.

To set a primary table:

1. Select a table from the drop-down list.

2. Review the fields in the table.

3. Click Set as Primary when the table that holds the required fields is found.

4. Click Next.

Processed Table Details

Define a processed table and apply additional filters, analytics, or grouping operations to further process thedata returned to the application. Click Preview to skip this optional procedure, if required.

To define the table returned to the application once the output table is processed by the client:


2. Click Add.

3. Enter the Name of the processed table.

4. Select Download YES to include the table in the returned data set.

5. Enter the Description.

6. Click Add.

7. Click Next.

84


Processed Table Fields

Define the operations performed on the processed table to return data to the application. At least one Selectstatement is required.

To define the functions performed on returned tables :

1. Select the operation Name.

The following operations are available:

Operation Description

Select Select data in the database by a specific field.

WhereClause Extract data that meets the specified criterion.

GroupBy Group the results set by one or more columns (comma-delimited data format).

OrderBy Sort results by a specified column in ascending or descending order: ASC|DESC.

2. Select the required Function.

The following functions are supported:

Function Description

Concatenate Combine results two character strings end to end with a defined Delimiter.

Index Select the record based on the index value defined in the Delimiter.

AddColumn Add a new column in the returned data table.

Count Get the number of records.

Sum Get the sum.

Avg Get the average.

Max Get the maximum value.

Min Get the minimum value.

Arithmetic Calculate based on the binary operation defined in the Delimiter.

Addition, subtraction, multiplication, and division are the supported operators.

DateCalculation Calculate the number of years between two dates. The Date Type isautomatically selected this function is used.

3. Enter the function Value.

4. If the field is a date type field, then select Date from the Type drop-down list.

5. Enter the field name Alias.

85


6. Enter a Delimiter.

The delimiter is used for the following purposes depending on the function type:

Defines the index value for the index function. Defines the operator for the arithmetic function. Defines the delimiter for the concatenate function.

7. Click Add.

8. Click Next.

Preview


Read the SAP table to preview the loading time of fields for each record generated in the application.





3. Click Preview.




86


Data Element for Listings

The Edit/Create new data element for a report (listing) wizard is used to define the data and table structurespassed between the SAP server and the application listings.

Configure the Nakisa ABAP Add-On to read a maximum of 18 source SAP tables. The process involves thefollowing steps:

Create the data element used in the transactionDefine the source tables and join conditionsDefine the tables and fields returned from the SAP serverPreview the data loading time

Prerequisite


Data Element



2. Click Read SAP Table (Directory).




6. Select the Data Connection to the SAP system where the required tables are stored.

7. Click Create.


9. Click Next.

87


Table Details

To define the SAP tables to be downloaded from the data source:

1. Click Add.









10.Repeat the process to add the required tables, then click Next.

88


Table Fields


Add the required fields from the SAP tablesDefine structural authorization checks for fields








To define the field for the authorization check :








6. Click Next.

89


Join Details

The following joins are available:

Inner Join combines the column values of two tables. The rows returned have at least one columnmatching the fields in both tables.

Left Join returns all rows from the "left" table, and the matching rows from the "right" table. Right Join returns all rows from the "right" table, and the matching rows from the "left" table.

To define the join conditions that control how the SAP tables are combined :

1. Click Add.

2. Select the From Table and From Field.

3. Select the required Join Type.

4. Select the To Table and To Field.

5. Click Add.

6. Repeat the process to join additional tables, when required.

7. Select a join in the list, then click Move Up or Move Down to set the table join order.

8. Click Next.

Output Table Fields

Specify the fields for the output table.

To add the required fields for the output table:


2. Select the Source for the required fields, then click Add.



5. Click Next.

90


Preview


Read the SAP table to preview the loading time of fields for each record generated in the application:





3. Click Preview.




91


Data Element for RDBMS Structure

The Edit/Create new data element for an RDBMS structure wizard is used to define the data and tablestructure passed between a relational database management system (RDBMS) and the application. Thisprocess involves the following steps:

Create the data element used in the transactionDefine the source data table that holds the required fieldsDefine the fields returned from the databasePreview the data loading time

Prerequisite

Establish a connection to the RDBMS data source in the Data Connections screen.

Data Element



2. Click Edit/Create new data element for an RDBMS structure .




6. Select the Data Connection to the server that holds the required data table.

7. Click Create. The data element is added to the list.

8. Select the new Data Element, then click Next.

Data Connection

To set the data table in the data source:

1. Click and select the required Data Table.

2. Optional: Enter a Data Filter to return a subset of data from the table.

3. Click Next.

92


Fields

Select the fields from the data table, and specify the key fields used to link data.

To set the fields:

1. Click Add to load the Add Fields form.

2. Select the Field Name for the required columns, then click Add.



5. Select the Key Field in the list.

Set a new caption for the table fields (optional).

To change a caption:

1. Click and enter a new Caption in the field provided.

2. Click to confirm the new caption.

Preview


Read the data table to preview the loading time of fields for each record generated in the application:





3. Click Preview.




93


Manage Nakisa ABAP Add-On Parameters

The Nakisa ABAP Add-On serves as the integration layer between Nakisa and the SAP server. It provides thecustom function modules that extract organizational structure and data from the SAP system.

The predefined keywords are customized by the administrator to define how the system works. For example,the administrator enters the Current Plan Version used in the application.

Update the keyword parameters used in the Nakisa ABAP Add-On.

To change a keyword:


2. Click Manage Nakisa ABAP Add-On Parameters.

3. Click to activate the required keyword.

4. Enter a new Value.

5. Optional: Modify the Description.


7. Click Finish.

8. Click Submit.

Refer to the Nakisa OTFSchema Reference Guide for the list of keywords and default values implemented inthe application.

94


Build ManagementExport a Build

The resources and settings used by the application are localized in a specific build under the .system/Admin_Config/ directory. A typical build contains:

Authentication and security settings Data connections XML templates that store module, org chart, views, listing, and detail configurations XSL files that transform and render XML documents Scripts Images Enabled and disabled add-ons and loading precedence settings

You can export a build as a ZIP file that can be used as a backup, or as a means to transfer customizations toanother Nakisa application server.

To export a build:


2. Modify the build, if necessary.

3. Click Save & Publish current build in the menu bar.

The Export Changes, Save As, Save, and Publish actions load in the top frame of the NakisaAdminConsole.

4. Click Export Changes. The Choose Build Name... dialog box appears.

5. Enter a name for the build in the field provided.

6. Click Export Build. The files associated with the build are saved in a ZIP file in the add-ons/inboxdirectory on the Nakisa application server. This file contains the set of all changes to the currently loadedbuild, including the selected user authentication method, preferences, and other Nakisa AdminConsolesettings that are not part of AppResources . A download link appears allowing you to save the ZIP file to alocation of your choosing.

95


Import a Build

You can import a build as a ZIP file that was created as a backup, or to transfer customizations from anotherNakisa application server.

Note: A build can only be imported if the source build on which it is based is present in the target environment.For example, if you used the “SuccessionPlanning” configuration to export a ZIP file, then “SuccessionPlanning”must be present in the target system.

To import a build:

1. Access the Nakisa AdminConsole.

2. Click Browse... and locate the ZIP file corresponding to the build you wish to import.

3. Click Import Build..., then enter a unique name for the build you are about to import.

Note: This allows you to import a build from the same ZIP file more than once.

4. Click Import. The imported build appears in the list of available builds.

A new folder is created on the application server for this imported build (all previously installed buildsremain untouched).

5. Select the imported build, then click Load.

96


Upload Content

Use the Upload Content feature to update configurations files and import user-created print and exporttemplates for the current build. The Upload Content feature allows you to quickly make permanent changes tothe build that will be included if the build is exported. To add features that can be enabled and disabled, and totake loading precedence into consideration, use the Add-On Manager instead.

WARNING: The Upload Content feature should only be used by advanced administrators.

Updated configuration files must be in a ZIP file that follows the same folder structure found in the /Admin_Config/[build workspace] directory. For example, to upload thePositionView_Standard.xml file, it must be placed in a /AppResources/viewsconfigurationdirectory within the ZIP file.

WARNING: Because Nakisa applications are highly customizable, the folder structure of the ZIP file is notvalidated upon import. Create a back-up of your build and ensure the folder structure in the ZIP file is correctbefore continuing, to avoid unexpected results. Imported files are copied to the [application directory/.system/Admin_Config/[buildworkspace]/.delta directory, and are enabled once the build is published.

If you wish to import a complete build, use the Import Build feature instead.

To upload files into the current build:


2. In the top-right area of the interface, click Upload Content. If the button is not visible, click the Save &Publish current build link in the menu panel.

3. Click Browse, then locate the ZIP file to upload.

4. Click Upload, then click Logout.

5. Log back into the Nakisa AdminConsole, then load the build.

6. Click Publish to enable the changes in the User Console.

97


Reset the Build

When builds are published, all files contained in the build workspace folder are copied to the main applicationdirectory. Importing many customizations into a build and saving or importing many builds can cause theapplication directory to become filled with many extra files. If one of the builds introduced an error, then it maybecome impossible to load and publish other functioning builds.

Resetting the build will clean up the root application folder. Note that the root folder is always cleaned up thesame way regardless of which build was reset. All of the files and folders are deleted except for the following:

[application directory]/.system

[application directory]/Log

[application directory]/WEB-INF

[application directory]/rfc-logs

Note: The rfc-logs folder is only present if the RFC Trace feature has been enabled in one of the builds.

Once the application completes the cleanup, it logs out the administrator, reloads the root directory with filesand folders resembling a new build that has just been loaded but not yet published, and redirects theadministrator to the login page. The build needs to be published for the User Console to become availableagain.

Note: Resetting a build preserves all changes, customizations, add-ons, and saved builds, which are found inthe [application directory]/.system directory.

To reset a build:


2. If the Upload Content, Export Changes, Save As, and Publish buttons are not displayed in the top-rightcorner, click Save & Publish current build in the menu panel.

3. Nakisa recommends saving the build before resetting it.

4. Click Reset Build > Log Off and Reset Build.

5. Log back into the Nakisa AdminConsole, and load the required build.

6. In the top-right corner, click Publish.

98


Delete a Build

After saving and publishing a build, it appears in the build selection frame when accessing the NakisaAdminConsole. Any custom build appearing in this frame can be deleted. Deleting a build completely removesits build workspace folder.

Note: Default builds shipped with the application cannot be deleted.

To delete a build:

1. Open the administrator URL. The build selection frame is displayed.

2. Select a custom build, which is identified by the phrase "(user created)" after the Build Name.

3. Click Delete under the Action column.

99


Add-On ManagerAdd-On Manager Overview

The Nakisa AdminConsole Add-On Manager allows you to do the following:

Export and transfer changes to administrator builds, or specific configurations, from the test env ironment tothe operational system

Load and test add-on enhancements and customizations provided by Nakisa before publishing live Select how add-ons load in the application so client files always get precedence Disable add-ons that produce unexpected results from loading in the client application Disable and remove add-ons that are no longer required

Note: Nakisa "add-ons" are a mechanism for exchanging discrete application components, primarily used in thedistribution of enhancements, hot fixes, or service packs.

The following table provides the directory structure for the Add-On Manager.

Directory Use

.system/add-ons Stores the software extensions (add-on directories andapplication files) used by the administrator build.

.system/add-ons/inbox Stores the add-on archive files to load in the Add-On Manager.

It is recommended to save all add-on archive files in the .system/add-ons/inbox directory.

100


Activate an Add-On

The Add-On Manager is used to load and activate an add-on in the build. This process involves the followingsteps:

Load an add-on fileSet the loading precedence between enabled add-onsActivate the add-on configurations in the build

Once an add-on is activated, you can publish the build to enable the settings in the live client. Refer to the Submit, Save, Save As, and Publish topic for more information about publishing a build.

Note: There is a special add-on called add-on-customizations that appears in the Add-On Manager bydefault. This is reserved for use by Nakisa Professional Services.

Load an Add-On File

Load and add-on stored in the .system/add-ons/inbox directory to the Add-On Manager.

To load from the inbox:


2. Click Application-wide Settings > Add-On Manager.

3. Select the required add-on from the Load from Inbox drop-down list.

4. Click Load from Inbox. The add-on is moved to the Loading Precedence list.

Use the Browse for File option to load an add-on that is stored in a directory on the network.

To upload an add-on from a network directory :

1. Click Browse in the Browse for File section.

2. Navigate to the directory where the add-on files are stored.

3. Select the required add-on file and click Open.

4. Click Load. The add-on is moved to the Loading Precedence list.

Set the Loading Precedence

Configure the precedence between add-ons once an add-on is loaded in the Add-On Manager. This ensures allimplicit and forward dependencies are found for a needed function when the application loads.

Note that client files and manual settings submitted in the Nakisa AdminConsole wizards after activating theadd-on always get precedence.

To set precedence:

1. Select the required add-on from the Loading Precedence list.

2. Click Move Up or Move Down to set the required order.

101


Activate the Add-On

Activate the add-on configurations in the build.

To activate the add-on:

1. Click Submit in the Add-On Manager once the add-ons are set to load in the required order.

2. Log out of the Nakisa AdminConsole to activate the add-on in the build.

The add-on is extracted to a new directory under .system/add-ons .

3. Log back in to the Nakisa AdminConsole.

Publish

Publish the build to enable the add-on settings in the live client.

To publish the add-on:

1. Click the Save & Publish current build link in the top frame of the Nakisa AdminConsole.

2. Click Publish. All settings stored in the add-on are enabled in the application.

102


Create an Instructions File

An instructions file named addOnInstructions.txt is typically included with the add-ons provided byNakisa.

The file is saved in the add-on archive file, and is read by the Add-On Manager to quickly perform these whenthe add-on loads:

Set the precedence between the new add-on and an existing add-on Disable old add-ons in the application

The following table lists typical commands entered in the instructions file.

Command Description

after [add_on_path] Sets the loading precedence when a new add-on is dependenton another add-on in order to load.

This command is entered only once in the instructions file.

disable [add_on_path] Moves an existing add-on to the disabled list.

This command is optional, and may be included in theinstructions file more than once, as required.

Use these commands to create an instructions file for add-ons created in the Add-On Manager.

To create an instructions file:

1. Open a text editor, and type the required commands in the file.

2. Save the text file as addOnInstructions.txt.

3. Export the build as an add-on in the Nakisa AdminConsole, then save the text file to the add-on archive filecreated by the tool.

103


Enable an Inactive Add-On

Enable an inactive add-on in the build when required.

To enable an add-on:



3. Select the required add-on from the Disabled Add-Ons list.

4. Click Enable Add-On. The add-on is moved to the Loading Precedence list.

5. Set the required Loading Precedence.

6. Click Submit and log out of the Nakisa AdminConsole.

7. Log back in to the console. The add-on is enabled in the build.

104


Disable an Add-On

Disable an add-on from loading in the operational system in the following scenarios:

The add-on configuration produces unexpected results in the client The add-on configuration is out-of-date and no longer required

To disable an add-on:




4. Click Disable Add-On. The add-on is moved to the Disabled Add-Ons list.

5. Click Submit and log out of the Nakisa AdminConsole.

Follow these steps to ensure the enabled add-on is disabled from loading in the application.

To complete the disable action:

1. Log in to the Nakisa AdminConsole and click the Save & Publish current build link in the menu panel.


2. Click Publish. The add-on is disabled in the application.

105


Remove an Add-On

Remove an add-on that is no longer required. The archive file remains in the .system/add-ons/inboxdirectory once the add-on is removed; delete the file to remove it from the application completely.

To remove an add-on:




4. Click Disable Add-On.

5. Select the add-on from the Disabled Add-Ons list.

6. Click Remove Add-On. The add-on is removed from the .system/add-ons directory.

7. Click Submit. and log out of the Nakisa AdminConsole.

Follow these steps to ensure the disabled add-on is removed from the application.

To complete the remove action:

1. Log in to the Nakisa AdminConsole and click the Save & Publish current build link in the menu panel.


2. Click Publish. The add-on is removed from the application.

106


Export a Configuration

Export Configurations provides a tree view of the directory structure and files for each configuration stored inthe .system/Admin_Config/[build]/AppResources/ directory.

WARNING: The Upload Content feature should only be used by advanced administrators.

Tip: Use the Export Configurations feature to export a specific AppResources configuration as an add-on. If youwish to export an entire build, use the Export Changes feature instead.

The following occurs during the export: The add-on archive file that contains the configuration is created. The archive is saved in the [application directory].system/add-ons/inbox directory. The file is named add-on-[name].zip . A download link is created. The add-on is listed in the Add-On Manager upload list.

Tip: The exported configuration files can also be imported into any build using the Upload Content feature if thetop-level add-on folder is removed from the zip. For example, if you named your exported configuration files export in the Nakisa AdminConsole, the top-level add-on folder name is add-on-export . This folder mustbe removed and the contents of the folder re-zipped.

To export any configuration in the tree view:

1. Click Application-wide Settings > Export Configurations.

2. Expand the tree structure.

3. Select the required configuration files.

Tip: Select a top-level check box to select all files that belong to a specific configuration.

4. Enter an Add-On Name.

5. Click Export as Add-On.

To find and export an existing configuration:

1. Enter a partial Name followed by the wildcard character '*'. For example, enter connection* to get the DataConnection Configuration.

2. Click Search. The configuration structure that matches the search loads in the tree.

3. Expand the tree structure.

4. Select the required directories and configuration files.


6. Click Export as Add-On.

7. Click Clear to show the entire tree structure.

107


Immediately export a configuration set up in the current session.

To export the current session:

1. Update any configuration in the Nakisa AdminConsole. Configure the data connection in the org chart andlistings, for example.

2. Click Submit to temporarily store the configuration in the session memory.

3. Click Application-wide Settings > Export Configurations.

The changed configuration files are highlighted, and the structure is automatically selected in the tree. Theassociated AppResources setting appears at the top of the list when a change is made in the currentsession.


5. Click Export as Add-On. A message indicates when the export is successful.

To download the add-on after the export:

1. Click the Download link provided.

2. Save the archive file to the required directory.

108


Org Charts and HierarchiesOrg Chart Overview

Organization charts—or org charts—graphically show the hierarchical authority, roles and responsibilities, andfunctional relationships in an organization.

The Nakisa AdminConsole is used to set up the linked hierarchies and graphical controls of the org chart andrecord details for each organizational object.

The process involves the following steps:

Enable the org chart.Connect to the SAP data source.Add fields from the data source tables, and set the key field of each object.Create an organizational hierarchy using key fields.Link a child hierarchy to the parent hierarchy.Design the details panel layout.Design the profile window layout.Design the box views for the org chart.Finish and submit the changes.

Org charts are graphical representations of the self-referencing relationship between objects at the samehierarchical level, and the relationship between superior and subordinate objects.

The following table lists the org charts in each Nakisa SuccessionPlanning build:

Build Org Chart

TalentFramework Job Architecture Hierarchy shows the functional and job family structureof the organization.

Competencies shows the competencies assigned to each functionallevel, as well as those inherited from parent functional levels.

SuccessionPlanning Organizational Structure shows the org unit (department) hierarchy andits reporting positions.

Position Hierarchy shows the positions and successors in theorganization plan.

Both of these charts are available in the Employee and Position modules.

The My Work Area module includes both of these charts but they arenamed My Org Units and My Positions respectively, and only displayrecords in the logged-in user's area of responsibility.

Manager My Reports shows the org unit (department) hierarchy and its reportingpositions in the logged-in user's area of responsibility.

109


Enable/Disable

This procedure enables an organization chart in the end-user interface.

The following occurs when the build is saved and published:

The org chart that represents the hierarchy is enabled in the application. The caption for the org chart appears under Visualize in the appropriate application menu. The caption appears as the tab name in the org chart panel.

To enable an org chart:


2. Click the required module to load it in the interface.

The Visualize section displays the hierarchical structure of objects for each organization chart.

3. Click the top-level organizational object. Enable/Disable loads by default.

4. Select Yes to enable the org chart, or No to disable it.

5. Enter a new Caption using company-specific terms, or leave the default.


7. Click Next.

The next step is to set the Data Connection.

110


Data Connection

A connection to the main SAP application server host for organization data is configured in the Data Connectionscreen. Information about the SAP connection is provided in the Connection String topic.

Establish a connection to the SAP source system:

1. Click the required organizational object under Visualize.

2. Click Data Connection.

3. Click to activate the Connection String field.

4. Enter the string Value to the SAP data source.

5. Click Test Connection to verify the connection string.

6. Click to complete the connection.

The Data Table Value of the data element is pre-configured for the selected organizational object.

7. Click Next.

The following optional task is available for the data connection.

Add a data filter:

1. Click to activate the Data Filter field.

2. Enter a filter to query the data table. For example, Type='O' is entered for org units to return that subsetof data to the application.

3. Click to complete the filter.

The next step is to set up the org chart Fields.

111


Fields

Prerequisite: Establish a data connection to the SAP source system.

Add fields from the SAP data source, and set the key field(s) for an organizational object.

To set the fields:


2. Click Fields.


4. Select the required fields, then click Add.



7. Select the Key Field that uniquely identifies the record type.

The key fields are used to:

Create an object hierarchy Link hierarchies together

A typical example is the org unit ID field, and the position Object_ID and ParentNo fields.

8. Click Next.

The following optional task is available for the data source fields.

To modify a field caption:


2. Enter a new caption for the field.

3. Click to accept the caption.

The next step is to set up the Hierarchies.

112


Hierarchies

Prerequisite: Add fields from the SAP data source, and set the key field(s) for each organizational object.

The following procedure uses an org unit (parent hierarchy) to position (child hierarchy) org chart as a sampleconfiguration. Each hierarchy is configured separately, then linked using a common field.

The first step is to set up the parent hierarchy, which is the self-referencing relationship between org units at thesame hierarchical level.

This table lists the org unit fields selected from the data source:

ID ParentID HasChildren Name

1 NULL TRUE Finance andAdministration

2 1 TRUE Accounts

3 1 TRUE Treasury

4 4 FALSE CollectionsManagement

The ID is set as the key field.

To set up the hierarchy:

1. In the menu panel, click My Work Area, Employee, or Position, then select the required parent hierarchyunder Visualize.

2. Click General Settings.

3. Enter the Hierarchy ID Field for the org unit. This field holds the ID of each record in the org unit table.

4. Enter the Hierarchy Parent Field. This field identifies the ParentID field in the org unit table. The recordis the top-level parent (root) if the ParentID is 0 (or NULL).

The Element ID Field uniquely identifies the record if IDs are shared among objects; this does not occur inSAP.

5. Enter the Child Exists Filter for child nodes.

The filter identifies the field in the org unit table that tells a record if it has children, for example: HasChildren = 'TRUE' . A data call is sent to the server if this option is left blank.

6. Select the Org chart root value source. This defines where the application retrieves the root record from.Two options are available:

Org Chart Root: Retrieves the record specified in the next step from the hierarchy data element. User Record: Retrieves the record specified in the next step from the employee data element.

Note: The Static option is used for advanced customizations. Contact your implementation partner formore information.

7. Do one of the following to define the org chart root:

113


If Org Chart Root was selected in the previous step, enter the Org chart root value ID. If User Record was selected in the previous step, select the field containing the ID of the required

organizational object in the employee data element from the User record field drop-down list. Forexample, if you wish to root the org chart at the org unit of the logged-in user, select the field containingthe org unit ID.

8. Set Page limits to determine number of children that appear under a parent when the branches andgroups in the structure are expanded.

9. Click and select the Parent Description Field. This value appears when starting the org chart one levelabove the current node.

10.Enter a Dotted Relationship Filter to identify the field and value that indicate when a record has adotted-line relationship.

11.Select the Default Style for the org chart.

12.Click Finish, then click Submit.

The next step is to set up the child hierarchy of positions used for the direct interaction between objects.

This table lists the position fields selected from the data source:

Object_ID ParentNo HasChildren Name

1 1 TRUE Director Finance andAdministration

2 2 TRUE Credit Manager

3 2 FALSE Credit Assistant

4 2 FALSE Credit Specialist

5 3 FALSE Assistant Finance

6 3 TRUE Functional SpecialistFinance

7 3 TRUE Secretary: Finances

8 4 TRUE Manager: Collections

The Object_ID and ParentNo are set as the key fields.

To set up the hierarchy:

1. In the menu panel, select the required child hierarchy under Visualize.


3. Enter the Hierarchy ID Field for the position. This field holds the Object_ID of each record in the positiontable.

114


Subordinate positions are grouped by the ParentNo field, and then joined to the parent hierarchy using the orgunit ID field. The link between hierarchies is established using a FilterData query.

To link the hierarchies:

1. Go to the Link Information section.

The Linked From field indicates the parent hierarchy name, and is unavailable for editing.

2. Enter the Linked Using field of the parent hierarchy. Note that this field must have the same value as theHierarchy ID Field entered for the org unit.

3. Enter ParentNo in the Grouped by field. The ParentNo stores the org unit ID of each position, as outlinedin the position table.

4. Select FilterData as the Link Operation.

FilterData queries the ParentNo field of the position to find the link between hierarchies.

The ParentChild link operation is specific to LDAP tree hierarchies, which does not occur in SAP.

5. Enter a Static Filter to reduce the records returned by the server.

6. Enter the Group Child Exists Filter for grouped children.


The org chart renders this structure as follows:

The next step is to set up Sub Category Groups.

115


Sub Category Groups

Sub categories group employees in a single org chart box based on specific job functions.

To add a sub category group:

1. Go to the Subcategory Group Settings section.

2. Click Add New.

3. Enter the SubCategory Name.

4. Enter a SubCategory Filter for the grouped records.

5. Select the Default Display.

The following display options are available:

Group displays all employees in the group in the same org chart box. Show Group Members displays employees in the group in individual org chart boxes. Hide Group Members hides the org chart boxes for employees in the group.

6. Enter the Caption for the group. This caption appears in the org chart box if Group is selected in step 5.

7. Click Update to create the new group.

The next step is to Activate Menu Links for the org chart.

116


Activate Menu Links

This procedure activates the required menu links for subordinate objects in a hierarchy. The link is enabled inthe org chart box menu and Actions menu in the details panel.

To activate a link:



3. Go to the Link Configuration section.

The items in this section depend on the selected Visualize object. The link configuration may be empty.

4. Select Profile. This activates the link that opens the Profile window.

5. Click Next.

The next step is to set up the Selected Items Fields.

117


Selected Items Fields

Records are added to the Selected Items panel when users flag nodes in the org chart. Each record isrepresented by a box in the panel. This procedure sets up the fields that appear in the boxes and enablese-mail.

To set selected items fields:



3. Click and select the Item Description Field from the drop-down list (the second description field isoptional).

Typically, the Name is used.

4. Click and select the Email Field. This activates Send E-mail in the Selected Items panel.

5. Click Next.

The next step is to set up the Sort Fields.

118


Sort Fields

This procedure sets the fields the user can select in the org chart Settings dialog box to sort the org chartdiagram.

Note: Some fields (Boolean, comment, binary, ntext) cannot be used for sorting an org chart. Errors occur ifthese field types are selected.

To set the org chart sort fields:


2. Click Sort Fields.




6. Click Done when all the required fields are added.

7. Select the Order number from the drop-down list for the required field. The field order is automaticallyupdated.

The field set to '1' is the org chart default.

8. Click Next.

The next step is to set up the Details Panel.

119


Profile Window

Nakisa SuccessionPlanning has a pre-configured profile window for each organizational object in theapplication.

The details profile window uses the details panel layout as a model, and has the same interface controlsavailable in the Details Designer. The controls normally displayed inside tabs are arranged into "flat" sectionson the page.

To set up the profile:



3. Click the required organizational object under Visualize, or the required listing under Work with.

4. Click Profile.

5. Select Flatten Details to automatically copy the details panel layout into flat sections.

6. Alternatively, select Configure Profile to load the design schematic for the profile.

7. Scroll down the screen to find the placeholder position, then add new interface controls and sections asrequired.

8. Click Copy from Details Designer at any time to reset the layout and start over.

120


Listings and SearchesListing Overview

A listing is a real-time search capability used to find organization information contained in the company humanresource data repository. Listings are used to generate advanced searches based on keywords and priorities,and to limit searches by specific organizational units, positions, employee types, talent groups, or a level in theorganization structure.

The Nakisa AdminConsole is used to set up the fields required for each listing, directory behavior, and thesearch and advanced search forms.

121


Enable/Disable

This procedure enables a listing in the end-user interface.


The listing is enabled in the application. The caption for the listing appears under Work with in the appropriate application menu. The caption appears as the tab name in the listing panel.

To enable a listing:



The Work With section displays the listings available for activation.

3. Click the required listing. Enable/Disable loads by default.

4. Select Yes to enable the listing, or No to disable it.



7. Click Next.


122


Data Connection

A connection to the main data source for organization data is configured in the Data Connection screen.

Establish a connection to the SAP data source:


2. Click the required listing under Work with.







8. Click Next.


Add a data filter:


2. Enter a filter to query the data table. For example, Type='O' is entered for org units to return that subsetof data to the application.


The next step is to set up the listing Fields.

123


Fields

This procedure updates the fields that are used to set up the listings.

To set the fields:



3. Click Fields.



Note: Do not select fields that begin with MC_ (for example: MC_STEXT). These fields are typicallyduplicates that contain the string in upper-case characters and may cause unexpected results whenperforming a search in the User Console. Use the field of the same name without the prefix (for example: STEXT).




A typical example is the org unit ID field.

9. Click Next.






The next step is to set up Directory Filter.

124


Directory Filter

This procedure sets up a filter to process the records that are displayed when users access a listing.

To filter a directory:

1. Click the required listing under Listings.


3. Select Start Directory Empty.

Users must perform a search in order to populate the list when this check box is selected. An emptydirectory prevents unnecessary load on the data server if the listing contains a large number of records.

4. Enter a Directory Filter to limit a search to a specific type of record (optional).

5. Enter the Records per page . This sets the default number of records returned on a page when the useraccesses a listing, or performs a search.

6. Enter the Export Limit (between 1 and 10000). This restricts the number of records users can export fromthe application.

The next step is to set up the Selected Items Fields.

125


Selected Items Fields

Records are added to the Selected Items panel when users flag items in a results list. This procedure sets upthe fields that appear in the selected items boxes and enables e-mail.

To set selected items fields:




4. Go to the Selected Items Settings section.

5. Click and select the Item Description Field from the drop-down list (the second description field isoptional).

Typically, the Name field is used.

6. Click and select the Email Field. This activates Send E-mail in the Selected Items panel.

The next step is to set up the Listing Columns.

126


Listing Columns

A listing contains an array of items that is generated in response to a user-defined search.

This procedure sets the display fields for columns in a listing.

To set the listing columns:


2. Click the directory name under Work with.

3. Click Display Fields.



Note: Because the listings in Talent Framework and Succession Planning use TREX, you must only addfields that are also part of the set of fields in TREX, otherwise these fields will not be properly displayed inthe User Console and other features that use listing information may no longer work. If you require a fieldthat is not available, contact your TREX specialist to have it added. For more detailed information about thefeatures that use TREX, refer to the Feature Checklist.



8. Select the Order number for the required field from the drop-down list. The field order is automaticallyupdated.

The field set to ‘1’ is the first column in the listing grid.

Configure the columns to be sorted by the user.

To enable sorting:

1. Click to activate the required rows.

2. Select Sortable.

3. Select the Sort Order: Ascending, Descending, or Both.



The next step is to set up the basic Search Form.

127


Search Form

This procedure sets the field values that appear in the "Look for" drop-down list in the listing search form, andthe operator and validation types for each value.

To add fields to the search form:



3. Click Search Fields.



Note: Because the listings in Talent Framework and Succession Planning use TREX, you must only addfields that are also part of the set of fields in TREX, otherwise searches will not return proper results in theUser Console and other features that use listing information may no longer work. If you require a field thatis not available, contact your TREX specialist to have it added. For more detailed information about thefeatures that use TREX, refer to the Feature Checklist.




Set the operator and validation type for each value.

1. Click to activate the required search field value.

2. Select the Operator Type, then the Field Validation Type.


4. Click Next.

The next step is to set up the Advanced Search Form.

128


Advanced Search Form

This procedure sets up the advanced search form for a listing. The advanced search form loads when the userclicks the Advanced Search button in a listing. The user selects multiple fields and values to return morethorough search results. Search filters are also available to specify multiple values for the same search field.

To add fields to the search form:



3. Click Advance Search Fields.

4. Click Copy From Search Fields . The same fields, operators, and validations configured for the basicsearch form are automatically added.






10.Click Next.

The next step is to set up the Details Panel for an object.

129


Details DesignerDetails Designer Overview

Nakisa SuccessionPlanning has a pre-configured details panel for each organizational and functional object inthe application:

Org unit Position Employee Functional area Job family Job

The panel displays extended information about a record, and includes collapsible sections and tabs thatorganize information according to a specific area of interest.

The Nakisa AdminConsole Details Designer provides a design schematic of the details panel graphical-userinterface (GUI). Use this schematic to set up the following interface controls in the details panel:

Details title (tab heading) Table layout Panels Tabs Sections and fields Style properties

130


Access the Details Designer

The Details Designer is accessed from the Listing or Org Chart configuration.

To load the Details Designer:



3. Click the required organizational object under Visualize, or the required listing under Work with.

4. Click Details Designer.

131


Create New Detail

Create a new detail link to add fields from a different data element to the details panel.

To add a new data element:

1. Access the Details Designer for the required object.

2. Click Create new detail in the Design Details section.

3. Enter the Detail Name.

4. Select an existing Detail in the data source to link to the data element.

5. Select the required Data Element created in the Data Center.

6. Select the Table that contains the fields required for the new section. The primary table set in the DataCenter is selected by default.

Map the fields to link the tables together. The key fields in the Source and Destination are selected by defaultin the Edit Mappings section.

To map the required fields:

1. Click >> to map the key fields.

2. Optional: select new fields to map the source and destination data.

3. Click Apply.

The detail is available for selection when a new section is added to the design schematic.

132


Details Title

The Details Title is the tab heading for the details panel.

The tab heading typically uses one data field to display the title of the record, for example: the org unit Title.

To set the tab heading:

1. Access the Details Designer for the required object.

2. Click Edit to load the Edit Fields dialog box.

3. Select the required field for the tab. It is recommended to use one or two fields for the tab.

4. Click Apply.

133


Table Layout

A table organizes the layout of the interface controls in the details panel.

Dotted lines show the boundaries of the table and its nested tables.

The lines form a guideline to aid in the design process, and are invisible to the end-user.

The following controls can be added to a table:

Nested row and column tables Panels Tabs Sections (fields)

This procedure adds the table in the example above. A new placeholder is provided each time a control isadded to the layout.

Create a table that has one column and many rows to arrange fields vertically in a section.

To create a table with two rows:

1. Click and select Row Table from the menu. The table is added to the layout.

2. Click inside the new table, then add a control to create the first row.

3. Click below the first row, and add a control the create the second row.

134


Create a table that has one row and many columns to arrange fields horizontally in a section.

To create a table with two columns:

1. Click and select Column Table from the menu. The table is added to the layout.

2. Click inside the new table, then add a control to create the left column.

3. Click next to the column, then add a control to create the right column.

Nest the row and column tables to create a more complex layout.

135


Panels

A panel creates a title bar in the layout, and is used to frame specific details inside a named section.

This procedure adds the panel in the example above. A new placeholder is provided each time a control isadded to the layout.

To add a panel:

1. Click and select Panel from the menu.

2. Click to load the Change Panel Caption dialog box.

3. Enter the English caption in the field provided.

4. Repeat the process for the additional languages, if required.

5. Click Apply. The panel is added to the layout.

Move the tables (created in the Table Layout topic) over to the placeholder position inside the panel.

To move the table:

1. Click and hold the title bar of the main row table.

2. Drag the table to the placeholder.

3. Release the mouse button when the Panel is highlighted.

The row table and all nested controls are moved to the new position.

136


Tabs

Create a series of tabs inside the panel, and use the new layout to group sets of information about a recordinside each tab.

This procedure adds the tabs in the example above. A new placeholder is provided each time a control isadded to the layout.

To add tabs:

1. Click and select Tabs from the menu. One tab is added to the layout.

2. Click to load the Change Tab Caption dialog box.

3. Enter the language captions for the tab in the fields provided. English is the application default.

4. Click Apply.

5. Click Add Tab, and add the next tab to the layout.

137


Sections

A section holds the fields used by the application, and arranges them in specific formats in the details panellayout.

The application gathers these fields from the following sources:

Data elements specified for the current object Data elements specified for the linked objects in the hierarchy Data elements created in the Data Center, which are joined to the current object Pre-configured XSL sections that read data from the application configuration files

The fields are rendered in the details panel using these section types:

Section Displays

Field ValueField/Value (Multiple)

A field name and its value.

NameName (Multiple)

A comma-separated name.

Listing Field values in a table with column headings.

Image An employee portrait.

Mouse over any section in the Details Designer layout to view the data source:

138


Add sections to a table (created in the Table Layout topic) to display specific fields from the data source in thedetails panel.

This procedure adds the sections in the example above. A new placeholder is provided each time a controlis added to the layout.

To create the layout:

1. Add a Row Table, then nest a Column Table to the first row.

2. Click in the left column, then select Section > Field/Value Section (Multiple) > Data Source Table.

The data source tables are identified as follows:

Current object Linked object in the hierarchy Connection established in the Data Center

3. Select the ID, Title, and Abbreviation fields in the Edit Fields dialog box. The fields listed are drawn fromthe selected data source table.

4. Click Apply. The section is added to the left column.

5. Click the arrows to arrange the fields in the required order.

6. Add a Row Table to the right column.

7. Add an Image Section that contains the Picture_Url field to the top row.

8. Add a Name Section that contains the Lastname and Firstname fields to the bottom row.

139


Move Controls

Move controls to a different area in the details panel layout.

This example moves a section to the right column in a table.

To move the section:

1. Click and hold the top bar of the Field Value Section.

2. Drag the section to the placeholder position on the right.

3. Release the mouse button when the Column Table is highlighted.

The section is moved to the right column position.

140


Remove Controls

These steps remove interface controls from the details panel layout:

Click Edit in a section, and clear the required check box to remove a field. Click Delete to remove a control, and all nested controls are removed. Click to remove a tab, and all nested controls in the tab are removed.

141


Style Properties

Customize the appearance of panels and tables with Cascading Style Sheet (CSS) markup language.

To set style properties:

1. Locate the required panel or table.

2. Click Properties in the top bar. The Properties dialog box appears.

3. Enter CSS declarations for the Style, for example: color:orange; text-align:center; .

4. Click Apply.

142


Views DesignerViews Designer Overview

Nakisa SuccessionPlanning has pre-configured org chart views for each organizational and functional object inthe application:

Org unit Position Employee Functional area Job family Job

The org chart box displays specific information about a record, and includes regular and condensed styles thatarrange the diagrams in different formats.

The Nakisa AdminConsole Views Designer provides a design schematic of each org chart box view. Use thisschematic to set up the following interface controls in the org chart box:

View caption Table layout Panels Sections and fields Icons (image mapping) Box color and size

The following tasks are performed in the Views Designer:

Enable the views available for the organizational object Set the default view for the org chart View hidden sections defined by Nakisa

143


Access the Views Designer

The Views Designer is accessed from the Org Chart configuration.

To access the Views Designer:




4. Click Views.

144


Create New Detail

Create a new detail link to add fields from a different data element to the org chart box.

To add a new data element:

1. Access the Views Designer for the required object.

2. Click Create new detail in the Design Details section.

3. Enter the Detail Name.

4. Select an existing Detail in the data source to link to the data element.

5. Select the required Data Element created in the Data Center.

6. Select the Table that contains the fields required for the new section. The primary table set in the DataCenter is selected by default.

Map the fields to link the tables together. The key fields in the Source and Destination are selected by defaultin the Edit Mappings section.

To map the required fields:

1. Click >> to map the key fields.

2. Optional: select new fields to map the source and destination data.

3. Click Apply.

The detail is available for selection when a new section is added to the design schematic.

145


Enable/Disable Views

This procedure enables a view for the organizational object in the org chart.

To enable a view:

1. Go to the Enable/Disable Views section.

2. Select the check box next to each view to enable for the object.

3. Clear the check box to disable a view from appearing in the org chart.

146


Default View

The org chart boxes display the default view when users access the org chart.

To set the default view:

1. Go to the Enable/Disable Views section.

2. Select the radio button next to the default view for the object.

147


Preview Mode

Generate a view preview to see the org chart box as it appears in the application.

To preview a view:

1. Select the required view in the Modifying section.

2. Click in the Design Mode section. The design schematic switches to preview mode.

3. Enter the Record ID, or click to select the required record.

4. Click Go to preview the org chart box as it appears in the application.

5. Click to return to design mode.

148


Condensed Style

The Condensed style displays a left-hanging vertical chart, and condenses all boxes in the org chart. Thecondensed box style is modified in the Views Designer.

To access the condensed style:

1. Select the required view in the Modifying section. The box layout opens on the Regular Style tab.

2. Click the Condensed Style tab. The condensed org chart box loads in the designer.

149


View Caption

The View Caption is the name that appears in the org chart panel Views menu.

To set the caption:


2. Enter a new View Caption.

3. Click Apply.

150


Table Layout

A table organizes the layout of the interface controls in the org chart box.

Dotted lines show the boundaries of the table and its nested tables.

The lines form a guideline to aid in the design process, and are invisible to the end-user.

The following controls can be added to a table:

Nested row and column tables Panels Sections (fields)

This procedure adds the table in the example above. A new placeholder is provided each time a control isadded to the layout.

Create a table that has one column and many rows to arrange fields vertically in a section.

To create a table with two columns:

1. Click and select Column Table from the menu. The table is added to the layout.

2. Click inside the new table, then add a control to create the left column.

151


Create a table that has one row and many columns to arrange fields horizontally in a section.

To create a table with two rows:

1. Click next to the left column, and select Row Table from the menu. The table is added to the layout.

2. Click inside the new table, then add a control to create the first row.

3. Click below the first row, and add a control the create the second row.

Nest the row and column tables to create a more complex layout.

152


Panels

A panel creates a title bar in the org chart box, and is used to frame specific fields inside a named section.

This procedure adds the panel in the example above. A new placeholder is provided each time a control isadded to the layout.

To add a panel:

1. Click and select Panel from the menu. A panel is added to the layout.

2. Click to load the Change Panel Caption dialog box.

3. Enter the English caption in the field provided.

4. Repeat the process for the additional languages, if required.

5. Click Apply. The panel is added to the layout.

153


Sections

A section holds the fields used by the application, and arranges them in specific formats in the org chart box.

The application gathers these fields from the following sources:

Data elements specified for the current object Data elements specified for the linked objects in the hierarchy Data elements created in the Data Center, which are joined to the current object Pre-configured XSL sections that read data from the application configuration files

The fields are rendered in the org chart box using these section types:

Section Displays

Email An e-mail icon and the address with an active link.

Simple Value A field value.

Telephone A telephone number.

Picture An employee portrait.

Image Mapping Icons mapped to a specific value.

Name A comma-separated name formatted in bold.

Field Value A field name and its value.

Simple Caption A field value formatted in bold.

Mouse over any section in the Views Designer layout to view the data source:

154


Add sections to a table (created in the Table Layout topic) to display specific fields from the data source in theorg chart box.

This procedure adds the sections in the example above. A new placeholder is provided each time a controlis added to the layout.

To create the layout:

1. Add a Column Table.

2. Click in the left column, then select Section > Picture Section > Data Source Table.

The data source tables are identified as follows:

Current object Connection established in the Data Center

3. Select the Picture_Url field in the Edit Fields dialog box. The fields listed are drawn from the selected datasource table.

4. Click Apply. The section is added to the left column.

5. Add a Row Table to the right column.

6. Add a Simple Value Section that contains the Lastname and Firstname fields to the top row.

7. Click the arrows to arrange the fields in the required order.

8. Add a Simple Value Section that contains the Position ID field from a linked hierarchy to the bottom row.

155


Box Size

Increase the size of the org chart box once new sections and fields are added to the view.

To change the box dimensions:


2. Enter the org chart Box Height and Box Width in pixels.

3. Click to switch to preview mode, then verify that the new sections and fields added to the view displayproperly.


156


Box Color

Change the color of the org chart box.

To change the box color:


2. Enter an HTML color code in the Box Color field, or click to load the color box and select the requiredcolor.

The default color defined by the theme is used when Transparent is selected.

3. Click to switch to preview mode, then verify that the new color is correct.


157


Color Mapping

Color mapping changes the color of the org chart box according to a defined field and value.

Note: The org chart box shows the color defined by the application theme when mapping is not used.

Example

Org chart box with the field Country from Canada is red

To color map the field value:


2. Click to load the Edit Color Mapping dialog box.

3. Select the Country field from the drop-down list.

4. Click Add Mapping. The Map From and Map To fields load in the Edit Mapping section.

5. Enter Canada in the Map From field.

6. Enter RED (or the color code #FF0000) in the Map To field.

7. Repeat step 3 to step 7, and map additional field values to a color.

8. Click to delete a mapping when required.

9. Click Apply.

158


Image Mapping

Image mapping sections display icons in the org chart boxes according to specific field values.

Note: The icons that represent certain values—such as successor readiness and ranking—are mapped to thedefault application images. Contact your implementation partner to modify the image maps if custom scalevalues are required.

To map an icon to a field:


2. Add an Image Mapping section.

3. Click Edit. The Edit Fields dialog box appears.

4. Select the required field from the drop-down list.

5. Enter the Image width and Image height in pixels.

6. Click Add Mapping. A new row is added to the Edit Mappings list.

7. Enter the field value to map in the Map from field.

8. Enter the directory path to the image in the Map to field: images/[image_file_name] .

9. Repeat step 4 to step 8 to create additional maps, or click to delete a map.

10.Click Apply.

159


Hidden Sections

Nakisa adds hidden sections to the org chart views, which are available for edit in the Views Designer. A hiddensection uses the field value as a condition. It can be configured to show org chart boxes in different colorsdepending on the country value, for example.

To view a hidden section:


2. Click to load the Edit Hidden Sections view.

3. Edit the hidden section as required.


160


Move Controls

Move controls to a different area in the org chart box layout.

This example moves a section to the right column in a table.

To move the section:

1. Click and hold the top bar of the Field Value Section.

2. Drag the section to the placeholder position on the right.

3. Release the mouse button when the Column Table is highlighted.

The section is moved to the right column position.

161


Remove Controls

These steps remove interface controls from the org chart box:

Click Edit in a section, and clear the required check box to remove a field. Click Delete to remove a control, and all nested controls are removed.

162


AnalyticsAnalytics Overview

Talent management specialists (TMS) rely on detailed employee and position information to ensure the smoothand successful continuation of an organization. Analytics provide the quantitative and qualitative methodsneeded to visualize and analyze the human resource data.

The Analytics module in the User Console has five pages that include vital statistics about a workforce to helpa TMS track and evaluate succession planning goals:

Dashboard displays a summary of overall workforce performance in the organization, with links to thedetailed analytics in the subsequent pages.

Succession Planning provides in-depth information about the positions with and without succession plansin place.

Competency provides detailed employee proficiency ratings for the top four competency groups defined byan organization.

Holder/Successor provides statistics on the incumbents and successors to key positions in theorganization.

Performance/Potential provides an historical view of employee performance and potential values for thelast three assessment cycles.

The Nakisa AdminConsole is used to perform the following tasks:

Enable or disable Dashboard on entry Enable or disable the Analytics module pages Enable or disable the object counts and key performance indicator (KPI) dependencies Set alerts for target counts and demographics

163


Dashboard on Entry

This procedure sets the Dashboard as the entry page for the User Console.

To set up the Dashboard:


2. Click Application-wide Settings > Analytic Settings.

3. In the Enable/Disable Pages section, select Dashboard.

4. Select Dashboard on Entry.

5. Click Submit.

164


Succession Planning

The Succession Planning page in the User Console provides in-depth information about positions with andwithout successors. This section provides an example of the setup, and lists the object counts displayed in theUser Console.

The following tables describe the analytic counts in each section of the Succession Planning page.

The Overview section is a summary of the positions in the organization. The following counts are used in thissection:

Count Description

Total positions Calculates the total number of positions in the organization.

Key positions Calculates the number of positions that are defined as key.

In the Chart column, the application calculates the percentage of keypositions based on the total number of positions.

Total successors Calculates the total number of approved successors to key positions.

The Key positions with successors section provides details about positions and successors in theorganization.

The following counts are used in this section, and the application calculates the percentage of each total countbased on the total number of key positions:

Count Description

Key positions with successors Calculates the total number of key positions in the organization that havesuccession plans in place.

With 4 or more successors Calculates the total number of key positions with at least four approvedsuccessors.

With 3 successors Calculates the total number of key positions with three approvedsuccessors.

With 2 successors Calculates the total number of key positions with two approvedsuccessors.

With 1 successor Calculates the total number of key positions with one approvedsuccessor.

Without successors Calculates the total number of key positions without successors.

165


The Placement horizon section provides information about successor readiness. The following counts areused in this section:

Count Description

Non-key positions withsuccessors

Calculates the total number of positions that have successors, but no keyindicator.

Positions with successors Calculates the total number of positions (includes key and non-key) thathave successors.

Key position with successorsready now

Calculates the total number of key positions with approved successorsready to be placed immediately.

The application calculates the percentage of this count based on the totalnumber of key positions.

Key positions with successorreadiness

Provides a breakdown of key positions based on the successorreadiness.

Note: If a key position has multiple successors with different readinessvalues, that position is counted once for each value.

For example, if a key position has one successor ready immediately,three successors ready in the short term, and two successors ready in thelong term, then the position is counted once in the Immediately,Short-Term, and Long-Term columns.

The Overlap section provides information about an overlap in the placement horizon. The following counts areused in this section:

Count Description

Successors planned on morethan one position

Calculates the total number of employees who are approved successorsto more than one position.

The application calculates the percentage of this count based on the totalnumber of key positions

The Bench Strength section provides the successor bench strength calculation. The following counts are usedin this section:

Count Description

Positions with successors Calculates the total number of positions (includes key and non-key) thathave successors.

Successor bench strength(average)

This average is calculated using the following SAP remote function call(RFC):

HRTMC_GET_POSITION_ATTR hasATTRIBUTES/SUCCESSOR_BENCH_STRENGTH output

This RFC uses customer-defined values to generate the average benchstrength of key positions.

166


The Strong successors section provides information about the talent pool and successors with high potentialand performance scores. The following counts are used in this section:

Count Description

Successors who are part of aTalent Group

Calculates the total number of successors assigned to a talent group.

Successors who are HighPerformers

Calculates the total number of successors identified as high performers inthe employee record.

Successors who are HighPotentials

Calculates the total the number of successors identified as high potentialsin the employee record.

The Employee Overview section provides employee statistics and information about the talent pool. Thefollowing counts are used in this section:

Count Description

Employees Calculates the total number of employees.

Employees as FTE Calculates the total of part-time and full-time employees equated to thenumber of full-time positions.

Talents Calculates the total number of employees who are members of a talentgroup.

Talents per organizational unit Calculates the average number of talents per org unit.

To set up Succession Planning counts:



3. In the Enable/Disable Pages section, select Succession Planning.

4. Go to the Position and Staffing Analytics counts. All object counts in the list are enabled by default; clearthe check box to disable the required objects.

5. Set an alert to indicate when certain targets do not meet organizational goals.

The following counts provide an example of the setup:

Total number of key positions with successors: 50 Key positions with successors ready now: 4

6. Select Enable from the drop-down list next to Key positions with successors ready now.

7. Select a Condition operator, for example: < (less than).

8. Enter the required Value. For example, the organization indicates that 15% of key positions must havesuccessors ready to be placed immediately, so enter 15.

The application calculates the ratio: 4*100/50 = 8% An alert is shown to the user because successors ready immediately falls below 15%.

167


9. Click Submit.

168


Competency

The Competency page in the User Console provides details about the top-four competency groups chosen bythe client, for example: core, basic, leading, and technical competency groups. Each group displays the totalnumber of employees possessing the competencies in that group.

To set up Competency:



3. Select Competency in the Enabled/Disabled Pages section.

4. Go to the Competency section. All objects in the list are enabled by default; clear the check box to disablethe required objects.

5. Click Submit.

169


Holder/Successor

The Holder/Successor page in the User Console provides in-depth information about employees in theorganization. This section provides an example of the set up, and lists the object counts displayed to theend-user.

The following tables describe the analytic counts in each section of the Holder/Successor page.

The Incumbents/Successor of Key Positions sections provide information about employees according togender and nationality.

The following counts are used in these sections, and the application calculates the ratio of each gender count tothe total number of key positions with successors:

Count Description

Female incumbents of keypositions

Calculates the total number of females holding key positions.

Female successors of keypositions

Calculates the total number of females approved to succeed keypositions.

Male incumbents of keypositions

Calculates the total number of males holding key positions.

Male successors of keypositions

Calculates the total number of males approved to succeed key positions.

Incumbents of key positionsby Nationality

Calculates the number of incumbents with a particular citizenship.

Successors of key positionsby Nationality

Calculates the number of successors with a particular citizenship.

The Age section provides the average age of employees based on the date-of-birth field in the employeerecord. The following counts are used in this section:

Count Description

Age incumbent Calculates the average age of employees holding key positions.

Age successor Calculates the average age of employees approved to succeed keypositions.

The Tenure in Position section provides the average length, in years, that employees have held theirpositions. The following counts are used in this section:

Count Description

Tenure in position incumbent Calculates the average tenure of employees holding key positions.

Tenure in position successor Calculates the average tenure of employees approved to succeed keypositions.

170


The Tenure in Company section provides the average length, in years, that employees have been with thecompany. The following counts are used in this section:

Count Description

Tenure in company incumbent Calculates the average tenure of employees holding key positions.

Tenure in company successor Calculates the average tenure of employees approved to succeed keypositions.

To set up Holder/Successor counts:



3. Select Holder/Successor in the Enabled/Disabled Pages section.

4. Go to the Holder/Successor counts. All object counts in the list are enabled by default; clear the check boxto disable the required objects.

5. Set an alert to indicate when certain targets do not meet organizational goals.

The following counts provide an example of the set up:

Total number of key positions with successors: 50Female successors of key positions: 7

6. Select Enable from the drop-down list next to the Female successors of key positions.

7. Select a Condition operator, for example: < (less than).

8. Enter the required Value. For example, the organization indicates that 15% of successors must be female,so enter 15.

The application calculates the ratio: 7*100/50 = 14%An alert is shown to the user because female successors fall below 15%.

9. Click Submit.

171


Potential/Performance

The Potential/Performance page in the User Console provides the current and historical breakdown ofemployee potential and performance ratings for the last three assessment cycles.

Note: By default, it is assumed that there is one assessment cycle per year, and therefore the graph displaysdata for the last three years. If your assessment cycles are not performed once a year, contact yourimplementation partner to customize the time units.

To set up Potential/Performance counts :



3. Select Potential/Performance in the Enabled/Disabled Pages section.

4. Go to the Potential/Performance section. All objects in the list are enabled by default; clear the check boxto disable the required objects.

5. Click Submit.

172


TasksTask Overview

There are two tasks in Nakisa SuccessionPlanning that perform the following write-back operations:

Create Functional Area adds new functional areas in Nakisa TalentFramework. Functional areas are usedto group multiple job families, jobs, and positions collectively.

Create Job Family adds new job families in Nakisa TalentFramework. Job families are used group multiplejobs and positions to plan the distribution of employee potentials within an organization.

The Nakisa AdminConsole is used to set up the fields required for each task form. Mandatory fields, field order,and field validation types are also configured in the console.

173


Enable/Disable

This procedure enables a task in the end-user interface. The


The task is enabled in the application. The caption appears as the heading in the task dialog box. The caption for the task appears under Tasks in the appropriate application menu.

To enable a task:



The Tasks section displays the tasks available in the application.

3. Click the required task. Enable/Disable loads by default.

4. Select Yes to enable the task, or No to disable it.



7. Click Next.


174


Data Connection

A connection to the main data source for organization data is configured in the Data Connection screen.

Establish a connection to the SAP data source:


2. Click the task name under Tasks.







8. Click Next.


Add a data filter:


2. Enter a filter to query the data table.


The next step is to set up the task Fields.

175


Fields

This procedure updates the fields that are used to set up the tasks forms.

To set the fields:


2. Click Fields.






A typical example is the org unit ID field.

8. Click Next.






The next step is to set up the task Form Fields.

176


Form Fields

This procedure sets up the fields for the task form.

To add form fields:


2. Click Form Fields.





To set up the fields:

1. Click to activate the required rows.

2. Select the Field Validation Type.

3. Select the Order number for the required field. The field order is automatically updated.

4. Select the fields that are Mandatory in order for write-back to occur.

5. Click Next.

177


Application MaintenanceResetting Builds

When builds are published, all files contained in the build workspace folder are copied to the main applicationdirectory. Importing many customizations into a build and saving or importing many builds can cause theapplication directory to become filled with many extra files. If one of the builds introduced an error, then it maybecome impossible to load and publish other functioning builds.

Resetting the build will clean up the root application folder. Note that the root folder is always cleaned up thesame way regardless of which build was reset. All of the files and folders are deleted except for the following:

[application directory]/.system

[application directory]/.system [application directory]/Log

[application directory]/WEB-INF

[application directory]/rfc-logs

Note: The rfc-logs folder is only present if the RFC Trace feature has been enabled in one of the builds.

Once the application completes the cleanup, it logs out the administrator, reloads the root directory with filesand folders resembling a new build that has just been loaded but not yet published, and redirects theadministrator to the login page. The build needs to be published for the User Console to become availableagain.

Note: Resetting a build preserves all changes, customizations, add-ons, and saved builds, which are found inthe [application directory]/.system directory.

To reset a build:

1. Access the Nakisa AdminConsole, then load a build.

2. If the Upload Content, Export Changes, Save As, and Publish buttons are not displayed in the top-rightcorner, click Save & Publish current build in the menu panel.

3. Nakisa recommends saving the build before resetting it.

4. Click Reset Build > Log Off and Reset Build.

5. Log back into the Nakisa AdminConsole, and load the required build.

6. In the top-right corner, click Publish.

178


Deleting Builds

After saving and publishing a build, it appears in the build selection frame when accessing the NakisaAdminConsole. Any custom build appearing in this frame can be deleted. Deleting a build completely removesits build workspace folder.

Note: Default builds shipped with the application cannot be deleted.

To delete a build:

1. Open the administrator URL. The build selection frame is displayed.

2. Select a custom build, which is identified by the phrase "(user created)" after the Build Name.

3. Click Delete under the Action column.

179


Application Log Overview

Administrators use log records to monitor system operation, perform error analysis, or rev iew changes made tothe application configuration.

Nakisa applications create two log files:

Admin log: Records all configuration changes made to the application using the Nakisa AdminConsole. Anew Admin log file is created for every day that a configuration change is published.

Error log: Records application and database errors. Error log files are created in the following ways:

Upon initial login, an Error log file is created to record logs from the current day. This current log filecontains all the Error logs from the file's creation to the present.

When the user logs into the Nakisa AdminConsole on a subsequent day, the original log file is renamedto reflect that date and the current day's logs are then recorded in a new "current" log file.

The Roll Log button creates a new Error log file.

The following table outlines the default log file locations:

Log Type Default Directory

Admin /usr/sap/[system_name]/J00/j2ee/cluster/apps/Nakisa/[EAR]/

servlet_jsp/[WAR]/root/.system/Admin_Config/__XXX__[build_name]/Log

Where __XXX__ is the tenant number and [build_name] is the name of the requiredbuild.

Error /usr/sap/[system_name]/J00/j2ee/cluster/apps/Nakisa/[EAR]/

servlet_jsp/[WAR]/root/Log

The log files are named according to the following convention:

Log Type Default Directory

Admin yyyy-mm-dd.log

Error cds.log (for the current Error log file). cds.log.yyyy-mm-dd (for Error log files from previous days, created when the user

logs in to the Nakisa AdminConsole). cds.log.yyyy-mm-dd-hh-mm-ss (for Error logs created through the Roll Log

button).

180


Enabling Administrator and Error Logs

Use the Log Manager to enable or disable the Admin and Error logs. See Application Log Overview for detailson the log file names and locations.

To enable the logs:

1. In the menu panel, click Application-wide Settings > Log Manager.

2. In the Enable/Disable Log section, select the checkbox to enable the required log settings.

The following log settings are available:

Enable Log Module: Logs application errors. Enable Database Tracing: Logs database errors. Enable Admin Log Module: Logs configuration changes made in the Nakisa AdminConsole.

3. Click Submit to temporarily store the settings in the browser session memory.

181


Change Log Settings

The information written to the Error log has three severities:

INFO: Informational messages indicate when normal situations occur, for example, when the server isunable to deliver a notification message to a user who is logged off.

WARNING: A warning referencing a job signals a condition that does not prevent the completion of the job,but might indicate that some action is needed on behalf of the administrator.

ERROR: An error referencing a job signals a condition that might prevent the job from completingsuccessfully, depending on the setting of other parameters. Errors indicate that administrative action isneeded.

The application writes log entries of all severity levels (trace levels) to the error log file by default. The followinglog severity levels are available:

Errors, Warnings, and Information (the default setting) Errors and Warnings Errors only

Switching the severity level can help with the tracing of issues with the application.

Note: The decision to switch severity levels is left to the discretion of the system administrator.

To switch the severity level value :


2. Click Application-wide Settings > Enable/Disable Logs.

3. In the Set logging level section, select the required logging level.

4. Click Submit to save your changes.

Note: Increasing the log severity level has an impact on overall performance.

182


Administrators can update the provider properties to send Nakisa application log messages to SAP NetWeaver.

To direct Nakisa application log messages to SAP NetWeaver :

1. Navigate to the .system/application/Log directory of the application.

2. Open the provider.properties file.

3. Uncomment the following lines:

com.nakisa.log.provider=com.nakisa.framework.utility.log.SAPLogProvider

sap.logger.location=com.nakisa.application

sap.logger.category=Nakisa

4. Comment out the following line:

com.nakisa.log.provider=com.nakisa.framework.utility.log.Log4JLogProvider

5. Update the values of sap.logger.location and sap.logger.category for the system, if required.These are the values that identify the Nakisa error messages within the SAP NetWeaver Administrator logviewer

6. Save and close provider.properties .

7. Restart the Nakisa application from the SAP NetWeaver Administrator control panel.

Note: It is not possible to direct log entries to the Nakisa application log and the NetWeaver logging system atthe same time.

To view Nakisa application log messages in SAP NetWeaver :

1. Log in to the SAP NetWeaver Administrator control panel.

2. In the Show menus, choose General View and SAP Logs (Java).

3. Click Show View Properties.

4. In the Search By menus, choose Category and contains, then enter Nakisa in the search text field.

5. Click Find next. The log messages generated by the Nakisa application are displayed.

183


184


Viewing Error Logs

A log viewer is available in the Nakisa AdminConsole to provide quick access to Error log entries.

Note: The Log Viewer cannot be used to view the Admin logs.

To view Error logs:

1. In the menu panel, click Application-wide Settings > Log Manager. The View Log section displays theError log for the current session by default.

2. Choose the Error log you wish to view from the drop-down menu. Error logs from previous sessions areindicated by date (in the form cds.log.yyyy-mm-dd .).

3. The content of the log file is displayed.

Info messages are displayed in black text. Warning messages are displayed in orange text. Error messages are displayed in red text.

4. Click First to view the first 25 lines in the log file.

5. Click Next to view the next 25 lines in the log file.

6. Click Previous to view the previous 25 lines in the log file.

7. Click Last to view the last 25 lines in the log file.

185


Exporting Error Logs

The Error log is available to export through the Nakisa AdminConsole. By exporting the Error log, the user canhave a copy of the log to save locally.

To export the Error log:


2. In the View Log section, click Export Logs to export all of the logs.

3. Click the Download Logs link that appears to download a ZIP file containing the Error log files.

4. You can optionally export logs and system information together. See Viewing and Exporting SystemInformation for more information.

186


Generating Performance Reports

Generating a performance report collects and summarizes data found in an Error log file. There are two typesof performance reports:

The Detailed Performance Report provides the following information per action, displayed chronologically:

Time when the action occurred Action name Total action time (in milliseconds) Name of processor (Java class) that performs the action Total RFC calls

This section is split into two components: Number of all RFCs called for the action Sum of all instances that each individual RFC was called

Total RFC times

This section is split into two components: Total time (in milliseconds) of all RFCs called for the action Sum of the time (in milliseconds) for each individual RFC

The Summary Performance Report gives the following information per action, displayed chronologically:

Time when the action occurred Action name Name of processor (Java class) that performs the action Total action time (in milliseconds) Total RFC calls for the action Total time (in milliseconds) of all RFCs called for the action

To generate a performance report:


2. In the View Log section, select the log file for which you want to generate performance reports.

3. In the Select an action section, click Generate Performance Report.

4. Click the Download Report link that appears to download a ZIP file containing the two performance reportfiles, in the format:

logs-detailed-yyyy-mm-dd-hh-mm-ss.csv

logs-summary-yyyy-mm-dd-hh-mm-ss.csv

where yyyy-mm-dd-hh-mm-ss is the time when the reports were generated.

Tip: The Roll Log button is useful for generating reports for specific time periods or actions. See Creating ErrorLogs for details.

187


Creating Error Logs

The application automatically generates Error log files upon login to the Nakisa AdminConsole, but you can alsoforce the creation of a new Error log file.

To manually create a new Error log file:


2. In the Select an action section, click Roll Log.

The application renames the current log file to cds.log.yyyy-mm-dd-hh-mm-ss (whereyyyy-mm-dd-hh-mm-ss is the current time), and creates a new cds.log file to continue recording the day'slog.

Tip: Creating a new log file is useful when you want to generate reports for a specific action. In this case, youwould click the Roll Log button to create a new log file, perform the required action, then click the Roll Logbutton again, thus creating an Error log file containing only those log entries relevant to the performed action.

188


Find and Trace Application Errors

Transaction SLG1 (Application Log: Display Logs) is used to find and trace application errors logged in thesystem by the Nakisa RFC function modules.

Refer to the ZNAKISA_OBJECT Object and Sub-Objects section of the Nakisa Transport Package Installationand Specifications Guide (located in the Documents/InstallationGuides folder in the VisualizationSolutions by Nakisa 3.0 SP1 ZIP file) for a complete list of sub-objects for each Nakisa function module.

To view logs for Nakisa objects:

1. Log on to the SAP system and start transaction SLG1.

2. Enter 'ZNAKISA_OBJECT' as the Object to view all logs generated by Nakisa applications.

3. Enter the required Subobject to view log errors generated by a particular Nakisa RFC function module.

4. Select the required Time Restriction. Application logs are saved in the system for 7 days.

5. Click Execute.

189


Remote Support Procedure

The manager URL provides access to the Nakisa AdminConsole for remote application support.

Each Nakisa SuccessionPlanning application instance has its own URL, as follows:

http://[hostname]/SuccessionPlanning/manager.jsp

http://[hostname]/TalentFramework/manager.jsp

http://[hostname]/Manager/manager.jsp

Error logs can be reviewed remotely with the Log Viewer, but access to the Nakisa admin log is unavailableusing this URL.

The following actions are disabled in the Nakisa AdminConsole when the read-only administrator accesses theapplication remotely:

Submit in all setup wizards Save As, Save, and Publish build Create new admin user Change admin password Delete admin users

Follow the standard SAP remote access procedures to locate SAP logs for troubleshooting and supportpurposes. Information on setting up remote service connections to SAP is located on the SAP Support Portalunder http://service.sap.com/access-support.

190


Back Up and Restore

Application data resides in the client data system, including the ABAP data serv er or relational data server. Theback-up process for application data varies according to the data system; consult the appropriatedocumentation for details.

There are two application directories to back up:

Directory Contents

.system/Admin_Config/__XXX__[build_name] Configuration files modified after the build isupdated, saved, and published in the NakisaAdminConsole.

.system/custom Application files manually customized by a Nakisaimplementation partner.

The procedure is as follows:

Set up an automatic backup schedule for the current build, according to company policy. Back up the application customizations manually after changes are implemented by the consultant.

Note: A backup of the application directory can be made at any time (offline or online). A backup of theapplication directory should be made whenever the application is modified or updated. See also ExportChanges to a Build.

Follow these steps to restore the application:

1. Return the backup build directories and files to .system/Admin_Config .

2. Return the backup custom directories and files to .system/custom .


4. Review the build, then publish it to restore the application.

The console automatically quits administrator mode after publishing.

5. End the browser session.

6. Open SAP NetWeaver Administrator, then click Operations > Start and Stop.

7. Click the Java EE Applications tab, then restart the application.

191


TroubleshootingTroubleshooting Overview

The topics in this section cover common troubleshooting scenarios. If you are unable to resolve an issue onyour own, consult the SAP Service Marketplace Web site at http://service.sap.com, or contact the SAP GlobalSupport Center if you require standard product support for Nakisa applications.

Please be ready to provide the application name, product version, and build version, which can be found on thelanding page of the Nakisa AdminConsole.

Note: Detailed information about the package/build number can also be found in the NetWeaver administratorconsole.

http://service.sap.com

192


Unable to upload serial file, to log in, or to navigate

Problem

Following an initial deployment on SAP NetWeaver, one or more of the following problems occurs:

Unable to navigate through the Nakisa AdminConsole wizards Unable to log in to the Nakisa AdminConsole Unable to upload the Serial file Users unable to navigate in the Nakisa application

Explanation

Relative URLs are disabled.

Solution

Enable relative URLs in the AS Java Config Tool.

Procedure

1. Log on to the hosting server as an administrator.

2. Navigate to the /usr/sap/[system_name]/j00/j2ee/configtool directory, then run configtool.sh(in Linux), or configtool.bat (in Microsoft Windows).

The AS Java Config Tool opens.

3. Click Yes, if prompted.

4. Select View, Expert Mode from the main menu to enter Expert Mode.

5. Expand cluster-data, Template, managers, then select ClassLoaderManager in the left pane. TheManager properties load in the right pane.

6. Select the ForceResourceClose key in the table.

7. Enter false as the Custom Value in the Custom Property Data section, then click Set Custom Value.

8. Select File, Apply Changes from the main menu.

9. Restart the application server instance.

193


Error Message: Could not read properties file

Problem

The error "Could not read properties file" is received when launching the application.

Explanation

The JAVA_HOME environment variable is not set.

Solution

Set the JAVA_HOME environment variable in the Microsoft Windows System Properties.

Procedure

1. Right-click My Computer and select Properties. The System Properties dialog box appears.

2. Click Advanced.

3. Click Environment Variables. The Environment Variables dialog box appears.

4. Click New. The New System Variable dialog box appears.

5. Enter 'JAVA_HOME' as the Variable name.

6. Enter the directory path to Java (for example: C:\Program Files\Java\[Java_version] ) as theVariable value, then click OK.

7. Click OK to close Environment Variables.

8. Click OK to close System Properties.

194


Error Message: Invalid JAVA_HOME

Problem

The error "Invalid JAVA_HOME" is received when launching the application.

Explanation

The JAVA_HOME environment variable is not set.

Solution

Set the JAVA_HOME environment variable in the Microsoft Windows System Properties.

Procedure

1. Right-click My Computer and select Properties. The System Properties dialog box appears.

2. Click Advanced.

3. Click Environment Variables. The Environment Variables dialog box appears.

4. Click New. The New System Variable dialog box appears.

5. Enter 'JAVA_HOME' as the Variable name.

6. Enter the directory path to Java (for example: C:\Program Files\Java\[Java_version] ) as theVariable value, then click OK.

7. Click OK to close Environment Variables.

8. Click OK to close System Properties.

195


User login screen does not load

Problem

The login screen does not load.The user cannot log in.

Explanation

JavaScript is disabled in the Web browser.

Solution

Enable JavaScript in the browser Internet options.

Procedure

Microsoft Internet Explorer

1. Click Tools on the menu bar, then select Internet Options. The Internet Options dialog box appears.

2. Click the Security tab, then click Intranet.

3. Click Custom Level to open the Security Settings - Local Intranet Zone dialog box.

4. Click Enable for Active Scripting in the Scripting section.

5. Click OK to close the dialog boxes.

6. Press F5 to refresh the browser.

Procedure

Mozilla Firefox

1. Click Tools on the menu bar, then select Options.

2. Click Content and select the Enable JavaScript check box.

3. Click OK to close the dialog box.

4. Restart Firefox.

196


User interface does not display correctly

Problem

The application interface does not display correctly.

Explanation

Screen resolution is too low.JavaScript is disabled in the Web browser.

Solution

Set your computer screen resolution to 1024 by 768 or higher in the Windows Display Properties.Enable JavaScript in the browser Internet Options.

Procedure

1. Right-click the Windows Desktop and select Properties. The Display Properties dialog box appears.

2. Click the Settings tab.

3. Drag the Screen resolution bar and increase the value to 1024 by 768 or higher.

4. Click Apply. The screen adjusts to the selected resolution.

5. Click Yes to save the new settings.

6. Click OK.

Procedure



2. Click the Security tab, then click Intranet.

3. Click Custom Level to open the Security Settings - Local Intranet Zone dialog box.

4. Click Enable for Active Scripting in the Scripting section.

5. Click OK to close the dialog boxes.

6. Press F5 to refresh the browser.

197


Procedure

Mozilla Firefox


2. Click Content and select the Enable JavaScript check box.

3. Click OK to close the dialog box.

4. Restart Firefox.

198


Cannot load the Printing Wizard

Problem

The Printing Wizard does not load after selecting Print from the Actions menu.

Explanation

Pop-up windows are disabled in the Web browser.

Solution

Enable pop-up windows in the browser Internet options.

Procedure



2. Click the Privacy tab.

3. Clear the Turn on Pop-up Blocker check box in the Pop-up Blocker section.

4. Click Apply and OK.

Procedure

Mozilla Firefox


2. Click Content, then clear the Block pop-up windows check box.

3. Click OK.

199


Error Message: Internal Error

Problem

The user receives an "Internal Error".

Explanation

An error referencing a job signals a condition that might prevent the job from completing successfully,depending on the setting of other parameters.

Errors indicate that administrative action is needed.

Solution

Perform error analysis using the log messages created by Nakisa applications.

Procedure

Use transaction SLG1 to find and trace application errors logged in SAP NetWeaver by the Nakisa RFCfunction modules. More information about this transaction is provided in the Find and Trace Application Errorssection.

Log messages are also written to the application log files named according to the date when a change or erroroccurs in the application or Nakisa AdminConsole: cds.log.yyyy-mm-dd .

The Error log records application, configuration, and database messages, and indicates three severities: INFO,WARNING, and ERROR. This log is saved under /Log in the main application directory.

The Admin log records Nakisa AdminConsole activity. The configuration file modified, the user who made themodification, and the changes made to the application is recorded. This log is saved to the .system/Admin_Config/___XXX___[build_name]/ Log directory, where ___XXX___ is the tenant number.

200


Org chart diagram is missing

Problem

The org chart diagram is missing when the user opens a hierarchy.

Explanation

The data source connection string is not set or incorrectly configured.Root ID for the hierarchy is not set.

Solution

Open the Nakisa AdminConsole, then verify the following for each hierarchy:

Check the connection string in the Data Connection setup wizard. Check the Hierarchy fields in the General Settings setup wizard.

Procedure

Refer to the following topics:

Connection String provides information about the connection string used to retrieve data from the SAPserver.

Hierarchies provides information about setting up the root ID for the hierarchy.

201


Talent Profile Details window is blank

Problem

The Talent Profile Details button in the Employee Details panel opens a window that displays a blank page.

Explanation

The Adobe Document Services (ADS) plug-in must be present in SAP to display content in this window.

Solution

Contact the SAP system administrator to install credentials and configure the Adobe Document Serv ices (ADS)Web Service in SAP NetWeaver.

202


Session timeout in Flash Grid

Problem

A session timeout notice is received if a user works in the Grid for more than 10-15 minutes, then attempts togo anywhere else in the application.

Explanation

The value of the Session.Timeout property is greater than 24 hours (1440 minutes) in the Microsoft InternetInformation Services (IIS).

Solution

Refer to the Microsoft Support Article ID: 233477 "PRB: Session.Timeout Has a Maximum of 24 Hours" tochange the value to less than 24 hours.

http://support.microsoft.com/kb/233477

203


Changes to a published build are unavailable to users

Problem

After making changes to and publishing a build from the AdminConsole, users already connected to the serverare unable to see the changes, or experience unexpected behavior.

Explanation

Cache or memory issues may be interfering with the display.

Solution

Ask the user to refresh his or her web browser display. If the problem persists, restart the Nakisa applicationserver.

204


Glossary

The following table lists the terms and definitions specific to the Nakisa AdminConsole.

Term Definition

add-on A software extension that contains customizations or provides additionalfunctions for a core application.

analytic A tool that measures specific information, such as gender, age, orperformance.

anonymous login An authentication method that provides access to the application without auser-specific account.

assistant filter A filter that includes or excludes assistants.

authentication mechanism The method that grants users access to the application.

authentication source The data source that contains user access information.

basic mode An application mode that uses the browser to render the organizationalcharts in HTML.

build A saved configuration that contains data connection, security, and featuresettings for the application.

build panel The top section of the Nakisa AdminConsole that displays details on thecurrent build.

build selection A list of builds that loads when the Nakisa AdminConsole is accessed.

child exists filter A filter used to identify whether a hierarchy node has a child.

column table element A Details Designer and Views Designer placeholder that displayselements in the table side by side.

competency The skills and abilities of an employee, such as adaptability, innovation, orstrategic thinking.

condensed style An org chart box view that is smaller than the regular style. See regularstyle.

data table The name of the relational database table used to configure the currentfeature or task.

default org chart root The defined top level of an org chart that does not have a parent.

Data Center A central location in the Nakisa AdminConsole that is used to managedata connectivity and configuration in the application.

Details Designer A customizable schematic of graphical user interface controls in theapplication Details panel.

Details panel A panel that displays extended information about a database record.

directory filter A filter that limits directory search results to a specific type of record.

dotted relationship The situation where a position belongs to one org unit, but also hasresponsibility to another via an indirect reporting relationship.

dotted relationship filter A filter that defines the field to search in the data source to render indirect

205


Term Definition

reporting relationships in the org chart.

element ID field The field containing the unique ID for an employee, position, or org unit.

e-mail section A Views Designer element that displays the selected field as an e-mailaddress.

emergency user A reserved user that can access the SAP system in cases where alladministrators are locked due to incorrect configurations or forgottenpasswords.

export limit The maximum number of records that can be printed or exported to athird-party application such as Microsoft Excel.

field link A Details Designer and Views Designer function that enables informationthat is not included in the current record to be displayed.

field value section A Details Designer and Views Designer element that displays the fieldname and value.

field/value section multiple A Details Designer element that displays the field name and value formultiple fields.

group by The field of the child hierarchy that matches the value in the Link Usingfield of the parent hierarchy. The method used to configure linkedhierarchies. See link using.

group child exists filter A filter used to identify whether a child hierarchy is linked to the parenthierarchy.

hidden section A concealed section in the Views Designer that uses the value of a fieldas a condition.

hierarchy An order of objects arranged above, below, or at the same level as oneanother.

hierarchy ID field The field used to create a hierarchy structure, typically the unique ID of anobject.

hierarchy parent field The field that identifies the ParentID field in a data table.

hierarchy root The top level of a hierarchy that does not have a parent node.

image section A Details Designer element that displays the specified field as a portrait.

initial catalog A parameter that specifies the database name for the data source in anSQL connection string.

key-performance indicator(KPI)

A metric used to define and measure progress toward organizationalgoals.

link using The field of the parent hierarchy that matches the value in the Group Byfield of the child hierarchy. The method used to configure linkedhierarchies.

linked hierarchy A hierarchy that is joined to another hierarchy by a common value. Anemployee hierarchy can be linked to a position hierarchy, for example.

listing A real-time search capability used to find organization informationcontained in the company human resource data repository.

206


Term Definition

listing section A Details Designer element that displays the selected field values as alisting.

module A self-contained application component that has features and/or tasks ofa similar focus.

name section A Details Designer and Views Designer element that displays only thefield value.

name section multiple A Details Designer and Views Designer element that displays only thefield value for multiple records.

node An individual element in a hierarchy that is branched to parent and/or childnodes based on structural relationships.

organizational unit (org unit) A functional unit in an organization that has a defined area ofresponsibility.

org chart A diagram that consists of one or more linked hierarchies.

org chart box An individual element of an organizational chart that displays recordinformation in a box.

org chart root The top-level node in an org chart. The org chart root does not have aparent org chart box.

org chart style A switch that displays organization hierarchies in various standard,compressed, and condensed formats.

org chart view The layout of information displayed in an org chart box.

panel element A Details Designer and Views Designer placeholder with an editable title.

parent description field The field that describes the parent node; typically the name or title.

picture section A View Designer element that displays the selected field as a portrait.

Profile A pop-up window that displays the details of a record.

publish A task in the Nakisa AdminConsole used to save and apply applicationchanges. Published changes are visible by users.

regular style The normal org chart box layout. See condensed style.

remote function call (RFC) The standard interface for communication between SAP systems and theclient system.

row table element A Details Designer and View Designer element that displays elements inthe table vertically.

section element A Details Designer and Views Designer element where the displayedfields and/or values are defined.

Selected Items panel The panel that loads to display selected org chart boxes or listing records.

serial file A file needed to activate the application. This file specifies the availablemodules, languages and total number of records the application canaccess.

simple caption section A View Designer element that displays the value of the selected field. Onlyone field may be selected.

207


Term Definition

simple value section A View Designer element that displays the value of multiple fields.

standard mode An application mode that uses the Flex compiler from Adobe Systems torender the organizational charts in Adobe Flash.

subcategory group A grouping of similar employees or positions that can be displayed in oneorg chart box.

successor bench strength A key figure that states the number of potential successors assigned to ajob or position.

swap file A file that stores user-defined application settings and preferences.

System Landscape Directory(SLD)

An SAP application that contains information on the software componentsinstalled in a system landscape.

tabs element A Details Designer placeholder that creates a tab section.

task An activity or set of activities performed by users to add, modify or deletedata stored on the company server directly from the application.

talent management specialist(TMS)

A specific role in an organization that analyzes and manages thesuccession planning process, and the organizational structure.

telephone section A View Designer element that displays the selected field as the telephonenumber.

validation The process that ensures consistent and correct data input in theapplication.

208


Index

- A -ABAP parameters 93access, logon screen 36add-on inbox 99add-on manager 99add-on, loading precedence 100add-ons, disabling 104add-ons, enabling 103add-ons, export configurations 106add-ons, instructions file 102add-ons, Nakisa ABAP 93add-ons, removing 105administrator users 15Advanced Business Application Programming (ABAP) 93advanced search forms 128anonymous login 40application interface 17application modules 51AppResources 18areas of responsibility 34authentication 35authorization objects 26authorization profiles 33, 34

- B -backup 190Basic org chart mode 63bench strength 164build comments, adding 22build, delete 98build, exporting 94build, importing 95build, reset 97builds 18builds, loading 19builds, saving and publishing 20

- C -Caption Editor 52captions, export and import 53cascading style sheet (CSS) 141client authorization 26color mapping 157color, org chart boxes 156company logo, for print 43competency groups 168condensed style 148configuration files 18connection strings, SAP 24cookie 59core competencies 168

- D -

209


dashboard, as entry page 163Data Center 64data connection tasks 174data connection, Data Center 65data connection, org chart 110data connections, listings 122data element, listings 86data element, multiple SAP tables 78data element, RDBMS 91data element, SAP RFC 70data element, single SAP table 74data elements 69data elements, creating 131default roots 112default view, org chart boxes 146Deleting Builds 178Details Designer 129Details panel, creating 129directory filters, listings and searches 124disabling, add-ons 104disabling, listings 121disabling, org chart views 145disabling, org charts 109disabling, tasks 173

- E -emergency users 32employee images 42employees 108enabling, add-ons 103enabling, listings 121enabling, org chart views 145enabling, org charts 109enabling, succession wizards 50enabling, tasks 173error logs 179error messages 48export captions 53export defaults 45exporting, add-on configurations 106

- F -field captions 111, 123field validations 46field, tasks 175fields, listing and search 123fields, org chart 111fields, sort setup 118fixed lists 46form fields 176full-time equivalent (FTE) 164

- G -glossary 204

- H -HCM Dashboard 162

210


hidden sections 159hierarchies 112

- I -image mapping 158images, portrait 42import captions 53import parameters 70inbox, add-on 99incumbents 169instructions file, add-on 102iView 37

- J -join details 78, 86

- K -key positions 164

- L -languages 62linked hierarchies 112listing columns 126listings 120listings, data element 86listings, directory filter 124listings, disabling 121listings, enabling 121listings, fields 123loading builds 19loading, add-ons 100log files 179log settings, change 181login, anonymous 40logo setup, for print 43logon screen 36logon ticket 39logs, creating 187logs, enable 180logs, exporting 185

- M -mapping, color 157mapping, images 158menu links, org chart 116modifying captions 52modules, enabling 51

- N -Nakisa ABAP add-on 93Nakisa AdminConsole, accessing 13Nakisa RFC function module 188

- O -org chart boxes, color 156

211


org chart boxes, color mapping 157org chart boxes, default view 146org chart boxes, height and width 155org chart boxes, image mapping 158org chart boxes, moving controls 160org chart boxes, panel design 152org chart boxes, removing controls 161org chart boxes, section design 153org chart boxes, table design 150org chart modes 63org chart roots 112org chart Views caption 149org chart views, creating 142org chart views, disabling 145org chart views, enabling 145org chart views, hidden sections 159org chart, menu links 116org charts 108org charts, adding details 144org charts, condensed style 148org charts, disabling 109org charts, enabling 109org charts, fields 111org charts, previewing 147org units 108organization plan 33organizational objects 108output table 78, 86

- P -panel design, org chart boxes 152performance 171performance reports 186placement horizon 164portrait images 42position 108positions 164potential 171precedence, add-on 100previewing, org chart boxes 147print defaults 45processed table 78, 86profile match 49profile windows 119profiles, authorization 33, 34publishing builds 20

- R -read-only users 15relational database management system (RDBMS) 91remote function call (RFC) 26, 70remote support 189removing, add-ons 105Resetting Builds 177restore 190roles 25, 41roots, org chart 112

212


- S -SAP connection strings 24SAP emergency user 32sapsecu.dll 39sapssoext.dll 39saving, builds 20search forms 127searches, fields 123section design, org chart boxes 153Selected Items panel 117, 125serial files 14SettingsResources 18single sign-on 37, 39sort field setup 118SSO2 ticket 39Standard org chart mode 63structural authorization 26, 34sub-category groups 115succession 164succession wizards, enabling 50successors 169swap file 59system directories 99system information 58

- T -table design, org chart boxes 150table joins 78, 86talent groups 164tasks 172tasks, data connection 174tasks, disabling 173tasks, enabling 173tasks, field 175technical support 11, 44themes 62transaction SLG1 188

- U -upload content 96user authentication 35User Console, launching 23user input 46user preferences 59user types 25users, administrator 15users, emergency 32users, read only 15Using the RFC Trace 54

- V -validations, field 46verify.pse 39Viewing Error Logs 184Views Designer 142views, creating 142

213


- W -wizards 50writeback refresh 57

Headquarters

Nakisa Inc.733 CathcartMontreal, Quebec H3B 1M6Canada

Phone: +1 (514) 228-2000Fax: +1 (514) 286-9786

Europe

Nakisa GmbHAltrottstraße 3169190 WalldorfGermany

Phone: +49 (0) 6227-734070

Asia-Pacific

NakisaLevel 21 Centennial Tower3 Temasek AveSingapore 039190

Phone: +65 6549~7506Fax: +65 6549~7001

www.nakisa.com

2012 Nakisa Inc. All rights reserved.