Destination rules are an important feature in the process design where it determines the person(s) that is assigned a tasks.

There are a variety of values that this dialog (shown below) can take.

I am not going to drive into the destination rule options settings as I covered that previously.  What I going to focus on is the values that you can put into each destination user dialog.

The dialog is somewhat cool as it is able to take both single values and list values (for multiple users).

For single values, it accepts the following:

• Role (This refers to the K2 role you define in the management console.  Roles allow you to specify users, groups or even SmartObject list methods.)
• Active Directory User or SQL User Manager user (if SQLUM is configured)
• Active Directory Group

Note that for the above, you can input the values in a variety of ways:

• User Browser pane in the K2 context browser window
• Manually type them in
• Retrieve from a SmartObject Load method
• Inline function which returns a singular value
• A process data field
• A singular element in a process XML field

For list values, it recognizes and accepts the following types:

• SmartObject List Methods
• XML Repeating Nodes
• Split inline function or any inline function that returns a string[] object

So if you have a list value type, the destination rule is smart enough to cycle through the list and adds them as individual task owners (which is very nice!).

Now the last thing is the values that you can specify (singular or list).  The destination rule is able to resolve the following formats:

1. K2:<Domain>\<User>
2. K2SQL:<User> (This is if SQLUM is configured)
3. <Domain>\<User>
4. <User> (This resolves to the machine domain user
5. <User>@<domain UPN suffix>.  e.g. mike@denallix.com (This relies on the UPN value configured for the user account)

As you can see, it is pretty flexible in the way it resolves the user.  The UPN suffix method was pointed out to me by Pat/Tor and is really cool (Thanks guys!).

I hope this little article helps you to better leverage the capabilities of the destination rule dialog a bit better.  Cheers!