Discussion

3
Replies
7770
Views
Tony Tung (tungt)
PEGA
Lead System Architect
Pegasystems Inc.
AU
tungt Member since 2013 7 posts
PEGA
Posted: March 17, 2015
Last activity: March 17, 2015
Posted: 17 Mar 2015 0:36 EDT
Last activity: 17 Mar 2015 20:07 EDT
Closed

Naming Convention

The suggested naming convention in the lesson Tips on Developing an application for flow action states that:

"Flow Actions - Use a verb and noun convention for flow actions, for example, Approve Correspondence. A flow action can reference other records. When associated with certain activities, data transforms and validation records, prefix the flow action name with:

  • Pre — if used with a pre-activity or data transform; for example, PreApproveCorrespondence
  • Post — if used with a post-activity or data transform; for example, PostApproveCorrespondence
  • Val — if used with a validate record; for example, ValApproveCorrespondence"

I don't think this convention is workable, because a flow action can have pre-action, post-action, and/or validation.  So what do you call a flow action that have all of them?  PrePostValApproveCorrespondence?  That's horribly clumsy.  Also, the pre-action, post-action and validation can be added or removed after the flow action is created and it is not that easy to change the name of a rule once it is created.  A convention like this won't work.

Pega Academy
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.