I have three occasions where I've had to use a conditional decision to set records management properties on one of a variety of records types in the same process.  Frequently the same organization creates multiple record types.  Since we are not using the regimented "record series/record folder" structure, we can have multiple record types in the same, department specific, folder structure.  When the record is created and a document type is selected, the cutoff instruction and retention schedule is logically known.  Having to create a pointless conditional decision that tests for specific values and then the branch uses an activity that matches the conditionally tested variable is very frustrating.  The field in the template says "State Retention Schedule - Rule 134A". The rule is defined as "State Retention Schedule - Rule 134A".  It would be a lot less work, and much less error prone, to simply use the value.