How to update model attributes when saving a model?

Volker,

AFAIK this can be done. Once you have the script ready, you configure it as described in this article; the most important points:

"You activate the macro by choosing “Available to users”.

To view or to change when the macro should be started automatically, select „Event” and „Select event…” in the “Context” property page of the macro."

hth

Hi Volker,

the equivalent for AssignedModels(...) in the macro API is called Designer.getAssignedModels(...). The latter does not allow direct filtering for certain model types, so you have to call getType() on the result yourself and compare it with the desired model type.

Designer.isModified(...) can only be called on models (it returns true if the model M itself or some of the occurences and definitions reachable from M have been modified); currently there is no way to find out whether a certain object has been modified or which items will be saved by the current save operation.

Ralf

Hi again,

in deed an event "Assignment removed" is missing, so we'll check whether we can add it for a future version.

But in principle you can also solve your problem by listening for "Assignment is to be deleted (vetoable)" (if you rely on that no one does a veto): you can get the model that is going to be assigned via "Context.getSelectedModels()" and the object to which the assignment is being done via "Context.getSelectedObjects()".

 

Ralf

Hi Volker,

I did my proposal just by having a quick look at our code, i.e. which information is packed into the event, but did not write a macro. Now I tried to experiment with some macro code. but unfortunately there seems to be something broken in my local installation, so the macro reacting on "Assignment is to be deleted (vetoable)" does not even start.

But form your posting I assume, that the macro listening on the above event does start in your case? If so, then you can try to get access to the model to whcih the assignment refers as follows:

    var args = Context.getProperty(Constants.EVENT_ARGUMENTS);
    var modelToWhichAssignmentToBeDeletedRefers= args.getValue(Constants.EVENT_ARGUMENT_MODEL)

If this does not work, then you can try something else (which is quite ugly, but should do the job :-) )

    var obj = Context.getSelectedObjects()[0]
    var assignmentsBefore = Designer.getAssignedModels(obj);
    
    // basically execution will now continue and later on when the deletion
    // of the assignment is done the code below will be executed
    
    var job = { run: function () {
        var assignmentsAfter = Designer.getAssignedModels(obj);
        Context.MsgBox("before: " + assignmentsBefore.length + ", after: " + assignmentsAfter.length)
    } }
    var runnable = new java.lang.Runnable(job);
    Packages.javax.swing.SwingUtilities.invokeLater(runnable);

Ralf