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.


Topics - Uffe

Pages: [1] 2 3 ... 20
1
Bugs and Issues / CallOperationActions in project browser
« on: April 20, 2018, 10:04:54 pm »
Hi all,


A CallBehaviourAction is displayed with its classifier in the project browser on the form action_name : classifier_name.
A CallOperationAction, on the other hand, doesn't display its operation.

Shouldn't it?

Something like action_name : element_name::operation_name, where element is the interface, class, component or whatever that holds the operation?


/Uffe

2
If you create a stereotype for Action and assign it a shape script which prints the Classifier or Classifier.Name property, the expected behaviour for a CallOperationAction is that the name of the operation (when set) is printed. It is not.

When you set the action's operation, the name of that operation is printed -- but only until the diagram is closed. When next it is opened, nothing is printed although you can still Find the operation from the action.

It appears that classifiers defined by the GUID string and not the integer ID aren't handled correctly by the shape script engine.

/Uffe

3
If you create a stereotype for CallOperationAction on the fly, then assign it a shape script in Configure -- UML Types, and then create a CallOperationAction in an activity diagram and give it that stereotype, the shape script is not executed.

If you modify the stereotype to apply to Action, it is executed correctly on the same CallOperationAction.


/Uffe

4
Bugs and Issues / Time-aware models: revert clone
« on: April 19, 2018, 10:14:14 pm »
Hi boys & girls,

I can't find a function to revert a cloned element in a diagram, in other words destroy the cloned element and replace it in the diagram with the original.

Isn't there one?


/Uffe

5
Bugs and Issues / Import/export of time-aware models
« on: April 19, 2018, 09:41:36 pm »
Hellu,


If I clone a package structure to a new version, and then export the new version as XMI, will the exported XMI include the non-cloned elements from the original version?

Similarly, if I do a CSV export will the non-cloned elements be included?


/Uffe

6
Bugs and Issues / Time-aware MDG Technology models
« on: April 19, 2018, 09:39:55 pm »
Hi all,


So I'm thinking about trying time-aware models in my MDG Technology project, where I've got a couple of different technologies.

Let's say I've got a model that I've generated an MDG Technology from, and I clone that model.

If I now generate a profile from a package in my cloned model, going from the project browser and not the diagram, will the generated profile include the non-cloned elements?

Will the generated profile have the same "<Documentation id" attribute as the original?


/Uffe

7
Hi all,


I'm fiddling around with time-aware models to see if they're of any use.

First thing I tried was to set up a simple package structure as version 1.0.
- Parent package
  - Package diagram (showing child package)
  - Child package
    - Component diagram (showing component)
    - Component


Then I went ahead and cloned the whole structure to a new version 1.1. Here's what I got:
- Parent package [cloned]
  - Package diagram (showing original child package)
  - Child package [cloned]
    - Component diagram (showing original component)


This can't be right, can it? Since the child package is cloned, surely the diagram it's in should show the clone and not the original?
The way this is implemented, if I navigate between diagrams by double-clicking the child package, I go from the 1.1 version of the package diagram into the 1.0 version of the component diagram, even though the child package exists as a clone in 1.1 and has a cloned component diagram.

Am I missing something?


/Uffe

8
Bugs and Issues / Downgrading from 13.5
« on: April 18, 2018, 01:33:44 am »
Hi all,


After our recent upgrade from 11.1 to 13.5, we've noticed multiple issues with document generation and database modelling, where things that worked in the older version no longer do in the new. We're getting nothing back from Sparx support, so we're going to have to look at downgrading.

We've upgraded all our databases (SQL Server) to the 1220 version of the schema. This means downgrading to 12.1 should be OK, but I'm thinking about what we'll need to do if it turns out the bugs that are causing our problems were already present in 12.1, meaning we'll have do go even further back to either 12.0 or 11.1, where we know things work.

Does anyone have experience of downgrading past a schema change?

Or is it possible to run 11.1/12.0 on a 1220 schema?

Thanks,


/Uffe

9
Bugs and Issues / No API documentation for Repository.ImportRASAsset()
« on: April 13, 2018, 06:34:55 pm »
Hi all,

There is no documentation in the user guide for the automation function Repository.ImportRASAsset(), which was introduced in 1308.

According to EA's VBScript IntelliSense it takes eight string parameters, which takes a bit more effort to work out through trial and error than I would like to spend.

Reported.


/Uffe

10
Bugs and Issues / Change: inconsistent details views
« on: April 11, 2018, 12:39:00 am »
Hi all,


I've spotted an inconsistency between the two details views for a Change, specifically with the Version property. I assume the behaviour is the same for other maintenance types.

The Changes window is a non-modal window which has the list of Changes for an element along with a details view which (NB) contains all the properties for a Change.1

