Macro help (before saving model )

Hi Misha,

for example - I disable model attributes.

So, create macro with event "Model attribute is to be changed by modeling (vetoable)". Use this code:

var m = Context.getSelectedModels();
if (Context.getLoginInfo(m[0]).getUserName() == "BANKUSER"){    
  Context.setProperty("event.veto", "1")
}

Open model attributes and try to change any - are disabled. So try other events, but in event name must be "(vetoable)".

Hi Misha,

I write you example, where I can create only event. You should select macro event "Object occurence created". There isn't vetoable event for creating occurence, so we have to delete occurence.

var oObjOccs = Context.getSelectedObjOccs();
if (Context.getLoginInfo(oObjOccs[0]).getDatabaseName() == "TEST" && Context.getLoginInfo(oObjOccs[0]).getUserName() == "BANKUSER"){    
  if (oObjOccs[0].getSymbolNum() != Constants.ST_EV){
    Designer.deleteOcc(Designer.getModel(oObjOccs[0]), oObjOccs[0]);  
  }
}

I think no, but you can call report from macro

That's a fantastic solution

Thanks

Abhijit Das

abhijit.das@cba.com.au

Hi Misha,

yes, I understand you, this is slow. But maybe solution is configurate new method filter (for only one object) for this user. This user have to login with this filter and you need to use simple macro, check only delete objects and occurence placement.

Hi Misha,

ooops, I forgott that user have to see whole model... I'm sorry, filter isn't good solution.

I think no... only check in macro, which user is login

Hi Mischa,

Didn't see your post until now. It's a common issue that running a macro takes a while and impacts the modelers work. That's why I usually only execute the macro on save (vetoable) or user triggered. One question I have about the limiting a user to model certain objects on the model. Do you mean in this case that the user is not allowed to place the occurrence at all (so also no reuse of existing) or is it not allowed to create new object definitions, but allowed to reuse existing.

In the first situation, working on the same model is no option. I would suggest to have separate models for the different purposes. If you have a derived modeltype you can limit the symbols to be used for the specific models. Using a report you can then generate a view containing the information of both other views (this however results in high school scripting knowledge).

If the second situation is the case, you can run a report checking on the creator of the objects with a signaling function.

Unfortunately I can't give you another option.

Best regards,

Edwin