WebSphere Lombardi Edition 7.2 > Modeling processes > Basic modeling tasks
Implementing activities
When implementing activities in the Designer in Lombardi Authoring Environment, you have several options. The following table list the available options and provides a link to detailed information and procedures in the Advanced modeling tasks section.
Implementation option Description See... Service You can create the following types of services: Integration, Human, Ajax, Rule, and General System. The type of service you choose depends upon the requirements of the activity. For example, if an activity requires that managers enter data about their employees, you can create a Human service with a Coach. If an activity requires integration with an external system, such as a database, you can create an Integration service. Build services Nested process You can implement an activity using a nested BPD. Nested BPDs provide a way to encapsulate logically related steps within a process while retaining the high-level view of the parent process. Use nested processes Javascript You can write JavaScript to implement a step in your process and embed that script in an activity. Use embedded JavaScript External activity You can implement an activity using an external application, such as an Eclipse RCP or Microsoft .NET application. Use external activities SharePoint Forum If you are using WebSphere Lombardi Edition for SharePoint, you can also implement activities using a SharePoint Forum. WebSphere Lombardi Edition for SharePoint documentation for more information about this implementation option. You can make an activity conditional
When the implementation that you want to use has been created, such as a service, you can select it as outlined in the following steps:
- Click to select the activity that you want in the BPD diagram.
- Click the Implementation option in the properties.
Under Implementation, select the option that you want from the drop-down list.
For example, choose Lombardi Service if the implementation for the current activity is a Human Service with a Coach. (The preceding table describes each available option.)
Click the Select button to choose the implementation from the library.
If the implementation does not yet exist, click the New button to create it.
If you are following the procedures in Basic modeling tasks to build a sample BPD, some of the activities in the sample are implemented in the linked procedures in the preceding table. For example, the Enter Expenses activity is implemented with an underlying Human service and Coach.
If you choose Lombardi Service or External Activity for your implementation option, you need to specify additional Implementation properties as outlined in the following steps.
- (For services only) click the Clean Slate checkbox if you want to clear the runtime execution state of an activity after it is complete. By default, this option is disabled. Enable this option only when you do not want to store execution data (such as variable values) for viewing after the process has finished execution.
In the Task Header section, specify the following properties:
Subject Type a descriptive subject for the task that is generated in Lombardi Process Portal when you run the BPD. You can also use the Lombardi embedded JavaScript syntax (for example, <#=tw.local.mySubject#>) to express the subject. Narrative Type an optional description. You can also use the Lombardi embedded JavaScript syntax to express the narrative. For the following properties (in the Priority Settings section) you can click the JS button for an option if you prefer to use a JavaScript expression with predefined variables to establish the priority settings.
- For the Priority field, click the drop-down list to select one of the default priority codes: Very Urgent, Urgent, Normal, Low, or Very Low.
For the Due In field, you can enter a value in the text box and then choose Minutes, Hours, or Days from the drop-down list. (When you choose Days, you can use the text box after the drop-down list to include hours and minutes in your specification.)
You also have the option of using the variable selector next to the text box to choose an existing variable from the library. At run-time, the variable should reflect the value that you want for the time period. Be sure to select the option that you want from the drop-down list: Minutes, Hours, or Days.
For the Schedule field, click the drop-down list to select one of the options. For example, select 24x7 if you want 24 hours a day, seven days a week to be the time period in which the resulting tasks from the current activity can be due.
You can leave the Schedule, Timezone, and Holiday Schedule fields set to (use default). If you do, the work schedule specified for the BPD is used. See Set the work schedule for a BPD for more information.
- For the Timezone field, click the drop-down list to select the time zone that you want to apply to the tasks that result from the current activity. For example, you can select US/Pacific for end users who work in California.
For the Holiday Schedule field, you can leave the setting at (use default) or you can click the JS button if you prefer to use a JavaScript expression. Each Holiday Schedule is made up of a list of Dates.
If you choose JavaScript, you can enter either a String (or String-generated JavaScript) or JavaScript that returns a TWHolidaySchedule variable. If you use a String, then Lombardi looks up the Holiday Schedule by name according to those rules. If you use a TWHolidaySchedule variable, then Lombardi assumes that the holiday schedule is filled in appropriately. (Go to the System Data toolkit and open the TWHolidaySchedule variable to view its parameters.)
Parent topic: Basic modeling tasks