Bhaskar has implemented a new naming convention that calls for users to include PRODI, PR0D2,...

One new benefit Bhaskar will gain by implementing this new naming convention is that he will be able to create a global product-specific scoring program that triggers off Program Status Changes with a Program Name constraint. This will help him score leads based on their engagement with different product lines across different programs. For example, he can create a trigger that fires when Program Status is Changed and Program Name contains PROD1, and then add a flow step that increases the score for PROD1 by a certain amount. Creating product-specific dynamic content or nurtures does not require this naming convention.