Navigate up button in OrgChart is missing after deployed new build

[Former Member]

I got the requirement to set root org as User's Org, so I set as User Record -> Org Unit ID.

Then I create text file "AllowUpLevelForRootTypeUser" in SettingResources, which has 'true' in it., Navigate Up button is shown and able to navigate up by structural authorization.

But I got issue on Generate Chartbook so I raised OSS and got information to deploy new build of 0910048400 to fix this. (My previous build is 0910026400).

After deployed new Build, I can solved generate chartbook issue, but got new issue; Navigate Up button that used to be at the root org is missing. I import the same configuration to my localhost (Tomcat), the button still exist.

I assumed that there might be some new configuration on this build. How should I get the button back?

Thank you

[StephenMillard · Accepted solution]

Apitchaya.

I'm currently working with a client that has deployed build 0910037100.  Their configuration is to start at the user's own root, but the usual configuration (as you described) is not allowing them to navigate upwards in the structure from that root; though they can search for an org unit and the navigation then works fine.

I reported the issue via OSS and SAP passed the issue on to Nakisa about a week ago.  I've just checked and I've had a response.  Whilst I'm pretty confident that I have done the configuration as they requested, there's always the chance I missed or mistyped something.  Unfortunately I won't get chance to check now until some time on Tuesday.

I think it would be worth you reviewing your configuration against the official information they have sent me.  If the issues persists then submit via OSS and include screen shots of the details they are referencing to prove that you have configured it correctly. That's what I plan to do should my configuration in fact be as per their instructions.

Info received via OSS:

Step 1: Get the Nakisa OrgChart latest build to deploy the application.

Step 2: In Admin Console set up dynamic rooting.

Go to the hierarchy wizard of an org chart's root hierarchy (for example Organizational Structure in OrgChart). Choose the following:

Orgchart root value source = User record

User record field = Organizational Unit (Org_unit)

Step 3: In SetingsResources set AllowUpLevelForRootTypeUser = true

AllowUpLevelForRootTypeUser.txt should be a text file and not an xml file.

The content of the text file should just be one word: 'true' (without the quotation marks)

Note: If the setting AllowUpLevelForRootTypeUser does not exist in SettingsResources, it is the same as AllowUpLevelForRootTypeUser = false

Step 4: Publish the build.

Step 5: In the User Console verify that the button with the tooltip 'Start chart one level above' starts appearing on the root org chart box

Regards,

Stephen.

[StephenMillard · Accepted solution]

Just to follow-up on this, our client's configuration does match this, so it does support my belief that there is a bug.  A colleague checked the config for me and passed the OSS back on Monday.  We've not had any updates since then, but I'll try and remember to come back on this.  I would still recommend that you submit via OSS and the if you get a response first you could come back and note it.

Hope that helps.

Regards,

Stephen.

[Former Member · Accepted solution]

Thank you for this. I have raised OSS for a while and got message that they are checking with Nakisa Support.

[StephenMillard · Accepted solution]

Apitchaya.

Last week we got a fix released to us for this issue (OrgChart build 0910053200).  We're just awaiting some resource availability on the client side to check it.

Regards,

Stephen.

[Former Member · Accepted solution]

Hi Stephen,

We've got this build to fix issue too. It solved the issue and we are currenly working on it.

Thank you.