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 - Geert Bellekens

Pages: 1 2 3 [4] 5 6 ... 818
46
General Board / Re: Colon in BPMN Lane/Pool name
« on: January 25, 2023, 12:13:08 am »
Reported it as a bug:

Details:
In previous versions, a BPMN lane shows the name of the element linked to the PartitionElementRef in case it's own name is empty.
In the current version the lane only shows a single colon ":"


Steps to Reproduce:
- Create a BPMN Lane
- Select an element in the PartifionElementRef property of the lane
- Clear the name of the lane
- notice that on the diagram there is only a single colon ":" as the name of the lane.

Geert

47
General Board / Re: Colon in BPMN Lane/Pool name
« on: January 24, 2023, 11:36:26 pm »
Hmm, I have the same issue in v16.1.1623 (64 bit)

I don't remember seeing this when testing EA v16 earlier. Might be a brand new bug... ???

Geert

48
General Board / Re: Best method to differentiate between AS-IS and TO-BE
« on: January 24, 2023, 11:32:38 pm »
We determined that it's not possible to maintain two versions of the same truth (AS-IS vs TO-BE) in the same model, so if anyone needs the old AS-IS situation, they need to refer to a old snapshot of the model.
Our working model only keeps track of the TO-BE situation.

We do "tag" the elements impacted with a change object so we know which model elements where updated for a certain change.

Geert

49
You cannot choose connectors. You'll have to change the type of your tagged value from RefGUID(List) to a regular string.

Geert

50
General Board / Re: Colon in BPMN Lane/Pool name
« on: January 24, 2023, 02:13:19 am »
The ":" you see is the classifier indicator. Have you tried it on a clean new model?

Geert

51
In that case you might want to consider switching to a real database such as SQL Server.

The file based options are really only suitable in a single user context.

Geert

52
Bugs and Issues / Re: Latest Release of EA v16.1 Template Fragments
« on: January 24, 2023, 02:08:49 am »
Child elements section is not really a section like the others is it?
It's more like: and now do the same thing recursively for all child elements

Geert

53
I don't think there even exists an XSD for these profile files.

I think Sparx consideres them as internal technical files, and therefore not needed to document the format.

Geert

54
General Board / Re: Best method to differentiate between AS-IS and TO-BE
« on: January 23, 2023, 08:58:42 pm »
Another question: how do you guys resolve navigating to what will be developed in what sprint?
We try to abstain from using the browser but prefer navigation cells; We accomplish this by building project pages; But in the end it delivers a huge clutter of pages to maintain.

What are the better practices?

Thanks in advance for the answers
We use change objects and link them to model items using a script.
https://github.com/GeertBellekens/Enterprise-Architect-VBScript-Library/blob/master/Projects/Project%20A/Diagram%20Group/Link%20To%20CR.vbs
https://github.com/GeertBellekens/Enterprise-Architect-VBScript-Library/blob/master/Projects/Project%20A/A%20Scripts/LinkToCRMain.vbs

Change objects are then grouped into releases/sprints

An SQL search gives us an overview of all changes in the model per change and per release.
We do not use diagrams for this purpose.

Geert

55
Automation Interface, Add-Ins and Tools / Re: EA16, Call to OpenFile2()
« on: January 23, 2023, 08:04:21 pm »
Have you tried with EA v16.1.1623?

They forgot the .qea file format in the ProjectTransfer function and fixed that in this version. Maybe they also fixed the same issue in the OpenFile2() method.

If not, report a bug.

Geert

56
Did you put the file on a Onedrive or Google drive or similar?

I can imagine that might get you into trouble.

Otherwise you can try to migrate to .qea files instead of .eap. These are a lot faster in general as well.

Geert

57
General Board / Re: Creating clickable links in generated documents
« on: January 21, 2023, 01:34:15 am »
If those these links are formatted as links in EA (using the hyperlink button on the notes dialog) then they should be clickable in the generated document.

If that is not the case you might want to report a bug.

In the meantime, or if the urls are not formatted, you can create a script fragment that takes your notes, figures out where the hyperlinks are, and formats them such that they become clickable links in Word. You can use the script I posted as a basis on how to do that.

Geert

58
General Board / Re: Creating clickable links in generated documents
« on: January 20, 2023, 04:51:19 am »
IIRC, if you a link into the notes with the proper icon, it translates into a clickable link in the document.

An alternative, for example to generate a WebEA or HTML Export link, is to use a script fragment.

Here's the one I use:

