Form tabs Conditions tab Actions tab Attachments tab Command tab Use this form to create an application rule for a workflow. Name the rule, enable it, and specify when it is to run just as you do for an advanced rule. Conditions tab The Conditions tab follows the same rules and conventions as advanced rules. Top Actions tab The actions that can be performed are the same as those on an advanced rule. The following actions are specific to application rules: Copy to folder Used to send a copy of the item to another container. Copying preserves all original attributes. Enter the path to the folder in the space provided. The path syntax is {DESKTOP}/{TYPED=##} where TYPED=## is the typed folder. Modify name Used in workflow to modify the From name of the item. This is useful when one message travels through various groups or departments and the original name may no longer be relevant at all steps. You can replace the name, or add a suffix or prefix to the original name. Create link Creates a membership to the item. Enter the path to the folder in the space provided. Play sound When the rule executes, a sound is heard. This can be used as a message notification, or more creatively within the workflow to alert users of another action. This action isn't available for received or sent messages. Enter the resource number of the sound. Open alert box Opens an alert box. Enter the box title and text and select the desired buttons for the alert. An alert box can be used to inform the user of a pending or ongoing action, to retrieve user input, or for other purposes. This action isn't available for received or sent messages. Get confirmation Gets input from the user. This action can occur anywhere in the action list and there can be multiple occurrences. They can also occur in any order. This means that a rule can perform some actions, be interrupted, and then continue processing after the confirmation has been accepted. Closing the window stops rule execution. Any fields collected by any of the actions will be retained and available to any subsequent actions. For example, if a field is entered on an earlier form by the user, and the same field ID appears on a later form, the user's input will be displayed in the later form. Some rules actions affect the later processing of other actions. You should avoid splitting these sets of actions across an Open Picker or Get Confirmation action, since these currently reset the action processor. The best way to avoid problems is to perform the user interface actions first and finish with the actions which perform operations on the store. Open picker This action interrupts rule action execution and opens a picker window. The selected object then becomes the rule target for the remainder of the action execution. This action can occur anywhere in the action list and there can be multiple occurrences. They can also occur in any order. This means that a rule can perform some actions, be interrupted, and then continue processing after the picker window has been accepted. Closing the window stops rule execution. Any fields collected by any of the actions will be retained and available to any subsequent actions. For example, if a field is entered on an earlier form by the user, and the same field ID appears on a later form, the user's input will be displayed in the later form. Some rules actions affect the later processing of other actions. You should avoid splitting these sets of actions across an Open Picker or Get Confirmation action, since these currently reset the action processor. The best way to avoid problems is to perform the user interface actions first and finish with the actions which perform operations on the store. Set object type This action is used to change a message to a document or vice versa. During a workflow it is much more convenient to work with editable documents than messages. Set form type If you have created a form to use with this application, it can be linked to this action. Set text field Used to change the contents of a text field. Set number field Used to change the contents of a number field. Set date field Used to change the contents of a date field. Transfer field Used to copy field content from either a form or the schema. "In object" refers to a field on a form. "In list" refers to a list item. "In layout" refers to a value you can set in the schema using FirstClass scripting (for example, you can set a starting serial number for a conference using PUT, then use an application rule to increment and copy that value to a form field using stationery). Transfer field to app doc Copies field data to the form defined as the app container document. Run a batch admin script Enter the text of the ba script. This rule can only be created from the administrator's account. Start helper application Enter the path to and parameters of the helper application. Top Attachments tab An attachment can be used as the basis for certain actions. For example, a reply with attachment uses the text, formatting, embedded pictures, and so on, of the attached object (typically a message or document). If you want to include an uploaded file, first attach it to a message or document, then attach the message or document to the rule. Top Command tab Sets the conditions of use/execution of manual rules. Add to toolbar Places the rule on the toolbar so it can be run manually by those with the appropriate permissions. Command icon Click to choose an icon for the toolbar display. Control-click for additional icons. Command name The name for the toolbar display. Show name If cleared, the rule will be identified by icon only and the name will be hidden. Tooltip text Help text for this rule. This help will be displayed when users hover their cursor over the icon. Command enabled When the toolbar rule will be available. Top