Clarity

  • Private Community

  • 1.  Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 08, 2015 05:36 AM

    Hello,

    I am getting the process status to change to "Error" instead of "Aborted" when cancelling a running process in Clarity PPM v12. The steps to replicate are below.

     

    Has anyone come across this issue and what was the resolution please?

     

    In "Programmes & Projects" section, choose a project, select the "Processes" tab.

    Click on "available" and select a process. Click on "start".

    Click on "initiated", select the running process and click "cancel process". Click "yes".

    The window should close and take us back to the "initiated" screen and show that the cancelled process should have the "aborted" diamond symbol.

    However, the screen stays at the Click "yes".

    Have to come out of "Programmes & Projects" section all together and then go back in "Programmes & Projects" section and project to see the process aborted.

    Unfortunately, the process is displayed as "Error" not "Aborted".

     

    Thanks

    David



  • 2.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 08, 2015 05:59 AM

    Is there any error you see in the logs ?

     

    NJ



  • 3.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 08, 2015 06:06 AM

    Please check this -

     

    How To Cleanup Orphaned and 'Stuck' Processes

    Document ID:  TEC618549
    Last Modified Date:  10/4/2014
    ShowHide Technical Document Details            
    • Products                    
      • CA PPM
      • CA Governance, Risk ＆ Compliance Manager
    • Releases                    
      • CA PPM:Release:13.0
      • CA PPM:Release:13.1
      • CA PPM:Release:13.2
      • CA PPM:Release:13.3
      • CA PPM:Release:14.1
    • Components                    
      • CLARITY PPM APPLICATION ADMIN, STUDIO, XOG ＆ PROCESSES
       Description:Occasionally Process Engine would get stuck. There might be lots of orphaned processes that need to be cleaned up. There might also be processes in ABORTING state.Solution:This resolution is applicable to On-Premise Customers.
    If you are an On-Demand Customer and encounter the symptoms described above, please log a support case for further investigation.Before proceeding to clear up 'stuck' processes, restart the background (bg) services and wait some time to see if the 'ABORTING' processes finish as expected.
    1. In order to 'clean up' orphaned or stuck process data, please follow these steps:
      1. Stop the bg services.

      2. Clean orphaned process engines: ----------------------------- DELETE FROM bpm_run_process_engines WHERE end_date != NULL OR end_date <= sysdate 
      3. Clean orphaned process instances: ------------------------------ DELETE FROM bpm_run_processes WHERE process_version_id NOT IN (SELECT id FROM bpm_def_process_versions) 
      4. Change status of process instances "stuck": ----------------------------------------------- UPDATE bpm_run_processes SET status_code = 'BPM_PIS_ABORTED' WHERE status_code = 'BPM_PIS_ABORTING' 
      5. Start the Clarity service
    2. Please check if you have a large amount of process instances already completed.
      Go to Administration, Processes, Initiated tab and check how many are finished because they are completed or aborted.
      If there are too many, you may want to run the 'Delete Process Instances' job (this only removes process instances with status done or aborted)
      We recommend scheduling this job on a regular, recurring interval to remove old data.

     

    NJ



  • 4.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 08, 2015 06:06 AM

    Also, this -

    Aborting and deleting process instances

    https://communities.ca.com/message/5400929#5400929

     

    NJ



  • 5.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 08, 2015 06:17 AM

    You can try this, but not before having a word with Support -

     

    Error Processes to be removed

    https://communities.ca.com/message/107439216#107439216

     

    NJ



  • 6.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 08, 2015 06:19 AM

    Also, hope that you do this (as mentioned by Connie_Fu ) -

     

    CA Clarity Tuesday Tips - Process Maintenance

    https://communities.ca.com/message/105628128#105628128

     

    NJ



  • 7.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 08, 2015 08:12 PM

    Just to make it clear, the credit of that post should go to Jeanne Gaskill



  • 8.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 09, 2015 01:06 AM

     

     

    Correct ! Thanks Jeanne_Gaskill_CA_Clarity_Support

    NJ



  • 9.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Posted Jan 08, 2015 07:13 AM

    Thanks for your response.

     

    I can see there are 95629 completed processes, which may cause the problem?

     

    How do I run "Delete processes instances" job please?  I can delete all the "completed" processes manually from Administration>Processes> Initiated tab but I guess this is not the right way to do it

     

    Thanks

    David



  • 10.  Re: Stoping workflow process causes the process status to be displayed as "Error" not "Aborted"

    Broadcom Employee
    Posted Jan 08, 2015 07:48 AM

    Run the Delete Process Instance Job, that will delete the Process.

     

    Regards

    Suman