IFS 开发培训文档(Chapter-05)

Specifications and Guide LinesProduct/Project: Doc.No: Issued By: Date: Page:: R&D Training * Henry Zhong 2009-7-12 1(4) Title:Solution-Chapter 05Document Revision HistoryRevision Date By RemarksA1 2009-7-12 Henry Zhong CreatedList:Adding a state diagram1.Model changes2.Storage and Business logic3.Client DeveloperSolution – Chapter 05(Adding a state diagram)1Adding a state diagram1.1Select the DemoTrInvoice class in the model diagram for OrderEntry. Select the main menu item Browseand next chose the sub menu item State Diagram (Pressing ctrl+T also opens the state diagram view).1.2Add three states to the diagram Created, Cancelled and Paid. Also add a starting state to the diagram.Connect the start state to the state Created with a State Transition arrow. (To do this, select the StateTransition arrow from the tool box, and next drag and drop from the starting location to the end location.)Note: This will automatically assign the new records to the state Created at the beginning.1.3Then from the state Created add State Transition arrows to both Paid and Cancelled.1.4To add the event Cancel to the State Transition s from the states Created to Cancelled, select the StateTransition and right click to get the pop-up menu. There will be only one menu item which is theSpecification item. Select this menu item.1.5Add the event name Cancel for the Event, apply and close. Add the even Pay to the State Transition betweenCreated and Paid in this same manner.Note: There is no specific end state as all the states with no out going events are considered to be end sates.1.6Add a …note text‟ for LU DemoTrInvoice class, like this:2Storage and Business logic2.1Adding a state diagram will require an additional column in the table for DemoTrInvoice to store the object‟sstate.2.2Open IFS Design, next open the storage folder and merge the changes to the CRE file and save it. Create aUPG file, save and deploy the UPG file.2.3Then open the code for the DemoTrInvoice in the business logic. Note the changes from the lastly saved code.Merge all the functions related to the Finite State Machine. Then any additional code in the previousfunctions that have turned red or brown should either be merged or set to default.2.4Save and deploy the API and the APY.3Client Developer3.1Open demord.apl in the Developer. Select the window frmDemoTrInvoice and get the Outline.3.2Add the new column, named STATE to the frmDemoTrInvoice form and make sure that the “State Machine”check box is checked.3.3The way to change states of a record is to send the events that cause the state changes from the client. To dothis we need to add an RMB option for each event.3.4To add an RMB option, a menu needs to be added to the “Named Menus” section of a window. Look at thefollowing table for a compleat list of the manu names that can be used. These are from the named menusdefined in the application‟s popup menus section (a library item from ifsfnd.apl)3.5Add to the menu, menuFrmMethods to the Named Menus section of frmDenoTrInvoice window. (Right clickon the item Named Menus, and chose the Add Next level Option. Select the Menu option from that.)3.6Under this menu add the menu items correspondin g to the events of the state diagram. Namely “Cancel” and“Pay”.3.7To do this, select the Menu and right click. From the pop-up menu that appear, select Add Next Level option.Select the option Manu Item.3.8Add the following coding.3.9For each menu item code for the …Enabled When‟ and …Menu Actions‟ are needed to be added.3.10In the current situation the menu item is a State machine event. Hence the actual database event can beinvoked by sending the message PM_DataRecordStateEvent.Note: This message takes two parameters. One is a standard method parameter taking values likeMETHOD_Inquire, METHOD_Execute. The other one is the actual event name.3.11For Enabled When add the following code.Note: The METHOD_Inquire is indicating this is just a check for availability of this event for the current record. The reason for converting the event name (should be replaced with …Cancel‟ and …Pay‟) to a number is the SalSendMsg function only accepts numeric values for message parameters. The message handler of the message will do the reverse conversion where needed to identify the event.3.12Under Menu actions add the following line.Note: The third parameter is now METHOD_Execute, indicating now that the action should be executed and not just checked. There is no need to convert the event name here as the PostMessage function accepts the string parameter.3.13Save and Run the application.Note: You need to add new records as the previously created records will not have a state defined for them you will not be able to modify them. The new records will automatically be of state “Created”.3.14Check for the availability of the Menu Items …Cancel’and …Pay’. Both should be enabled for records in state“Created”. Then invoke “Cancel”, now the state will be changed to “Cancelled”. Then both menu items will be disables (as expected since “Cancelled” is an end state there are no available state transitions from it).Similar test can be done for “Pay” event on another “Created” record. Without the code in the Enabled when section all the menu items will be enabled all the time giving a false impression about the availability of an event.。