Route Entry to Group
This activity assigns a Laserfiche entry to a specified group. It can also:
- Assign a template to an entry.
- Populate a field.
- Adds or remove tags to or from an entry.
- Send an e-mail.
- Use wait conditions.
See the tokens this activity produces.
- Drag it from the Toolbox Pane and drop it in the Designer Pane.
To configure this activity
- Select the activity in the Designer Pane to configure the following property boxes in the Properties Pane.
- Activity Name
- Activity Description
- Routing Options
- Entry to Route
Note: If you have more than one connection profile for your workflow definition, the Connection Profile property box lets you specify which connection profile this activity will use.
Tokens for Route Entry to Group
The Route Entry to Group activity produces the following tokens.
Note: If a group's Display Name is not set, the value for the group's Account Name is used for the Group_Display Name token instead.
| Name | Description | Sample Syntax* |
|---|---|---|
| Group_Id |
The Laserfiche ID number of the group specified in the Route Entry to Group activity. Note: For LDAP and Windows groups, the ID token is replaced by the group's SID. For Laserfiche users, the ID token is replaced by the group's ID, not their SID. |
%(RouteEntrytoGroup_Group_Id) |
| Group_Display Name | The display name of the group specified in the Route Entry to Group activity. | %(RouteEntrytoGroup_Group_Display Name) |
| Group_Account Name | The account name of the group specified in the Route Entry to Group activity. | %(RouteEntrytoGroup_Group_Account Name) |
| Group_E-mail | The e-mail address of the group specified in the Route Entry to Group activity. | %(RouteEntrytoGroup_Group_E-mail) |
| Group_Is Group | Whether the group specified in the Route Entry to Group activity is a group. This token can have one of two values: True or False. | %(RouteEntrytoGroup_Group_Is Group) |
| Group_Qualified Name | The unique identifying name of the group specified in the Route Entry to Group activity. | %(RouteEntrytoGroup_Group_Qualified Name) |
| Group_Working Folder | The working folder for the group found by the Route Entry to Group activity. The working folder is the folder specified in the Destination tab of the activity. | %(RouteEntrytoGroup_Group_Working Folder) |
| Group_Default Folder | The default folder for the group specified in the Route Entry to Group activity. | %(RouteEntrytoGroup_Group_Default Folder) |
| Group_Managers E-mail | The e-mail address(es) of the manager(s) of the group specified in the Route Entry to Group activity. If the group has more than one manager, then the managers' e-mail addresses will be listed as a multi-value token. | %(RouteEntrytoGroup_Group_Managers E-mail) |
| RoutedEntry_Name | The name of the routed entry. | %(RouteEntrytoGroup_RoutedEntry_Name) |
| RoutedEntry_Id | The Laserfiche ID number of the routed entry. | %(RouteEntrytoGroup_RoutedEntry_Id) |
| RoutedEntry_Path | The folder path of the routed entry. | %(RouteEntrytoGroup_RoutedEntry_Path) |
| RoutedEntry_FullPath | The folder path of the routed entry, including the entry's name in the path. | %(RouteEntrytoGroup_RoutedEntry_FullPath) |
| RoutedEntry_Repository | The repository the routed entry is in. | %(RouteEntrytoGroup_RoutedEntry_Repository) |
| RoutedEntry_Server | The Laserfiche Server that contains the routed entry. | %(RouteEntrytoGroup_RoutedEntry_Server) |
| RoutedEntry_Guid | The GUID (Globally Unique Identifier) of the routed entry. | %(RouteEntrytoGroup_RoutedEntry_Guid) |
| RoutingFolder_Name | The name of the folder the Route Entry to Group activity moved the entry into. | %(RouteEntrytoGroup_RoutingFolder_Name) |
| RoutingFolder_Id | The Laserfiche ID number of the folder the Route Entry to Group activity moved the entry into. | %(RouteEntrytoGroup_RoutingFolder_Id) |
| RoutingFolder_Path | The folder path of the folder the Route Entry to Group activity moved the entry into. | %(RouteEntrytoGroup_RoutingFolder_Path) |
| RoutingFolder_FullPath | The folder path of the folder the Route Entry to Group activity moved the entry into, including the folder name in the path. | %(RouteEntrytoGroup_RoutingFolder_FullPath) |
| RoutingFolder_Repository | The repository that contains the folder the Route Entry to Group activity moved the entry into. | %(RouteEntrytoGroup_RoutingFolder_Repository) |
| RoutingFolder_Server | The Laserfiche Server that contains the folder the Route Entry to Group activity moved the entry into. | %(RouteEntrytoGroup_RoutingFolder_Server) |
| RoutingFolder_Guid | The GUID (Globally Unique Identifier) of the folder the Route Entry to Group activity moved the entry into. | %(RouteEntrytoGroup_RoutingFolder_Guid) |
| Event Initially Satisfied | Whether the wait condition specified in the Route Entry to Group activity was initially satisfied. This token can have one of two values: True or False. | %(RouteEntrytoGroup_Event Initially Satisfied) |
| Event Duration | How long it took for the activity's wait condition to be satisfied. | %(RouteEntrytoGroup_Event Duration) |
| Event Id | The event ID for the activity's wait condition being satisfied. | %(RouteEntrytoGroup_Event Id) |
| Event User | The user who satisfied the activity's wait condition. | %(RouteEntrytoGroup_Event User) |
| Event User SID | The SID (Security Identifier) of the user who satisfied the activity's wait condition. | %(RouteEntrytoGroup_Event User SID) |
| E-mail.Reminder Count | How many times the e-mail has been resent with the e-mail escalation feature. This token is only available when configuring an e-mail within a Routing activity. | %(E-mail.Reminder Count) |
| Parent | If an entry and the folder it is in (its parent folder) have the same field, this token represents the field value of the parent folder’s field. The token %(Parent:Fieldname) represents the value of a different parent field. These tokens can only be used with fields and are available only in the Fields tab of the Routing activities.
Note: You can also access all field tokens within the Routing activities. |
%(Parent) |
Note: The Routing activities also let you access fields that would normally only be available if you used a Retrieve Field Values activity. The syntax for these field tokens is: %(Fields.Field Name).
User tokens available if round robin is used
If you choose to route the entry round robin style in the Destination tab of the activity, the following tokens are also available for the user to which the entry was routed.
Note: If a user's Display Name is not set, the value for the user's Account Name is used for the User_Display Name token instead.
| Name | Description | Sample Syntax* |
|---|---|---|
| User_Id |
The ID of the user that the entry was sent to. Note: For LDAP and Windows users, the ID token is replaced by the user's SID. For Laserfiche users, the ID token is replaced by the user's ID, not their SID. |
%(RouteEntrytoGroup_User_Id) |
| User_Display Name | The display name of the user the entry was sent to. | %(RouteEntrytoGroup_User_Display Name) |
| User_Account Name | The account name of the user the entry was sent to. | %(RouteEntrytoGroup_User_Account Name) |
| User_E-mail | The e-mail address of the user the entry was sent to. | %(RouteEntrytoGroup_User_E-mail) |
| User_Is Group | Whether the user the entry was sent to is a group. This token can have one of two values: True or False. | %(RouteEntrytoGroup_User_Is Group) |
| User_Qualified Name | The unique identifying name of the user the entry was sent to. | %(RouteEntrytoGroup_User_Qualified Name) |
| User_Working Folder | The working folder for the user the entry was sent to. | %(RouteEntrytoGroup_User_Working Folder) |
| User_Default Folder | The default folder for the user the entry was sent to. | %(RouteEntrytoGroup_User_Default Folder) |
| User_Managers E-mail | The e-mail address(es) of the manager(s) of the user the entry was sent to. | %(RouteEntrytoGroup_User_Managers E-mail) |
*The "RouteEntrytoGroup" portion of the syntax changes to match the activity's name as specified in the Activity Name property box. Note that all non-alphanumeric characters, except underscores, are removed from the name. For example, if you rename the activity Move to: Group *A*, the syntax for the RoutedEntry_Id token will be %(MovetoGroupA_RoutedEntry_Id).
Note: The Routing activities create extra tokens while running that are used internally by the activity. These tokens appear in the Tokens tab of the workflow's instance details if you use the Track Tokens activity.
