PerfectApps™ Help Guide

If you want to set a field state (normal, hidden, read-only and disabled) based on a workflow stage or role, do not use the Set State behavior command. Controlling field states in this manner will require extensive behavior creation on your part. To control field state based on actions occurring within the app,  behaviors are more appropriate.

PerfectApps offers options related to field state control without the need of behaviors. See Limiting User Access to App Fields.

Do not use behaviors to manage conditions that can be controlled on the Properties panel.

Many app objects offer properties that manage data input, making additional behaviors unnecessary. For example, a Text Input object allows you to specify the type of data input (e-mail, alpha, numeric). Additionally, a numeric input object can have minimum and maximum values configured on the Properties panel.

However, in certain circumstances it may be necessary to modify the default properties of an object such as position, size or colors using behaviors. Use the Set Property command to manage this.

Special behavior commands can efficiently manage in a single command what would otherwise require a sequence of simple commands.

For example, the Check Mandatory command allows you to manage required field checking with just the one command rather than using a sequence of Branch ('if') commands.

In most cases (with the exception being the implementation of notifications), avoid using behaviors to manage workflow. Although behavior commands are used on workflow paths, most workflow logic should be handled through the workflow diagram.

For more information, see the Adding Workflow topics.