Super Contributor.. patrick-sa Super Contributor..
Super Contributor..

Timer in execution step

Hi All,


I'm running a couple of commands in an execution step and this works well.The problem i'm faced with is that  after execution step completes execution,the front end takes a few milliseconds to update the data.So if i were populate a certain field,the field still shows blank even after successful execution of the step.If i refresh the page the information is displayed as expected.I have set the execution to finish before displaying results to users.


I'm thinking of creating an additional command after execution of the first batch of commands so that this command delays the page display by about 10 seconds to allow data to be populated.I know it exists i just cant remember how to do this.


So the solution would be


1. execution steps -> delay execution step -> display result to user.





2 Replies
Jason Nichols K Absent Member.
Absent Member.

Re: Timer in execution step

My first question would be what commands you are executing?  Internal commands like ksc_store should show the data immediately upon page refresh.  Now, if you are updating data using a SQL script, things get a little trickier.  Theoretically, if you update the LAST_UPDATE_DATE field in the tables you are updating, PPM should automatically refresh its cache so that the new data will available to the server.  However, I have seen where this doesn't always work, and a manual flush of the cache may be in order.  This can be done as part of your existing execution steps, just put the following lines in at the end of the command:


ksc_connect_dest_server DEST_ENV="KINTANA_SERVER" 

cd $PPM_HOME/bin
./ A 


If you are already making a connection to the KINTANA_SERVER, you can exclude the ksc_connect and ksc_exit commands and just include the other two lines in before your existing ksc_exit.  This also assumes you have an environment variable defined called PPM_HOME that points to the root directory of where PPM is installed.

Established Member.. Utkarsh_Mishra
Established Member..

Re: Timer in execution step

Try these if it work..


  1. Add one more SQL exectuion step and just put "SELECT 'SUCCESS' from DUAL"

  2. Else at the end of your command call sleep using

    ksc_local_exec sleep 2


Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
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.