miUML Metamodel State Subsystems Interface / mint.miUMLmeta.td.11
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
Still loading...
ABCDEFGHIJKLMNOPQRST
1
Call (organized by subsystem)Parameters & examples (see also comments in code)Return ValueDescriptionStatusRequested byReply to requestComments / Issues
2
[ ] = may be omitted, x | y = choose x or yYour nameMy responseAny comments or issues you may have with requested or existing features
3
Event
4
UI_new_signaling_eventevent_name, state_model, domain, [ev_num]
ex: 'open', 'door', 'elevator'
-- 'door' is the name of a class lifecycle state model
ex: 'customer arrived', 5, 'store management'
-- 5 is the rnum for an assigner state model
event_number, event_idCreates a new Signaling Event on the specified Lifecycle. An Event ID will be generated along with an Event Specification number, if none is specified. Both the assigned Event.ID and Event Specification.Number will be returned. If a desired Event Specification number is specified, it will be used unless the number is already taken, in which case any available number will be assigned.

Also a Non-Transition Response of 'Can't Happen' is created by default for each State in the State Model.
Tested OK
5
UI_new_creation_eventevent_name, class_name, to_state, domain, [ev_num]event_number, event_idDefines a new Creation Event on the specified Lifecycle. An Event ID will be generated along with an Event Specification number, if none is specified. Both the assigned Event.ID and Event Specification.Number will be returned. If a desired Event Specification number is specified, it will be used unless the number is already taken, in which case any available number will be assigned.

Tested OK
6
UI_set_creation_stateclass_name, domain, new_to_statenoneChanges the State where an instances are created with the existing Creation Event.Tested OK
7
UI_new_polymorphic_eventevent_name, superclass_name, domain, [gen_rnum], [ev_num]
ex: 'Start', 'Connector', 'Gas', 2, 12
Poly event spec '12:Start' is defined on the 'Connector' superclass and delegated down Generalization R2 only.
ex: 'Start', 'Connector', 'Gas'
Poly event spec '<n>:Start' is defined on the 'Connector' superclass and delegated down ALL Generalizations where 'Connector' is the superclass.
event_number, event_idCreates a Polymorphic Event Specification, a Delegated Event for the specified Superclass and an Inherited Effective Event on each Subclass reached through the supplied Generalization. The user can further delegate a subclass event if desired by further delegating it in a separate operation.

If the specified Class plays multiple Superclass roles (is the root of a compound Generalization), the event will be delegated down each Generalization. If an Rnum is supplied, however, the event will be delegated down the specified Generalization only.

The Event Spec number and Local Delegated Event ID is returned.

Tested OK
8
UI_delete_eventstate_model, event_name, domainnoneDeletes an Event Specification and any corresponding Events. If this is a Monomorphic Event Specification, then only one Event will be deleted. Otherwise, it is polymorphic and all descendant Events (Inherited / Delegated) will be deleted.

Tested OK
9
UI_delegate_eventevent_name, evspec class name, domain, [delegation class name], [delegation rnum]noneDelegates an Effective Signaling Event so that it is handled in the Subclass Lifecycle State Models of the specified Generalization. If no Generalization is specified, the Event is delegated down all Generalizations rooted in the specified Class.

Tested OK
10
UI_undelegate_eventevent_name, evspec class name, domain, delegation class name, [delegation rnum]noneMigrates a Delegated Event to an Effective Event. If the specified Event is a Local Delegated Event (on the same class as its Polymorphic Event Spec), and un-delegation would result in no Inherited Effective Events descended from the Polymorphic Event Spec, the Polymorphic Event Spec is migrated to Monomorphic.

Tested OK
11
UI_add_param_to_state_sigparam_name, type, state_name, state_model, domainnoneDefines a new State Model Parameter and associates it with an existing State Model Signature. An attempt is made to update each of the Event Signatures associated with any Signaling Events on Transitions leading into the State.

Tested OK
12
UI_add_param_to_event_sigparam_name, type, event_name, state_model, domainnoneDefines a new State Model Parameter and associates it with an existing Event Signature. An attempt is made to update any State Signature on the destination of any Transition triggered by an Event defined by the Event Specification.

Tested OK
13
14
State
15
UI_new_deletion_pstatestate_name, class_name, domainnoneCreates a new Deletion Pseudo State in the specified Lifecycle State Model.
Tested OK
16
UI_new_statestate_name, state_model, domain, [snum]state_numberCreates a new State in the specified State Model. Uses the optional state number if it is not currently in use in the same State Model. Otherwise, the lowest available number is assigned. In either case the number is returned. Fails if the State Model does not exist or it already has a State with the same name.

