Frequent Contributor.. hyllplan Frequent Contributor..
Frequent Contributor..
156 views

ksc_create_baseline_staffing_profile, known bug?

Jump to solution

Hi

 

PPM v9.22

Trying to use the command 'ksc_create_baseline_staffing_profile'

 

The following example works properly:

ksc_create_baseline_staffing_profile STAFFING_PROFILE_ID="[REQ.P.KNTA_STAFFING_PROFILE]" SP_BASELINE_NAME="[REQ.VP.KNTA_STAFFING_PROFILE] Baseline #1"

 

Below example does not work as I cannot make [SQL_OUTPUT] to resolve!!??
(I can see by using ksc_comment "[SQL_OUTPUT]" that I do get a result in this token but NOT when it is used in the SP_BASELINE_NAME parameter below)

 

ksc_run_sql QUERY_STRING="SELECT to_char(sysdate, 'YYYY-mon-DD') FROM dual" ENV_NAME="[SOURCE_ENV.ENVIRONMENT_NAME]"

ksc_create_baseline_staffing_profile STAFFING_PROFILE_ID="[REQ.P.KNTA_STAFFING_PROFILE]" SP_BASELINE_NAME="[REQ.VP.KNTA_STAFFING_PROFILE] [SQL_OUTPUT] Baseline #1"

 

It seems like not all tokens is able to resolve within SP_BASELINE_NAME parameter? Ive tried some of my tokens from the project request, e.g. [REQD.P.TEST], it does not work either. It seems like STANDARD tokens resolves fine though such as [REQ.VP.KNTA_STAFFING_PROFILE].

 

Is this a known bug? Is there a workaround?

 

Johan

0 Likes
1 Solution

Accepted Solutions
Frequent Contributor.. hyllplan Frequent Contributor..
Frequent Contributor..

Re: ksc_create_baseline_staffing_profile, known bug?

Jump to solution
Thanks Randull
SQL_OUTPUT isnt the problem, it behaves correctly as It resolves using ksc_comment
I did find a solution - if I do ksc_set and try to use that token in the same execution step as ksc_create_baseline_staffing_profile in the SP_BASELINE_NAME parameter it will NOT work, the token will not resolve. It is like ksc_create_baseline_staffing_profile executes first in the execution step dispite its last in the list. My workaround is to do a ksc_set in a separate execution step BEFORE the one used for ksc_create_baseline_staffing_profile. That works fine.
Johan
3 Replies
Absent Member.. randull Absent Member..
Absent Member..

Re: ksc_create_baseline_staffing_profile, known bug?

Jump to solution

Hi Johan,

 

In this case only the standard tokens can be used. I mean you should not use the tokens from user created fields for these commands.

 

Also, I believe that what is causing you problems is the SQL_OUTPUT. Try to Add an Environment to the Source for the Workflow Step will allow the [SQL_OUTPUT] Token to resolve.

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
Frequent Contributor.. hyllplan Frequent Contributor..
Frequent Contributor..

Re: ksc_create_baseline_staffing_profile, known bug?

Jump to solution
Thanks Randull
SQL_OUTPUT isnt the problem, it behaves correctly as It resolves using ksc_comment
I did find a solution - if I do ksc_set and try to use that token in the same execution step as ksc_create_baseline_staffing_profile in the SP_BASELINE_NAME parameter it will NOT work, the token will not resolve. It is like ksc_create_baseline_staffing_profile executes first in the execution step dispite its last in the list. My workaround is to do a ksc_set in a separate execution step BEFORE the one used for ksc_create_baseline_staffing_profile. That works fine.
Johan
Absent Member.. randull Absent Member..
Absent Member..

Re: ksc_create_baseline_staffing_profile, known bug?

Jump to solution

Hi Johan,

 

Thanks for the information.

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.