Succession Planning 3.0 : Logout button missing

[Former Member]

Hi,

I'm in Succession Planning 3.0.

Security setting is set to log on screen. When I launch the application, I do get the logon screen. However, on top top left of the main screen, I don't get the logout button. I checked the images folder, the image are there. But it is not showing up, and there is no error either. Does anyone have any idea?

The same happens to TalentFramework, but OrgChart is working fine. Here's the log:

115. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - Tenant ID: 000
116. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - LoginSettingsObject Load: 16
117. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Credential provider ActiveDirectory
118. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : User to authenticate acn_spchuah
119. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Authentication provider SapStandard
120. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : User authenticated acn_spchuah
121. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Authentication row is null
122. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : User population provider is Default
123. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : User populated
124. 11 Jan 2011 14:25:27 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Login process finished successfully
125. 11 Jan 2011 14:25:29 INFO com.nakisa.Logger - Invoking action:setorgchartdirectory [SAPMyOrgUnitOrgChart, myreports]. For processor OrgChartAppEventProcessor. Against controller OrgChartCtr
126. 11 Jan 2011 14:25:29 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:1
127. 11 Jan 2011 14:25:30 INFO com.nakisa.Logger - FunctionRunner.executeFunctionDirect: HRTMC_GET_DIRECT_RESP_ORGUNITS took: 391ms
128. 11 Jan 2011 14:25:30 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:1
129. 11 Jan 2011 14:25:30 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:1
130. 11 Jan 2011 14:25:30 INFO com.nakisa.Logger - FunctionRunner.executeFunctionDirect: HRMSS_GET_ORGSTRUCTURE_AS_XML took: 516ms
131. 11 Jan 2011 14:25:30 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:1
132. 11 Jan 2011 14:25:30 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:1
133. 11 Jan 2011 14:25:31 INFO com.nakisa.Logger - FunctionRunner.executeFunctionDirect: HRMSS_GET_ORGSTRUCTURE_AS_XML took: 94ms
134. 11 Jan 2011 14:25:31 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:1
135. 11 Jan 2011 14:25:31 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:1
136. 11 Jan 2011 14:25:31 INFO com.nakisa.Logger - FunctionRunner.executeFunctionDirect: HRMSS_GET_ORGSTRUCTURE_AS_XML took: 63ms
137. 11 Jan 2011 14:25:33 INFO com.nakisa.Logger - setorgchartdirectory on OrgChartAppEventProcessor took: 4281ms
138. 11 Jan 2011 14:25:33 INFO com.nakisa.Logger - Invoking action:refresh []. For processor FalconModuleControlAppProcessor. Against controller ModuleControlCtr
139. 11 Jan 2011 14:25:34 INFO com.nakisa.Logger - refresh on FalconModuleControlAppProcessor took: 500ms

[lukemarson]

Hi,

The Log Out button is disabled by default because of Portal integration. No logout is required in the Portal for obvious reasons.

The setting Stephen provided will allow you to toggle the display or non-display of the button so you can change it for various scenarios (ie Portal integration or Forms Login). One to write down

Best regards,

Luke

[Former Member]

Hi,

Thanks Stephen. It works.

Hi Luke,

Shouldn't the logoff button shows when the security setting is set to Logon Screen? It should be off only if I set the security settings to Single Sign On, isn't it?

Regards,

[lukemarson]

Hi,

You'd expect that, but I think this option gives flexibility for clients with different security policies. Users using a hsare computer, for example, should always log off while those on their own computer need not do it. It's a simple setting and only really needs to be set once so it's just about seeking your client's preference on it.

Best regards,

Luke

[StephenBurr]

I've noticed this behaviour ... if you move from Logon screen to SSO settings it creates a settingsresources item called "HideLogOff" (as file HideLogOff.txt in \.delta\SettingsResources\ folder).

But if you change back from SSO to Logon screen this doesn't get amended / removed ... so the logoff button remains hidden.

Suggest removing from your .delta (or opening and changing content from true to false).  I'd remove if I was you.

Stephen

[Former Member]

Hello Stephen,

I followed your recomendations and it worked perfectly.

Thank you for your help...

[Former Member]

Hello Stephen,

  The solutions did not work at all, because when I published the Build of CP the valor of HideLoggOf.TXT file changed from FALSE to TRUE. Then I searched the folder .delta, but there is´nt, I found xdelta-1.1.3 folder.

I think that is because the Operative System is Linux red hat and the paths are diferents, do you know what is the path or folder name .delta in Linux?

Thank you for your help

[lukemarson]

The path will be something like:

/usr/sap/<SID>/<Java SID>/j2ee/cluster/apps/Nakisa/OrgChart/servlet_jsp/OrgChart/root/.system/Admin_config/<build>/.delta

<SID> = NW instance

<Java SID> = NW Java instance

<build> = name of your configuration

All changes must be made in files in this folder. If not, then your changes will be lost.

[Former Member]

Hello Luke,

I found the path, but the folder .delta not exist into the Build folder, can I create it?,or What I have to do?

Regards

[lukemarson]

Are you looking in a build you created, or a default build? It won't exist in a default build unless you made changes to the build, which I don't recommend.

[Former Member]

Hi Experts,

We are using Nakisa 3.0 SP3, and the Log on bottom is a default configuration to TF, SP, CP, OM.

Thank you for your help

Regards.

[StephenBurr]

There is a setting in SettingsResources.xml that controls this:

    <item>
        <name><![CDATA[HideLogOff
        True
    
]]>

Stephen

[Former Member]

Hello experts,

We´re implemented some applications of Nakisa two of them are Talent Framework and Succession Planning, we have problems with Logout bottom is missing, in OrgModeler we  copied the security folder from OrgChart to OrgModeler and it worked, is it the same steps for TF and SP? ...would you tell me what we have to do for set the logout bottom in Talent Framework and Succession Planning?

ECC 6.0 EHP5, Nakisa 3.0 SP2

Thanks in advance for your help!!