Configuring Attributes for Route Notifications

Open the Run MQL window:
1. From the compass, select Collaboration and Approvals.
2. In the navigation pane, click Utilities > Run MQL.
To run an MQL command, enter the command in the MQL Command box and click Run or press Enter.
To set the context for the MQL session, run this command:
```
set context user creator;
```

To modify the eService Trigger Program Parameter object, run this command:

modify businessobject "eService Trigger Program Parameter" <NAME> <REVISION>
     "eService Program Name" <PROGRAM>
     "eService Method Name" <METHOD>
     "eService Sequence Number" <SEQUENCE>
     "eService Program Argument 1" <ARGUMENT>
     "eService Program Argument 2" <ARGUMENT>
     "eService Program Argument 3" <ARGUMENT>
     "eService Program Argument 4" <ARGUMENT>
     "eService Program Argument 5" <ARGUMENT>
     "eService Program Argument 6" <ARGUMENT>
     "eService Program Argument 7" <ARGUMENT>
     "eService Program Argument 8" <ARGUMENT>
     "eService Program Argument 9" <ARGUMENT>
     "eService Program Argument 10" <ARGUMENT>
     "eService Program Argument 11" <ARGUMENT>
     "eService Program Argument 12" <ARGUMENT>;

where:

<NAME> is the name of the object
<REVISION> is the revision of the object
The remainder of the command adds these attributes:


Attribute Name	Description	Example
`eService Program Name`	JPO name	emxNotificationManager
`eService Method Name`	JPO method name	createNotification
`eService Sequence Number`	Used to order the program executions when more than one notification object is found. Route notifications should be executed last, so set this number high, for example, 100.	100
`eService Program Argument 1`	Object id used to evaluate embedded select clauses and added to the message as a URL	${OBJECTID}
`eService Program Argument 2`	To list (semicolon separated list of users to be notified)	$<from[Route Task].to.owner>
`eService Program Argument 3`	Cc list (semicolon separated list of users to be notified)	Same format as Argument 2
`eService Program Argument 4`	Subject string key or the string itself	Varies by notification object.
`eService Program Argument 5`	Body string key or the string itself	Varies by notification object.
`eService Program Argument 6`	Property base file name (this argument must be blank if not passing keys in arguments 4 and 5)	emxFrameworkStringResource
`eService Program Argument 7`	To select clauses (semicolon separated list of select clauses that result in users added to the To list)	Select clause resulting in a list of users
`eService Program Argument 8`	Cc select clauses (semicolon separated list of select clauses that result in users added to the Cc list)	Same format as Argument 7
`eService Program Argument 9`	Filter where clause used to determine if the email should be sent or not (only use double quotes in the where clause)	Varies by notification object.
`eService Program Argument 10`	URL suffix (all URLs embedded in the message body will be appended with this string)
`eService Program Argument 11`	From agent (optional argument to give the user the notification is sent from (the default is the context user)
`eService Program Argument 12`	Id select clauses (semicolon separated list of select clauses that result in ids of objects that are added to the message as URLs). If this argument is given then the objectId from argument 1 is not added to the message.