Code: [Select]
'[path=\Projects\Project A\Template fragments]
'[group=Template fragments]
option explicit

!INC Local Scripts.EAConstants-VBScript

'
' Script Name: DiagramLink
' Author: Geert Bellekens
' Purpose: get the hyperlink for a diagram
' Date: 2019-12-02
'

function getObjectDiagramLink(objectID, baseUrl)
dim element
set element = Repository.GetElementByID(objectID)
'get diagram
dim diagram
set diagram = getFirstDiagram(element)
'get the xml data
getObjectDiagramLink = getRTFData(diagram, baseUrl)
end function

function getPackageDiagramLink (packageID, baseUrl)
dim package as EA.Package
set package = Repository.GetPackageByID(packageID)
'get diagram
dim diagram
set diagram = getFirstDiagram(package)
'get the xml data
getPackageDiagramLink = getRTFData(diagram, baseUrl)
end function

function getRTFData(diagram, baseUrl)

dim diagramUrl
diagramUrl = getDiagramLink(diagram, baseUrl)

dim xmlDOM
set  xmlDOM = CreateObject( "Microsoft.XMLDOM" )
'set  xmlDOM = CreateObject( "MSXML2.DOMDocument.4.0" )
xmlDOM.validateOnParse = false
xmlDOM.async = false

dim node
set node = xmlDOM.createProcessingInstruction( "xml", "version='1.0'")
    xmlDOM.appendChild node
'
dim xmlRoot
set xmlRoot = xmlDOM.createElement( "EADATA" )
xmlDOM.appendChild xmlRoot

dim xmlDataSet
set xmlDataSet = xmlDOM.createElement( "Dataset_0" )
xmlRoot.appendChild xmlDataSet

dim xmlData
set xmlData = xmlDOM.createElement( "Data" )
xmlDataSet.appendChild xmlData

dim xmlRow
set xmlRow = xmlDOM.createElement( "Row" )
xmlData.appendChild xmlRow

dim formattedAttr
set formattedAttr = xmlDOM.createAttribute("formatted")
formattedAttr.nodeValue="1"

dim xmldiagramLink
set xmldiagramLink = xmlDOM.createElement( "DiagramLink" )

xmldiagramLink.text = "<a href=""$inet://" & diagramUrl &"""><font color=""#0000ff""><u>" & diagram.Name & "</u></font></a>"
xmldiagramLink.setAttributeNode(formattedAttr)
xmlRow.appendChild xmldiagramLink

getRTFData = xmlDOM.xml
end function

function getFirstDiagram(diagramOwner)
set getFirstDiagram = nothing 'initialize
'get first diagram
dim diagram as EA.Diagram
for each diagram in diagramOwner.Diagrams
set getFirstDiagram = diagram
exit function
next
end function

function getDiagramLink(diagram, baseUrl)
dim link
link = baseUrl & "/?guid="
'get diagram GUID
link = link & diagram.DiagramGUID
'remove braces
link = replace(link, "{","")
link = replace(link, "}","")
'return
getDiagramLink = link
end function

'msgbox MyPackageRtfData(3357,"")
function test
dim outputString
dim fileSystemObject
dim outputFile

outputString =  getPackageDiagramLink (1783, "http://myserver.local")
'outputString =  getObjectDiagramLink (7220, "http://myserver.local")

set fileSystemObject = CreateObject( "Scripting.FileSystemObject" )
set outputFile = fileSystemObject.CreateTextFile( "C:\Users\gbl\Documents\Temp\diagramLink.xml", true )
outputFile.Write outputString
outputFile.Close
end function

'test

Geert

59
General Board / Re: How to set Multiple Stereotypes on one EA.Element?
« on: January 20, 2023, 12:00:31 am »
In most cases it's not a good idea to use multiple stereotypes.
A lot of things (like shapescripts) are not very well equiped to handle that.

In your case, it look to me like a constraintBlock is (or should be) a specialized (meta) type of block. So you can use stereotype inheritance in the your profile to model that, and use only constraintBlock as stereotype.

Apart from the advice, you can set multiple stereotypes using the property EA.Element.StereotypeEx: passing comma separated stereotype names.

Geert

60
I just tested with a .eap file and the latest version (v16.1.1623 64 bit); and I can confirm what you are seeing. It doesn't work.

I get the dialog, but even when pressing the Transfer button it doesn't work.

Just to be sure, I checked; but I can still transfer from DB to .qea automatically

Looks like a bug to me. You better contact support@sparxsystems.com

Geert

Pages: 1 2 3 [4] 5 6 ... 818