You can also use the Element Browser, which is also a non-modal window with a tree view in which all maintenance items (and a bunch of other stuff) is displayed with just some basic info.
From the Element Browser you can double-click a Change to open a modal window titled "Change details for <element type>: <element name>" which (NB) contains all the properties for a Change.1

Here's my thing.

If you create a Change from the Changes window, it's given a default Version. A little cryptic, and not related to what's in the element's Version property, but whatever, it's there and you can change it to whatever you want.
You can even clear that property, and save the Change. The empty string is saved in the database.

But here's where it gets weird.

If I open up the Change Details window, the empty Version is replaced with a new Version on the same form as the default. The database has not changed at this point, but the Apply and OK buttons are disabled even though the dialog contents do not match the database.

If I close the Change Details window without making any changes, I don't get a confirmation prompt.

If I open it up again, there is a new generated Version filled in.

So in other words the Changes window allows empty Versions, but the Change Details window does not.

Reported.


/Uffe


1There's actually one column in the t_objectproblems table, Severity, which is not shown. But it's not in either of these windows, so it is consistent.

11
Hi all,


According to the user guide, the Description field of a Maintenance Item should be shown but not editable in the Notes window.

I don't see anything in the notes window, whether I select the element that has an associated maintenance item in the project browser or a diagram, or even if I select the maintenance item itself in the element browser.

Is there a configuration I'm missing?

Cheers,


/Uffe

12
Hi all,

Following on from my earlier Bugs & Issues post, I sent the following feature request to Sparx on March 28. I haven't heard back yet, but will update this post when and if.

/Uffe


1) For action pins which do not have a defined Argument but do have a defined Type, provided the type is a classifier, the classifier's tagged values should be included in the pin's extended tagged values.
This is how activity parameters behave.

2) For action pins which have a defined Argument, it should not be possible to edit the Name, Type, Multiplicity, Kind, or its Stream, Control Type or Exception properties.
These properties should all be slaved to the argument's corresponding properties.

3) If an action pin has a defined Argument, and that argument has the Fixed Value property set, it should not be possible to edit the pin's Value.

4) When creating an action pin based on an activity parameter, the pin's Value should be set to the parameter's Default Value, if any.

5) When creating an action pin based on an activity parameter, the pin's Kind should be set based on the parameter's Direction as follows:
in => in
out => out
return => out
inout => this should result in two pins, one in and one out, with otherwise identical properties.

6) When shown in diagrams, an action pin label should contain the following based on which of the pin's properties are set:
Name and Value => "name = value" (Type omitted if set)
Name, no Value => "name : type"
Value, no Name => "value : type"

13
Bugs and Issues / DocumentElement fails for certain users
« on: April 05, 2018, 12:07:23 am »
Hey guys,


Got a weird one.

The setup:
SQL Server repository, 13.5.1352 clients. Recently upgraded from 11.1, where everything worked.
Browser script (VB) which calls an MDG Technology-deployed script to generate a document. Templates in same MDG Technology.
Security enabled with Windows authentication. All users have both Run and Edit Script permissions.

For some users, the script fails when it hits the first call to DocumentGenerator.DocumentElement().
Previous DocumentGenerator calls all seem to work just fine. They are, in order:
DocumentGenerator.SetStyleSheetDocument("Numbered Headings - Black")
DocumentGenerator.NewDocument("")
DocumentGenerator.InsertLinkedDocument(linkedDoc)


Then comes
DocumentGenerator.DocumentElement elementID, 0, "The template"
... and that's all she wrote. The script breaks on that line, popping an error dialog which contains the line number but no error code or message.
If the user hits F8 and selects the same template, the generation works fine.

This is consistent:
Some users cannot run the script at all, other users can run the same script repeatedly without any problems.
For users who can't run the script, if they log in as admin (which has the full set of permissions), the script still breaks the same way.
In a different repository, the problem persists: the same users can't run the script.

Any bells ringing?

Could it be related to my zombie custom-script-fragment-doesn't-work-when-invoked-through-the-API bug?
The template in this case does include a fragment, although this time it's a regular SQL fragment.

Is DocumentGenerator fundamentally broken in 13.5?


/Uffe

14
Bugs and Issues / User guide: wrong permission listed
« on: April 04, 2018, 09:23:30 pm »
Hi all,


The user guide page Specify Required MDG Technologies specifies that in order to manage the set of required / permitted MDG Technologies for a security-enabled project, the permission 'Manage Project Settings' is required.

This is incorrect. The relevant permission is 'Configure Project Prerequisites'.

Reported.


/Uffe

15
In 1352, if you create an RTF template and select the Package / Element section, EA automatically includes the Child Elements section.

If you deselect Child Elements, and then click the '+' icon next to the Element section to collapse it, EA reselects the Child Elements section and places the corresponding tags in the template.

Reported.


/Uffe

Pages: [1] 2 3 ... 20