Skip to main content

Enactor Tool Kit

State

This section describes the functionality of a State action. This state will not have a User Interface, and in general will not raise any events, other than those triggered by the platform itself (e.g. StateEntered, or Exception).

Properties

PropertyValue
Class NameThis 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.
CommentsThis 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 IDThis indicates the ID of the next state in the process flow, e.g. NewUser.
EventsThis indicates the events 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 event, e.g. OKPressed.
Unused - a tick indicates that the event is unused by the action.
Flow Page OptionsThis 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.
InputsThis 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.
NameThis indicates the name of the action in a more readable format, e.g. Remove User.
OutputsThis 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.
ParametersThis 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.
Respond to View Events?This is a flag which is selected from a drop down list, i.e. true or false.
Single Instance?This is a flag which is selected from a drop down list, i.e. true or false.
State DataThis indicates the state required for the selected action. Double-clicking on the value field will bring up a table which will identify for each state data the following:
Name - the name of the state data, e.g. enactor.administration.activityLog.ViewEntity.
Type - the type of the state, e.g. java.lang.Boolean.
Transient - a tick indicate that the selected state data is transient.
State IDThis is the ID of the state, e.g. DuplicateLevels
URLThis is URL for the state, e.g. /Message/NonModalOK
  • 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.