Sparx Systems Forum

Enterprise Architect => Suggestions and Requests => Topic started by: fwoolz on June 11, 2010, 05:27:52 am

Title: Undocumented feature: Repository.CustomCommand
Post by: fwoolz on June 11, 2010, 05:27:52 am

Is it possible to get a list of the various commands (class, method, and parameters) supported by the (undocumented) CustomCommand() method?

Thanks!

Title: Re: Undocumented feature: Repository.CustomCommand
Post by: Eve on June 11, 2010, 08:15:08 am

No.  Commands available through CustomCommand are undocumented because they are subject to change without notice.

Title: Re: Undocumented feature: Repository.CustomCommand
Post by: fwoolz on June 11, 2010, 10:05:41 am

ARGGHH!!! Wuffo that be? (Translation: "Right, then! Why, pray tell, is that the case?")

This seems like a likely candidate for automating UI actions otherwise available only by manual user action (e.g. opening the properties dialog for an element, along the lines of DoCmd in Office VBA). I know that at least one such action is CustomCommand("Repository", "Sync", "<yadayada>") to synchronize stereotypes from the AI; in fact, I found this out from y'all at Sparx!

I would seriously consider (but then I don't have to do the work!) standardizing on an existing set of "CustomCommand" calls (the "interoperable" command set) while leaving room for custom calls that may change with time. Other than the work involved, I don't see why this would be a problem.

[Likewise with Repository.Execute(SQL statement)...]

Cheers,
Fred W

Title: Re: Undocumented feature: Repository.CustomCommand
Post by: Eve on June 11, 2010, 02:52:00 pm

Ok, you would consider a standardized set of supported commands.  In a way that is happening.  Any commands that are standardized will be added to the automation objects themselves.

We are currently planning this for the Synch Profile command.