Hi Murni

Found this in some customers.

It looks like the query used to draw the pipeline, performs a query using SQL “like”

If you have two or more stages in your oppo_stage values that contain the same text in the code (capt_code), you will have duplicate stages in the pipeline.

The only Workaround I found in this version is change the stages to avoid these duplicates.

Wonder this has been corrected in later versions.

I do have Approved and NotApproved, and I have use it a lot in my workflow. Do you know which view the pipeline use?

I do have Approved and NotApproved, and I have use it a lot in my workflow. Do you know which view the pipeline use?

HI Murni.

Not really, as far I know this is hard coded. 

I know that changing oppo_stages could be a nightmare, as the oppo_stage could be referenced in a lot of places.

This query would show in what rules action is used the field oppo_stage, so you can easily check:

select * from vWorkflowActions where WkAc_Field = 'oppo_stage'

This query also would show you in wich rules the field oppo_stage is used in the javsscript condition (transition rules) or where clause (escalation rules):

select * from vWorkflowRules where WkRl_JavaScript like '%oppo_stage%' or WkRl_WhereClause like '%oppo_stage%'

Hope this help if you decide change one of the oppo_stage codes.