Enactor Tool Kit
Execute in Window
This section describes the functionality of an Execute in Window action.
Properties
| Property | Value |
|---|---|
| Action ID | This is the exact name of the action (no spaces), e.g. AddLocationIdFilter. |
| Class Name | This is the class name of the action, which can be selected from a drop down list, or entered by the developer, e.g. com.enactor.commonUI.list.processes.AddListFilterAction. |
| Comments | This is a text field which can contain additional information about the action. It is displayed as a tool tip when the action is hovered over with the mouse. |
| Default Next State ID | This indicates the ID of the next state in the process flow, e.g. NewUser. |
| Execute Process ID | This indicates the ID of the process to be executed, e.g. Maintenance/PromoEditPromotion. |
| Expected Execution Time (ms) | This numerical value is the expected execution time of the action in milliseconds. |
| Flow Page Options | This option enables the developer to produce a flow page diagram associated with the Process Diagram. The text can be entered/edited by double clicking on the value field for this property. The developer can also edit/view the Flow Page by selecting the flow tab when editing the process diagram. |
| Inputs | This indicates the inputs required for the selected action. Double-clicking on the value field will bring up a table which will identify for each input the following: - Name - the name of the input, e.g. enactor.coreUI.EntityName. - Type - the type of the input, e.g. java.lang.String. - Required - a tick indicates that the input is required by the action. |
| Name | This indicates the name of the action in a more readable format, e.g. Remove User. |
| Outcomes | This indicates the possible outcomes of the action.Double-clicking on the value field will bring up a table which will identify for each output the following: - Name - the name of the outcome, e.g. Success. - Unused - a tick indicates that the outcome is not used by the action. |
| Outputs | This indicates the outputs produced for the selected action.Double-clicking on the value field will bring up a table which will identify for each output the following: - Name - the name of the output, e.g. enactor.coreUI.ListCriteria. - Type - the type of the output, e.g. com.enactor.core.servers.IListCriteria. |
| Parameters | This indicates the parameters required for the selected action.Double-clicking on the value field will bring up a table which will identify for each parameter the following: - Name - the name of the parameter, e.g. enactor.coreUI.MessageBasename. - Value - the value of the parameter, e.g. com.enactor.maintenance.resources.UserMaintenanceMessages. - Type - the type of the parameter, e.g. java.lang.String. |
| Privileges | This indicates the privileges for the selected action, e.g. enactor.userMaintenance.Remove. |
| Session Management Type | This field determines the session management for the action (if any). It is selected from a drop down list, i.e. None, Make new session, Make session if one does not exist, Manages own session or Needs existing session. |
| Type | This indicates the type of action. It is selected from a drop down list. It is selected from a drop down list, i.e. Pause, Assign, Action, Execute Script, Call Process, End Process, Execute in Window, Execute Process or Call Web Process. |
Navigation Tips
- Double clicking on various parts of the action will bring up further information, e.g. on the name of the action will bring up the actual source code, on the Inputs will bring up the Inputs information.
- If a small light bulb appears adjacent to a property value, it means that Content Assist is available. By pressing the control key followed by a space, the standard Select Type dialogue will appear, enabling the User to search for the required file.
- For most types of actions, shift followed by double click on the Inputs will bring up the Parameters for that action.
- The User can switch between display types using the tabs at the bottom left hand side of the window. Source displays the process in XML format. Model displays the process in an easy readable, diagram format. Flow displays the flow page associated with the process.