27     Home  •  Help  •  M0  •  form  •  27

Application rules are not merely more advanced rules. They are rules that are used in workflow creation. These specialized rules are used in conjunction with custom forms created using FirstClass Designer, custom containers or container templates created by the administrator, and FirstClass scripting commands. Applications may also use custom columns and view properties, specific user groups and model Desktops. Before attempting to create and run Application rules, you must: •       have the Application Developer privilege enabled on the Group Privileges or User Info form •       have a full understanding of Send, Receive, and Advanced rules •       ensure what you are attempting to do cannot be done more simply using Send, Receive, or Advanced rules •       have a documented plan of what you want to do with this application •       have all associated attachments, forms, and containers created and tested in their functional locations on your system. Messages vs. items A message is an item that is delivered through the MTA. When to run the rule     Choose when to run this rule: Message Received Message Sent Message Read Item Deleted Item Opened Item Modified Item Edited Item Closed Run Manually    Use the options on the Command tab to determine when to run rule and from where it can be accessed. Conditions tab Actions tab Attachments tab Command tab Conditions tab The Conditions tab follows the same rules and conventions as Advanced rules. Top Actions tab The following actions are found on the Advanced Rule form and function in the same way as on that form. See the Advanced Rule form help for information about these actions: File in folder Generate Reply Redirect Reject Delete silently Modify subject Stop rule processing Forward Send pager message Send notification Send new message Turn approval on/off Turn unread flag on/off Turn automatic open on/off Turn protection on/off Set icon Set color Set priority Set sensitivity Set expiry period Suppress FC notifier Make rule log entry Actions 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 subscription 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. 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. Get confirmation Used to get input from the user.         Notes 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.         Notes 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. 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 Enter a 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 Enter help text about this rule, which will be displayed when users hover the pointer over the icon. Command enabled Choose when the toolbar rule will be available. Top