Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

PPM 9.13 - New server parameter

Highlighted
Sascha_1
Member

PPM 9.13 - New server parameter

Hello,

 

i read in the "Waht's New" guide about the AUTO_COMPLETE_LONG_TYPE_CULLTEXT_REQUIRED server parameter. Please can someone explain in more detail what the parameter will do when true/false? I tested both on our test system, but i saw no difference when open a auto complete list.

 

Best Regards,

Sascha

4 REPLIES
Utkarsh_Mishra
Honored Contributor

Re: PPM 9.13 - New server parameter

I have also not tested it but this is what it is mentioned in admin guide.

 

Determines whether the user must enter a filter in the auto-complete dialog box in order to retrieve the initial
results for validations of type long. If set to true, and no user filter is specified, the validation returns an
empty result set. The user must then either click Find or select the Show All link.

 

 

Also have you resarted the server and run kUpdateHtml.sh after the parameter change.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Sascha_1
Member

Re: PPM 9.13 - New server parameter

Hi,

 

i will explain what I have done to test the new parameter:

 

1. Add parameter com.kintana.core.server.AUTO_COMPLETE_LONG_TYPE_CULLTEXT_REQUIRED=true to server.conf

2. Stop server

3. Run kUpdateHtml.sh

4. Start server

5. Open Workbench --> Search for a auto complete list validation (in my case the validation is sql-custom / type: long)

6. Create a test request and open the affected validation.

 

Result: The system show all available results by default. So i did not get a blank result page.

 

Regards,

Sascha

Utkarsh_Mishra
Honored Contributor

Re: PPM 9.13 - New server parameter

Are you trying for LONG type...

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Sascha_1
Member

Re: PPM 9.13 - New server parameter

Yes, i tried (see 5. point of my previous answer).

//Add this to "OnDomLoad" event