Messages

1

Automation Interface, Add-Ins and Tools / Hide header in custom fragment (bookmark?)

« on: April 16, 2019, 07:38:24 pm »

Hi!

I have a document fragment where the data is coming from a custom script (Document Options -> Custom Query -> Custom Script). This script returns, among other information, the constraints associated with an element. I want to, if there are no constraints associated with the element, to not show the header. This is how the fragment looks like:

custom>
Definition
{Definition}

Constraints     <-- If there are no constraints, I don't want to show this text
{Constraints}
<custom

I cannot figure out how to do this using bookmarks (if it is even possible). The other option is to let the script return the header as well, but how do I format it? (I want it to be Calibri, bold and 9)

2

Automation Interface, Add-Ins and Tools / Re: Default value for tagged value not shown in report

« on: March 28, 2018, 05:35:06 pm »

Very annoying.

Thanks for the information! At least I didn't do something wrong.

3

Automation Interface, Add-Ins and Tools / Default value for tagged value not shown in report

« on: March 28, 2018, 12:05:04 am »

Hi!

I have developed a MDG Technology and extended Class by adding a few tagged values. Some of these tagged values have a list of possible values, where one of the values is the default value.

When I deploy and use this technology the default value of the tag is visible in EA (Tagged Values window), but when I create a report, there is no value (using custom SQL in the report). If I explicity set the value to the default value, everything works as expected.

What should I do so it it not necessary to change the default value to...the default value to see it in the report?

4

Automation Interface, Add-Ins and Tools / Re: Custom toolbox is not opening for diagram

« on: March 08, 2018, 11:52:48 pm »

I started to play around with this and it seems that the problem is when you have a a profile element with the same name as the toolbox.

Code: [Select]

<UMLProfile>
...
<Stereotype name="NNN">
...
</UMLProfile>

<DiagramProfile>
...
<Property name="toolbox" value="NNN"/>
...
</DiagramProfile>

<UIToolboxes>
...
<Documentation id="3F040576-9" name="NNN" version="1.0" notes="My custom diagram"/>
...
</UIToolboxes>

It also worked to change the name property as you said.

5

Automation Interface, Add-Ins and Tools / Custom toolbox is not opening for diagram

« on: March 08, 2018, 11:13:10 pm »

Hi!

I have created an MDG Technology including custom stereotypes, diagram and toolbox, and imported this technology in a project. When creating a new diagram, I can select my custom diagram type, but when I open the diagram, the custom toolbox is not opened. I have to select it manually (so it is there and working).

I checked the xml file for the MDG:

Code: [Select]

<DiagramProfile>
...
<Property name="toolbox" value="NNN"/>
...
</DiagramProfile>
<UIToolboxes>
...
<Documentation id="3F040576-9" name="NNN" version="1.0" notes="My custom diagram"/>
...
</UIToolboxes>

It seems to be correct, but it is not working. Any ideas why?

6

Automation Interface, Add-Ins and Tools / Re: Tags on connector depending on elements

« on: March 01, 2018, 10:30:29 pm »

Thanks for the information!

7

Automation Interface, Add-Ins and Tools / Tags on connector depending on elements

« on: March 01, 2018, 08:57:07 pm »

Hi!

When you create a profile in a MDG technology, you can specify which tags should be created for a connector. Is it possible to have different tags dependent on the source and target element stereotypes (without defining two different connectors)?

For example:
If the source element has stereotype 'a' and target element has stereotype 'b', a tag with name 'My tag' should be added to the connector. But if the target element has stereotype 'c', the tag 'My other tag' should be added to the connector.

Or am I required to create an add-in for this?

8

Automation Interface, Add-Ins and Tools / Re: UML Profile, don't show the stereotype

« on: January 24, 2018, 11:03:24 pm »

Thanks, now I understand!

9

Automation Interface, Add-Ins and Tools / Re: UML Profile, don't show the stereotype

« on: January 24, 2018, 10:36:27 pm »

I would prefer to not do this for all elements in the diagram, but only for this element. But I cannot figure out how to do this in a shape script. Or do you mean that I need to create the shape from scratch? I thought about using DrawNativeShape and change it somehow. But perhaps that does not work?

10

Automation Interface, Add-Ins and Tools / UML Profile, don't show the stereotype

« on: January 24, 2018, 09:09:56 pm »

Hi!

I am creating an UML profile, extending the Component meta class to add a few tagged values, and set it to show the tagged values in the diagram (_Tag = 1). However, when I do this, the stereotype text is also shown (in addition to the icon). Can I change this behavior so that it acts the same as the original Component, only showing the icon and not the stereotype text?

11

Automation Interface, Add-Ins and Tools / Re: Is it possible to remove the heading if the field is empty?

« on: January 22, 2018, 09:55:43 pm »

Thanks for the information.

Too bad there is no easier way to do it.

12

Automation Interface, Add-Ins and Tools / Is it possible to remove the heading if the field is empty?

« on: January 22, 2018, 08:04:24 pm »

I have a fragment which is a custom SQL query returning the note of a specific tagged value of the element. Above this note text is a heading. I would like that if the note is empty, or if the tag does not exists, the heading is removed because there will be no text beneath the heading. Is this possible?

I have tried with Bookmark.Start and Bookmark.End which works in other situations, but could not get it to work in this case.

13

Automation Interface, Add-Ins and Tools / Re: Shape script: Show tagged value at bottom left

« on: December 08, 2017, 09:12:50 pm »

Thanks for the options!

The Custom Compartment with RelatedElement is also interesting.

14

Automation Interface, Add-Ins and Tools / Re: Shape script: Show tagged value at bottom left

« on: December 05, 2017, 11:51:34 pm »

This is the situation:

We have information flow diagrams showing our applications. We have added tagged values for ID, alias, lifecycle, status and other things related to the application. Everyone needs to see the ID and alias so we know that we are all talking about the same application (different parts of the organisation seems to use different names). The other tags are mostly targeting the more advanced group and is not of interest to the "general public"; hence I would like to hide them in some diagrams. Using tags is also a convenient way to make things searchable (i.e. show me all applications that are under development).

Right now I am trying to find out the best way to do this. We can still change the way we work. Is custom compartments a better way?

I could use the diagram stereotype to show different tagged values. This shape script will go into a mdg profile later, so it may be better to use Type or MdgType.

15

Automation Interface, Add-Ins and Tools / Shape script: Show tagged value at bottom left

« on: December 05, 2017, 09:16:11 pm »

Hi!

We have an element type with several tagged values. Some of them are relevant to one group of people, and others are relevant to another group. Unfortunately we cannot select which tagged values should be visible in a certain diagram.

So to solve atleast some of the problem, I would like to create a shape script that always shows the tags that are relevant for all people, and if someone creating a diagram want to show all tagged values, that is up to them.

I thought that one option is to use "shape label" with SetOrigin = SW.

Code: [Select]

shape label {
   SetOrigin("SW", 5, 35);
   Println("#TAG:Alias#");
   Print("#TAG:ID#");
}

This makes it possible to hide these tagged values if someone wants to show all tagged values (instead of having duplicate information). The problem is however that the default width of the label is too short so the user needs to immediately change the width. The maximum width of the label may also be too short, which makes the text wrap.

Is there another (better) way to do this?

The requirement is essentially:

• Show the value of certain tagged values, somewhere inside the element, each on its own line.
• Don't wrap the text
• Preferable (but not a requirement), hide this if all tagged values are shown on the element