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 ... 7
16
That works fine. Thank you Geert!

Result is:

{Note.Formatted}

referring to the following query:

SELECT
Perspective = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Perspective'),
Code = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Code'),
t_object.Name as Name, t_object.Note as "Note.Formatted",
Implications = (select tv.notes from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Implications'),
Rationale = (select tv.notes from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Rationale')
FROM t_object
where t_object.stereotype = 'NMBS_Principle'
and t_object.package_id = #PACKAGEID#
order by Code


17
Hello,
In a template fragment I am selecting elements of a certain types in the current package using #PACKAGEID# (see select clause below).
I use that fragment only to be able to sort elements by a certain tagged value in a package.

The select clause collects notably the element Note.
The fragment also formats the resulting values in a table.

Problem: The generated Note field value, referred as {Note} in the document, shows the source HTML text including <LI> etc...

Any idea how to fix this problem?

Cheers,
Alain

SELECT
Perspective = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Perspective'),
Code = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Code'),
t_object.Name as Name, t_object.Note,
Implications = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Implications'),
Rationale = (select tv.value from t_objectproperties tv
where tv.Object_ID = t_object.Object_ID and tv.property = 'Rationale')
FROM t_object
where t_object.stereotype = 'NMBS_Principle'
and t_object.package_id = #PACKAGEID#
order by Code


18
Workarounds are also not compatible with our model validation addin that uses a clean language metamodel as configuration data.

19
We don't want workarounds (e.g. creating instances)

We need clean and direct traceability between elements as we are generating lots of excel reports and governance charts.

Alain

20
Any date about when we shall have a solution for this? (besides the weird and buggy “virtual connectors”).

http://www.sparxsystems.com/forums/smf/index.php/topic,39241.msg242691.html#msg242691

Users complain they cannot create SIPOcs because of this.

21
Does anybody know whether it is possible to deploy an add-in using ClickOnce Security and Deployment?
https://docs.microsoft.com/en-gb/visualstudio/deployment/clickonce-security-and-deployment

The goal is to
- enable users to install an add-in without admin rights
- update the add-in automatically when it has changed

Cheers,
Alain

22
Automation Interface, Add-Ins and Tools / MDGs and strict connector syntax
« on: February 27, 2018, 07:10:15 pm »
We have a connector validation implemented for our MDG.

How can we make sure that...
Step 1: when the strict connector syntax in ON, this only applies to UML and not to stereotypes derived from UML
Step 2: when the strict connector syntax is switched ON/OFF, our MDG-specific connectors are validated/not validated (same as for BPMN)

Reference: http://www.sparxsystems.com/enterprise_architect_user_guide/13.5/user_interface/links.html

Thanks
Alain

23
Suggestions and Requests / Enable tooltips on HTML reports
« on: February 21, 2018, 11:54:48 pm »
We would like to see element notes when hovering on elements in generated HTML reports.

A.

Related post: http://sparxsystems.com/forums/smf/index.php/topic,29540.0.html

24
End users sometimes want to create several views of the same element on the same diagram.
They also want to tell which connector needs to be visible for each view on the element (diagram object).
They don't want to create a "virtual connector". How could they think about such terminology when searching the documentation?
=>

1) Bug: The documentation provides documentation on the implementation i.e. "virtual connector"
It should instead on the end user's feature i.e. getting several views on the same element on the same diagram.

2) Questioning the implementation
Why not creating virtual diagram objects instead of "virtual connectors". These virtual diagram objects would not visible in the project browser (like text, boundary etc...)??
Users would then explicitly hide the connectors they don't what to see for the virtual object.
So it would be also more flexible for the end-user.
And it would be a direct implementation of the requirement.

25
So that we can
- Export only changed elements (and import in other tools)
- Create reports on last changes

If we could also have the author that would be even better

26
Thank you Geert and Arshad

27
We can find the default property types in that table:
select * from t_propertytypes

And the tagged value in that table:
select * from t_objectproperties where property = 'vision'

and we have the possible values in the Notes column with equivalent access through the API.

I was hoping there would be some predefined validation. It is really weird that something as basic as that isn't available in the API.

28
But what API can we use to perform the validation (in a C# program)?

We can't find any equivalent to "Validate" in the "TaggedValue" class: http://www.sparxsystems.com/enterprise_architect_user_guide/12.1/automation_and_scripting/taggedvalue.html

The Validation features in the Project class are not looking useful either: http://www.sparxsystems.com/enterprise_architect_user_guide/12.1/automation_and_scripting/project_2.html

Since the tagged value type (e.g. enumeration, date...) has been defined in the MDG there should be something at run time that uses these definitions for validation????


29
Before importing elements from an Excel file, we would like to check whether the imported tagged values are compliant with the type defined in the element stereotype (part of a MDG).

Does anybody know how to validate the to-be-imported tagged values at runtime?

30
Prerequisite for reproducing the problems
- Create a package PV1 with 3 diagrams each showing same elements.

Scenario:
- Clone package PV1 as new version PV2

- In PV2...
- Open cloned diagram D1 and filter to version
- Create a new element ENEW
=> PROBLEM 1: ENEW is greyed out, though this is clearly a change.

- Clone an element ECHANGED. The element is properly cloned and it is no longer greyed out.
- Open cloned diagram D2 that shows same elements as D1
=> PROBLEM 2: ECHANGED is greyed out, though it has been clearly changed.

Pages: 1 [2] 3 4 ... 7