![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
If you have not already done so, install the sample project as previously described in Installing the Forms Tutorial Solutions Project.The Claims Process business process is used to process an insurance claim for an accident. Examine the process in the Process editor.When you open the sample application Claims Process No Forms, a graphical representation of the business process is displayed in the process editor.
•
•
• A diamond icon represents a gateway, that is, a point where the process flow is determined by whether or not a certain condition is met.
The icons used in the TIBCO Business Studio Process Modeler are Business Process Modeling Notation (BPMN). For more information about this standard see the TIBCO Business Studio Process Modeling User's Guide and the http://www.wfmc.org and http://www.bpmn.org web sites.
The first time a form is opened, a warning pops up to inform you that “The customized form is no longer being automatically kept in sync with the activity interface.” This is because opening a form, rather than simply previewing it, causes the default form to become a customized form. For the tutorials in this chapter, we customize forms rather than using default forms, so ignore the warnings and click OK when you open a given form for the first time.There are two main tasks displayed in the Capture Claim business process: Capture Claim and Interview Witness.To compare them in the form editor, open the Interview Witness form the same way you opened the Capture Claim form:
1. Figure 3 Form Open.
Figure 4 Capture Claim Form,Design Page
The GWT Preview tab is used to see how the form looks like at runtime. For an explanation of the Design tab, which is used for form modeling, and the preview tabs, which are used to preview and test the form, see The Design Tab and Preview Tabs.Figure 5 Capture Claim Form, GWT Preview Page
1. Figure 6 Interview Witness Form, Design PageBusiness processes modeled with TIBCO Business Studio generally include elements called user tasks and gateways. In this task, examine the user tasks and gateways in the sample business process.The two main user tasks in the sample business process are the Capture Claim task and the Interview Witness task, which differ in the kinds of user task parameters that are associated with some of the fields on these forms.The Capture Claim user task captures information about the customer, such as name and phone number, along with information about the accident, such as a description, the time it occurred, and whether any third party was involved. It appears at the beginning of the process, before any data have been collected.
1. Open the Claims Process No Forms in the Process editor.
2. Select the Capture Claim task.
3. In the Properties view below, select the Interface tab.If you want to remove any explicitly associated data, select the No interface data association required check box. By default, this option is cleared. If you select this check box, the text in the table below is set to [No Process Data].You can keep the No interface data association required check box cleared as the user task needs to be associated with the parameters.The Capture Claim is the first user task in the business process and has only Outbound Parameters. This is because when the user task begins at runtime, no data is yet gathered for the business process.The Interview Witness user task is associated with a form that captures information provided by the witness, including a description of the accident. It is provided with data that were gathered in the Capture Claim form, in addition to having data fields for new information. To see the task parameter mode:
1. Open the Claims Process No Forms process in the Process editor.
2. Select the Interview Witness task.
3. In the Properties view below, select the Interface tab.You can keep the No interface data association required check box cleared.The interface of the Interview Witness user task includes a mixture of In, Out, and In/Out parameters:
− The Inbound Parameters are associated with data that is already specified in the Capture Claim form.
− The Outbound Parameters are associated with fields that collect new data on the Interview Witness form.
− The Inbound/Outbound Parameters are associated with fields that can be revised on the Interview Witness form from the values that were previously specified on the Capture Claim form.These parameters provide information gathered on the Capture Claim form that is helpful to the interviewer performing the Interview Witness user task:
− Time of the accident, based on the value of the AccTime data field
− Customer Description of the accident, based on the value of the AccDescription data field
− Witness Name, based on the value of the WitName data field
− Witness Phone number, based on the value of the WitPhone data field.The data for these fields appears on the form (in the appropriate form fields) when the Interview Witness form shown in Figure 10 is opened.
4. Look now at the Interview Witness form detail.Figure 10 Interview Witness Task, Form DetailIn mode These parameters are bound on the Interview Witness form to form fields that are disabled for editing. In this tutorial, these fields are:
− AccTime (value appears in the Accident Time form field)
− AccDescription (value appears in the Accident Description form field)In/Out mode These fields are editable and in this tutorial they are:While their initial values are provided by the Capture Claim user task , the name and phone number of the witness may have changed from what they were when the Capture Claim user task was performed. Because they are In/Out parameters, their current values appear when the Interview Witness form opens, but the interviewer can edit those values if necessary.Out mode Two additional user task parameters in the Interview Witness user task are defined as Out mode parameters only are:
− WitDescription (Witness Description), which is the witness’s description of the accident to be specified on the form during the interview
− WitStatus (Witness Status), which is the status of the witness and is set programmatically based on buttons clicked by the interviewer.Note how Out mode user task parameters correspond to In/Out mode form parameters. This is necessary to allow the form to be opened and saved multiple times. If the form parameter was Out mode, you would lose the previously typed text if you subsequently reopened the form before marking the work item as complete.
• The first gateway, after the Capture Claim user task, is determined by the amount of the claim. If the claim is for a sum less than $500, then the process flow continues directly to the End Event. However, if the claim is for $500 or more, then the process flow continues to the next gateway.
• The second gateway is based on whether a witness is available to be interviewed; that is, if the Witness Available check box is selected on the Capture Claim form. If so, the process flow continues to the Interview Witness user task. If not, the process flow continues to the End Event.
• The third gateway is determined by whether the witness is to be interviewed again. If the interviewer clicks Completed, the process proceeds to the End Event. If the interviewer clicks Failed - Try again, the process returns to the Interview Witness user task. But if attempts to contact the witness have failed repeatedly, the interviewer needs to click Failed - Do not try again, and the business process proceeds to the End Event without the witness’s description having been captured on the form.
For more about how to use gateways in a business process, see TIBCO Business Studio Process Modeling User's Guide.In addition to one vertical pane containing all the controls for the user task parameters, the generated form contains a message pane for displaying validation error messages and a horizontal pane for the Cancel, Close, and Submit buttons.
• Customer Information Controls that gather information about the customer making the claim.
• Accident Information Controls that gather information about the accident.
• Third Party Information Controls that gather information about another person involved in the accident, if any.
• Witness Information Controls for capturing contact information for a witness to the accident, if any.
1. Click the Design tab for the Capture Claim form on the Form Designer so that the form is visible in the Form Designer.Figure 11 Show/Hide the Palette
b. Select Window > Show View... > Palette to open a Palette View that is shared between all open graphical editors.
3. Figure 12 Add New Pane: No Location Selected
− If you click with the mouse over the highlighted drop zone above the current pane, the new pane will be placed above the current pane.
− If you click with the mouse over the highlighted area inside the current pane, the new pane will be nested within the current pane.
− If you click with the mouse above the current pane without a highlighted drop zone showing up, the new pane will be placed under the current pane.
Hover the mouse over various areas on the form to see these visual signs. Experimenting with this functionality now will help you save time later and avoid accidentally placing form objects in unwanted positions. You can cancel the object placement operation and return the mouse to its normal function by hitting the Esc key at any time. Immediately after adding a pane, you can remove it by typing Ctrl+Z or clicking Undo Add Form Pane on the Edit menu.Figure 14 Untitled Panes Added
7. Click the Save icon to save the project.
Careful labeling at the pane level also allows you to use shorter labels for the controls. For instance, by using the label Customer Information for the pane, you can include controls within it labeled Name and Phone, instead of Customer Name and Customer Phone.
2. In the Properties View General tab of each of the untitled panes:
−
− Replace pane labels in the Label field.
Table 2 Name Labels
3. Once you have named and labeled the new vertical panes, drag each control to its appropriate pane and position the controls in the order in which they are listed. You can select multiple controls with Shift-Click or Ctrl-Click and drag at once.
1. Drag the following controls into the Customer Information pane:
d.
e.
g.
2. Drag the following controls into the Accident Information pane:
3. Drag the following controls into the Third Party Information pane:
4. Leave the following controls into the Witness Information pane:
a.
1. Click the Customer Name control.
The Required check box is already selected as the parameter CustName is defined as Mandatory at user task interface level.
2.
3. Add the following text to the Hint field for this control to illustrate the format that our application requires for phone numbers: Example (888) 888-8888.
4.
You want to require that a value be typed for either the Phone or the Email field, but both values will not be required. This functionality is best configured with a script, which will be presented in a later tutorial. You can leave the Required check box cleared for both Phone and Email.
5.
6. Make sure that the Required check box is selected, so that a value is required at runtime for this field.
Since you placed the above controls in a pane labeled Customer Information, it is not necessary to repeat the word Customer in the label for each control. This is generally a good practice because it results in a cleaner, easier-to-use form.
7.
8. The Label and Required properties for the Guardian Name field do not need to be changed. However, you want to add the following text to the Hint field for this control to explain that a guardian’s name must be supplied if the customer is under 21 years old: If age is less than 21.
9. Make sure that the Required check box is selected, so that a value is required at runtime.
10.
11.
12. Add the following text to the Hint field for the Witness Phone control to illustrate the format that our application requires for phone numbers: Example (888) 888-8888.In this step, you will modify other properties of selected controls in order to enhance the functionality of the Capture Claim form. The type of control that is generated from user task parameters, for instance, depends upon the type of the data fields from which those parameters are derived. The eight basic types for data fields in TIBCO Business Studio result in the following control types:
Table 3 Data Field Types The first control you will modify is Date of Birth, which was generated as a Date-Time control. The customer’s date of birth has a bearing on the insurance claim but the time does not. Therefore, you will change the type for this control from Date-Time to Date.
1. The type of the Age field is Text, which doesn’t need to be changed. But you want the value for this field to be calculated dynamically at runtime based on the value specified for the Date of Birth field. This means that you do not want a value to be typed by the user.To make the field uneditable, clear the check box for the Enabled property for this control.Figure 16 Making the Field CustAge Uneditable
2. The type of the Personal Injury field is Text and you will change it to Radiogroup, which ensures that a valid value will be specified, since the value will be chosen from among those you provide.
3. For a Radiogroup control the values of the radio buttons must be configured.
4. Specify the following values and labels, clicking the + (plus) next to each value/label pair once it is specified:
−
−
5. The control type of the Customer Description field is Text. Change it to Text Area in the General tab to allow space for a longer description.Click the Properties tab of the Properties View and type the values of 4 for Rows and 60 for Columns.
6. The type of the Insurance Company field is Text and you will change it to Optionlist, to ensure that a user will choose among the names that you provide.Click the optionlist for Control Type and select Optionlist. For an Optionlist control the values in the list must be configured.
7. Click the Properties tab for the Insurance Company control and type the following values and labels, clicking the Add button as needed next to the last value/label pair to add space for an additional empty optionlist value:
8. If there are any extra labels, remove them by clicking on the Delete (X) button.In this section you will begin configuring this functionality by binding the Visible property of the panes to corresponding parameter values. Binding can be added either from the General tab using the Add Binding iconor from the Mappings tab of the Properties view.
Bindings are created automatically between the controls and the parameter values when form is generated; for example, a two-way binding between Customer Name(CustName) parameter value and Name(CustName) control value. When a parameter value changes, the control value is updated automatically, and vice versa.
1. Click the Third Party Information pane so that its Properties View is displayed.
2. Figure 18 Add Binding to Configure Pane VisibilityThis will open Create Binding dialog.
3. The Select Binding Endpoint page opens.Figure 19 Select Binding Endpoint Page
4. Select Third Party Involved (ThirdPInvolved) parameter that will be bound to Visible property of Third Party Information pane.
5. Click Finish.Note that the binding icon has changed in the Properties View next to the Visible check box to denote that a binding is present.Figure 20 Binding Created for the Visible Property
6. Click the Witness Information pane so that its Properties View is displayed.
7.
8.
9. Select the Witness Available (WitAvailable) parameter that will be bound to Visible property of Witness Information pane.
10. Click Finish.Perform the following steps to bind the Visible property of the Third Party Information pane to the Third Party Involved (ThirdPInvolved) parameter value using the Mappings tab:
1. Click the Third Party Information pane so that its Properties view is displayed.
2. Click the Mappings tab in the selected pane’s Properties view.
3. In the Mappings tab view, the right pane displays the bindable properties of the selected Third Party Information pane. The left pane displays the bindable source properties to which the target elements are bound. It displays the Third Party Information pane and its ancestors all the way up to the containing form and also includes the form parameters and data fields.
4. Drag the Third Party Involved (ThirdPInvolved) parameter from the source tree and drop it over the Third Party Information pane’s Visible property in the target tree.
6.
7. Select is updated by Third Party Involved (ThirdPInvolved) option.
8. Click Finish.Figure 21 Adding Binding from the Mappings TabMake the following changes to the Interview Witness form:
2. Change the new pane’s Name property to witness_info_pane and the Label property to Witness Contact Information.
4. Change its Name property (root) to accident_info_pane and the Label property to Accident Information.
5. Drag the following controls from the Accident Information pane to the Witness Contact Information pane: Witness Name and Witness Phone.
− Witness Name into Name
− Witness Phone into Phone
8. Change the type of the Customer Description and Witness Description controls from Text to Text Area. On the Properties tab, specify values of 4 for Rows and 60 for Columns for each.
1. Select the button type Close in the Palette and drag it and drop between the Close and Submit buttons in the Navigation pane.Figure 22 Add a Button
− Cancel leave as is
− Close Change label into Failed - Try Again
− Close (the new button) Specify label as Failed - Do Not Try Again
− Submit into Completed
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |