Harvest

 View Only
  • 1.  Allow comments for Promote and Demote processes

    Posted Jun 09, 2017 03:47 PM

    Customer needs to specify a comment everytime the promote and demote process is used. It is possible to acchieve this? Similar to this, from a particular Project State we define multiple Promote or demote processes (based on customer workflow) but no matter which Process is used, Harvest always write this action as a promote or demote in HARPKGHISTORY table (But not able to identify whay promote or what demote process was used). 

     

    What alternatives exist to be able to identify them and to be able to use them in a report for example.

     

    Thanks for your help.

     

    Best regards,

    JOHN



  • 2.  Re: Allow comments for Promote and Demote processes

    Broadcom Employee
    Posted Jun 12, 2017 02:49 PM

    This would be a good enhancement request.  Currently the "Promote Package" and "Demote Package" processes in Workbench and from the command line "hpp" and "hdp" utilities do not provide a way to include a description, or the name of the process that was used.

     

    The promote and demote descriptions could be written to a custom form attached to the package.  But Harvest would not have a way to enforce that this is done every time.

     

    Another way would be to create a script that would accept a package name, process name, and description, write the needed information to a log file and then execute a "hpp" or "hdp" command to complete the promotion or demotion.  The key would be to make sure the "allow additional input parameters" checkbox is checked so that the user can type in their description when executing the UDP.

     

    Let me know if this makes sense and might be helpful.

     

    Thanks

     

    Melinda Skelton

    CA Technologies Support Team



  • 3.  Re: Allow comments for Promote and Demote processes

    Posted Jun 21, 2017 05:26 PM

    Hi Melinda, thanks for your replay.

     

    Based on your comment, the description variable will be saved on a log file, not in the database, am i wrong? Do you have any simple script sample in order to achieve something like this?

     

    Thanks for your help again.

     

    Regards,

    JOHN