Tested OK
17
UI_set_dest_nameold_name, domain, new_namenoneRenames a Destination (State or Deletion Pseudo State).Tested OK
18
UI_delete_statestate_name, state_model, domainnoneDeletes a Destination which may be a State or Deletion Pseudo State.Tested OK
19
UI_set_state_numberstate_name, domain, new_numbernoneAttempts to assign the desired state number. Fails if the number already assigned to another State in the same State Model.Tested OK
20
State Model
21
UI_new_lifecycleclass_name, domainnoneCreates a new Lifecycle State Model on the specified Class. Error returned if one is already defined.
Tested OK
22
UI_new_single_assignerassoc_rnum, domainnoneCreates a new Single Assigner State Model on the specified Association. Error returned if one is already defined.
Tested OK
23
UI_new_multiple_assignerassoc_rnum, loop_number, partition_class_name, domain
-- The rnum and the partition class must be in the same loop
noneCreates a new Multiple Assigner State Model on the specified Association. Error returned if one is already defined. Also, both Constrained Loop and partitioning Class will be validated to ensure that the meet requirements annotated in signature above.
Tested OK
24
UI_delete_state_modelstate_model, domainnoneRemoves a State Model along with any of its Events, States, Transitions, etc.Tested OK
25
UI_set_partition_classassoc_rnum, domain, new_part_class_namenoneChanges the partitioning Class defined on an Multiple Assigner.Tested OK
26
UI_multiple_assigner_to_singleassoc_rnum, domainnoneConverts a Multiple to a Single AssignerTested OK
27
UI_single_assigner_to_multipleassoc_rnum, domain, partition_class_name, loop_numbernoneConverts a SIngle to a Multiple AssignerTested OK
28
Event Response / Transition
29
UI_new_transitionfrom_state_name, dest_name, event_name, state_model, domainnoneCreates a Transition from a State to a Destination State or Deletion Pseudo State.
Tested OK
30
UI_delete_transitionfrom_state_name, event_name, state_model, domain, ['CH' | 'IGN'], [reason]noneDeletes the specified Transition. Actually, it converts a Transition Response into a Non-Transition Response which is CH (can't happen), by default. By default the reason is 'Transition deleted'.Tested OK
31
UI_set_transition_destinationfrom_state_name, event_name, state_model, domain, new_dest_namenoneChanges the destination of an existing Transition.Tested OK
32
UI_set_nt_responsestate_name, event_name, state_model, domain, ['CH' | 'IGN' ], [reason]noneSets the behavior and reason characteristics of an existing Non-Transition Event Response.
Tested OK
33
Build Spec
34
UI_set_default_initial_state_namenamenoneSets the default name that will be used for the state automatically created with a new State Model.
Tested OK
35
UI_set_max_event_specsceiling_valuenoneThis number is used as the maximum bound when searching for duplicate values during ev spec number assignment. It should always be MUCH higher than the anticipated maximum events specified on any single State Model. Since it is typical to have 1-30 events on a State Model, the number should never be lower than 100. Too high a value will increast the time it takes to assign a new event spec number. So don't make it 1,000,000! Unless there is some reason to change it, 200 is a safe ceiling. There's something terribly wrong with a State Model that approaches even 100 event specs.

The number cannot be changed to a value lower than the maximum assigned event spec number, across ALL domains. This maximum event spec value, can be changed to a lower value so that the ceiling can be lowered, however.
Tested OK
36
UI_set_max_statesceiling_valuenoneThis number is used as the maximum bound when searching for duplicate values during state number assignment. It should always be MUCH higher than the anticipated maximum states in any single State Model. Since it is typical to have 1-20 events on a State Model, the number should never be lower than 50. Too high a value will increast the time it takes to assign a new event spec number. So don't make it 1,000,000! Unless there is some reason to change it, 200 is a safe ceiling. There's something terribly wrong with a State Model that approaches even 30 states.

The number cannot be changed to a value lower than the maximum assigned state number, across ALL domains. This maximum state number value, can be changed to a lower value so that the ceiling can be lowered, however.
Tested OK
37
38
Request calls below
39
UI_
40
UI_
41
UI_
42
UI_
43
UI_
44
UI_
45
UI_
46
UI_
47
UI_
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
Loading...
 
 
 
UI Actions
UI Queries
Loose Ends