| || |
What is Best Policy for Actions
From the attached screen shot you can see that there are more than one step (information to be entered)
What is the best policy / convention to create the actions
Should I create an action for each step,
One action, for the whole process?
Re: What is Best Policy for Actions
I'd call that one "action" like 'AddSiteContact' or whatever it is that does. One per functionality/application screen is generally what I go for. Depends on the application.
I just do it with function libraries rather than actual actions, but that's another topic we've got plenty of threads on.