~~NOTOC~~
====== Compare Two Text Strings ======
Choose two [[Field|fields]] or build two [[Expression Builder|expressions]]. Then, select how you will compare them to each other.  If the comparison is true, the evaluation will pass.  If the comparison is false, the evaluation will fail.
===== Explanation =====
Evaluations have two [[Automation Trigger|automation triggers]] associated with them : Then and Else.  Actions under the "Then" automation trigger execute when the evaluation passes, and actions under the "Else" automation execute when the evaluations fails.

{{ ::action_evaluation_drop.png?direct |}}

Field comparison evaluations are used to execute a set of actions if two text values compare successfully, and another set of actions if they do not.

Example : Suppose an application contains a [[Table|table]] for Contacts with an [[Field Type - Address|Address]] field.  When a user creates a new Contact, the builder has determined that addresses in the state of Pennsylvania may not be accepted.  To accomplish this in the validate field automation trigger they would create a field comparison action and choose the State part of the Address field on one side of the comparison, enter the text "PA" on the other side, and choose "is equal to ( == )" for the comparison to use.  Then, use a [[Action Type - Show Error|show error]] action to show a validation failure when the State is PA.

===== Settings =====

{{ ::action_fieldcomparison.png?direct |}}
==== Choose a field or build an expression ====
Choose a field or build an expression to be compared.
==== Choose how to compare them ====
Choose how these two expressions will be compared to one another.

==== Choose a field or build an expression ====
Choose another field or build another expression to be compared.

==== Describe this action ====
Useful as a comment, this description will overwrite the automatically generated description in the [[Action Manager|Action Manager]].
==== Queue this action and children	 ====
When an action is [[Action Queue|queued]], the subsequent actions continue to process without it. Meanwhile, the queued action and its children process separately. Queue actions that you don't want a user to wait for.