cancel
Showing results for 
Search instead for 
Did you mean: 

Nakisa OrgChart not fitting full text of OrgUnit.

Former Member
0 Kudos
167

Dear Experts,

We are Implementing Nakisa OrgChart 4.0, SP1.

We are facing some Issue in OrgChart, OrgChart boxes are not displaying full text of the Organization Unit. We want to wrap the text/Extend the OrgChart Box width.

How to resolve this issue, after gone through the Admin guide we came to know we can change the width in XSL files, Can anyone please help me on this issue.

In which location, with XSL template and where the code needs to change?

Please find the below screenshot for your reference.

Thank you so much in advance for your great support.

Best Regards,

Vijaya.

Accepted Solutions (1)

Accepted Solutions (1)

StephenMillard
Active Contributor
0 Kudos

Vijaya.

For each view there is an XML file in AppResources\viewconfiguration.  It shouldn't be too hard for you to match the names to your views.  Within these you'll find some box widths that you can increase.  I've always changed each occurrence (in each configuration group).

e.g.


<boxwidth><![CDATA[270]]></boxwidth>

You'll also need to find the corresponding XSL file in Templates_Generated.  Look at the prefix of the file name to work out which XSL relates to which view configuration - it's pretty logical.

In here there are some VBox widths you will want to change for different view options (standard, condensed, print, etc.)

e.g.


<VBox width="250" style="vertical-gap:0;padding-top:10;">

You'll potentially also want to take a look at the XSL to see within each of these how it is truncating the length.  For example you might see some XML saying that in some views it truncates a string at 33 characters and adds an ellipsis (...) whereas in others it might truncate at 35.  I don't recall exactly what it is for your particular case.

These changes should allow you to tweak the box widths and text string lengths for both your basic (Flash) and standard (HTML) versions of your view in all it's varieties (standard, print, condensed, etc.)

Regards,

Stephen.

Former Member
0 Kudos

Hi Stephen,

Thank you so much for your guidance.

I have changed <boxwidth><![CDATA[270]]></boxwidth>  view of XML file in 5 occurrences and I tried to change in XSL VBox Width = "250" but in XSL file having percentage like <VBox width="100%" style="vertical-gap:0;padding-top:10;">, so I am confused how and where I need to change.

Please find the below screenshot of XLS file width option.

Could you please help me, how and where I need to change the width in XSL file.

Best Regards,

  1. Vijaya.
Former Member
0 Kudos

Hi Stephen,

do I need to change width in the below code?, see the below creen and let me know.

Best Regards,

Vijaya.

StephenMillard
Active Contributor
0 Kudos

Vijaya.

I'm not sure how much luck you'll have with percentages in the box width.  I think I tried it once when I was first starting out with Nakisa apps and I don't think it worked.  Try using pixels (just numbers) instead.

For the XSL I think  maybe I was thinking a little too much of some other fields.  Looking at the standard OU view for example I can see the html-display template using the boxwidth in determining at what length to out in an ellipsis so it looks like changing the boxwidth should be enough to specify the length of the text ... just keep in mind it is by pixels not characters,

Looking at the flex-display I can see the width in the VBox as 235 so this would need to be increased to accommodate your longest org unit name.  But note also that the $OrgUnitName could be output for either of two options (relating to the assistant icon).  The width of the label field would also need to be increased otherwise it will not make use of the additional box width.

The changes should also be reviewed for the other templates in the XSL.

Hope that helps.

Regards,

Stephen.

Former Member
0 Kudos

Hi Stephen,

Instead of using 100% how much width should I give in XSL files, in XML file I have added 270 so in XSL also should I mention the same?.

Yes you are right VBox is having 235 currently, so can I keep 270 here to accommodate my  longest org unit name?

@The changes should also be reviewed for the other templates in the XSL: you mean I need to change in all other View templates right?

Best Regards,

Vijaya

StephenMillard
Active Contributor
0 Kudos

Vijaya.

I would suggest keeping your widths consistent.  I can't give you an exact width as it will depend upon how many pixels it takes to display the width of your longest org unit name or to the width at which you think it is reasonable to truncate the name.

The way I do it is to find an example and keep trying different widths until I get the right one.  You could also use an on screen ruler (e.g. Ruler) to help you.

By other templates I do mean check all of them.  You may decide that for condensed boxes you are happy with truncation.  You may decide similarly for printing to save space.  You may decide that you want everything identical.  It is a decision for you or your client to make.

Make sure you verify for both standard and basic modes and that you give consideration to changing the widths for any other views you might be using.

Regards,

Stephen.

Answers (0)