Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - adepreter

Pages: [1] 2 3 4
1
When we lock a package, and the locking gets propagated into the elements in the package, other individuals or groups shouldn’t be able to change or delete connectors connecting elements in the locked package.

In other word, when an element is locked, its connectors should be implicitly locked as well.

Note that this could also be an option, in which case you need different types of locking.
So this is for you an opportunity to use the field LockType in the table t_seclocks.
Today this field is always empty.

Alain

2
Automation Interface, Add-Ins and Tools / Paste diagram objects by code
« on: September 18, 2017, 07:46:57 pm »
Selecting diagram objects seems to be OK: The Diagram class has a collection property called SelectedObjects that we can read and write to.

But I can't find a way to paste the selected data objects into another diagram (by code).

Any idea?

3
Thank you all for your useful answers

4
When we mix different types of element... in some cases (it seems random), we are no longer able to move SOME elements (not all of them) up and down by using CTRL-Up or CTRL-DOWN or by using the menu option "Move up" or "Move down" on the element.
In addition, the option 'Content / Reset Sort Order" does not sort these elements.

Any idea how to resolve this?

Thank you in advance,
Alain

5
Automation Interface, Add-Ins and Tools / Protecting some MDG
« on: March 09, 2017, 08:47:32 pm »
If we want to make a product out of an MDG, what is the best way to protect it from reverse engineering?
- MDG as part of the database?
- MDG as part of an add-on?
- ...?
Thank you in advance
A.

6
Thank you. That sounds like a good idea. We will give it a try.

7
Is there any way to update elements programmatically even when they are locked?
This is needed when a language gets migrated (Stereotype, tag name changes...).

As an alternative, how could we
- Save the locks to a file
- Release all locks
- Reload the locks from the file


8
Is there any option to define the lookup package for each tagged value type of type RefGUID or RefGUIDList?
The syntax for defining tagged value type is: Type=RefGUID; Values=Activity;Sterotypes=MyStereotype

We are looking for something like an extra tagged value type specification like "Catalogue={some refGUID of a package}"
Type=RefGUID; Values=Activity;Sterotypes=MyStereotype; Catalogue={some refGUID of a package}

PROBLEM when using multiple Tagged Value Types of type RefGUID or RefGUIDList :
When the value of a RefGUID or RefGUIDList tagged value is not set, The lookup always starts from the last accessed package location for all tags.
This makes the option of using RefGUID and RefGUIDList unacceptable for our end users.


9
We have detailed connectors that realize summary connectors. This is expressed using a connector to connector realization relationship.

0------0
    / \
     |
     |
0------0

Based on a selected connector (SC), I would like to create a script providing zoom-in/zoom-out behaviour :
- Find "connector to connector" connectors (CCs) starting from the selected connector (SC)
- Find target connectors (TCs) at the other end of each "connector to connector" connector (CC)
- Open diagrams that contain the target connectors (TCs) and select the target connectors

10
Using the connector API (http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/automation/connector2_2.html)

- how can we figure out that the client or supplier is another connector?

- if the client or supplier is a connector, how can we get a reference to that connector? Would the Client/SupplierID then be the ID of a connector?

11
Suggestions and Requests / Re: Deprecation warnings
« on: November 17, 2016, 02:28:14 am »
We use the nesting connector heavily in our Enterprise Architecture MDG to indicate ownership and to make this visible in the traceability window.

This is very useful e.g. when we want to distinguish the cases where an Application, an Application Component or a Data Store...
- *Owns* Data Objects (golden source)
- *Is composed of* Data Objects (the app, app comp or data store contains the data object bit is not the golden source)

Please don't shoot the nesting connector (even if you remove it from the UML toolboxes). Our MDG and its army of robots changed Sparx into a very competitive EA tool. I will not be able to share things if you change them into dust.

Related feature request: The ability to specify, in an MDG, the verbs appearing in the traceability window (the implementation approach was provided with the request). If you implement this then we would at least be able to compensate any connector type that you would remove. So that would be to the benefits of everyone.

Alain

12
Does/Will EA run on Windows 10 mobile (is it/will it be compatible with the Universal Windows Platform)?


13
Thank you for you nice recommendation. I will give it a try.

To answer your question about the need of such feature for EA...

To make diagrams readable by business and IT decision makers, it is important to not mix too many kinds of relationships on the same diagram, and yet... we need to show all information that we want to convey.

Sample diagram where such feature is needed:
An information flow between business functions where the applications supporting (connected to) each business function appear on the business function shape.

14
Let's say we have several Application Components that realize (they are connected to) some Business Function.

A key requirements for Enterprise Architecture is the ability to show the application component names directly on business function shapes.

Do we have a generic solution to show names of connected items directly on shapes?
I can't find anyway to do this on Shapescript.
Do we need some add-in?
Do we have any shared code available to do this?

NB: This capability should be built in Sparx

15
Does anybody know in which table(s) the model searches are stored?

Pages: [1] 2 3 4