Messages

1

General Board / Re: Slow performance on Azure SQL

« on: February 07, 2023, 08:21:17 pm »

This has some useful pointers https://azure.microsoft.com/en-us/blog/key-causes-of-performance-differences-between-sql-managed-instance-and-sql-server/. Looks like you might want to connect via ProCloud, hosted on an Azure VM in the same region as the DB. Also see the section on encryption at rest by default. If not required, switching it off would increase performance...

2

Automation Interface, Add-Ins and Tools / Re: Getting started with scripting

« on: October 15, 2022, 12:13:39 am »

Hi,

If you want to import CSV, you might also look at the Sparx DataMiner concept, here https://sparxsystems.com/enterprise_architect_user_guide/16.0/modeling_fundamentals/data_miner.html. I think it has out of the box connections for csv files + some examples.

You should also be aware of the CSV export/import feature - depending upon the specific details of your use case, this might fufill your requirements without having to write any code. See https://sparxsystems.com/enterprise_architect_user_guide/16.0/model_exchange/csvspecifications.html

Regards,

Jon.

3

Automation Interface, Add-Ins and Tools / Re: VBSCRIPT - Select folder/file to save to

« on: September 14, 2022, 12:41:04 am »

In vbscript its actually potentially even easier as the project interface provides this method:

Dim prj As EA.Project

Set prj = Repository.GetProjectInterface()
fullPath = prj.GetFileNameDialog (filename, "*.docx", 1, 0, "", 1) + ".docx"

4

General Board / Re: Upgrade path to Sparx EA v16 and PCS v5

« on: August 05, 2022, 05:35:54 pm »

One note of caution on 16 64bit. In my testing, i got timeout errors when opening a package with a large number of elements/subpackages in. When i tried with the 32 bit version all was ok. I need to do more testing. Bit if you have a large repository ... i'd run some tests yourself first...

5

PCS Frequently Asked Questions / Re: [Ask] column name with space on Custom Report Prolaborate

« on: July 05, 2022, 04:03:15 pm »

Hi,

Which version are you using. I know in 3.6, this was fixed. You can have spaces in column names. Not sure re v4.x. However i'm told there will be a new version, 4.2 release very soon. So maybe hang on a few days and try with the new version when its released if you on version 4.x

Regards,

Jon.

6

PCS General Board / Re: Custom report on Prolaborate DB content

« on: May 03, 2022, 06:25:33 pm »

Hi,

Depends on where your prolaborate and sparx repos are stored. I have both on same SQL Server DB. So i can use the following SQL (as an example)

SELECt emailid as name FROM Prolaborate.dbo.users

(where prolaborate is the name of my prolaborate database).

7

Automation Interface, Add-Ins and Tools / Re: SQL Search selected or zero results returned

« on: December 03, 2021, 02:38:50 am »

Hi,

If the SQL for a fragement returns 0 rows, the detail of the framgment will not be included in the report. Is this what your expecting ?

Regards,

Jon.

8

Automation Interface, Add-Ins and Tools / Re: MDG - strange behaviour when extending from another profile

« on: November 13, 2021, 03:10:17 am »

Yes sorry i should have said - there (BPMN2.0::SequenceFlow etc) are in my tool box as well...

9

Automation Interface, Add-Ins and Tools / Re: MDG - strange behaviour when extending from another profile

« on: November 12, 2021, 07:47:55 pm »

Hi,

Yes i have included BPMN2.0::Gateway and BPMN2.0::StartEvent etc in my toolbox. I can drag and drop these onto my stereotyped diagram. However im not offered SequenceFlow to connect the BPMN flow elements i have included in my toolbox when using the quicklinker. Is there some trick/setting to tell my toolbox/diagram stereotypes to inherit/use quicklinker settings defined in another MDG (ie the BPMN2.0 MDG) when i reuse their elements ??

Regards,

Jon.

10

Automation Interface, Add-Ins and Tools / MDG - strange behaviour when extending from another profile

« on: November 12, 2021, 03:46:11 am »

Hi,

I've hit some strange behaviour when extending stereotypes from another profile. In my example i have a stereotype that extends the BPMN2.0::Activity. Once i have deployed my MDG i can create MyProfile::Activities just fine, with my extra tagged values etc.

However if i use the quicklinker to try and link to / create other valid BPMN elements - i'm not presented with any. But this is intermittent. A couple of days ago i was. Now i'm not.

I thought if i extended a stereotype the constraints from the base type were inherited ?

Further, on my MDG profile toolbox, i have add a couple of standard BPMN2.0 elements, Gateway, StartEvent and EndEvent - i can add these to a diagram just fine. However, again if i use the quicklinker to try and connect them via SequenceFlows, i'm not offered the SequenceFlow connector.

I have the BPMN2.0 Tech enabled and create normal BPMN2.0 Business Process Diagrams - all is ok on them. The issue occurs if i add these elements to my own MDG Diagram (which extends Diagram_Analysis). Any thoughts as to why this might be ?

Regards,

Jon.

11

Automation Interface, Add-Ins and Tools / Re: Quicklinker question

« on: November 12, 2021, 03:38:02 am »

Hi,

Thanks for feedback everyone. The _IsCommon attribute worked for me.

Regards,

Jon.

12

Automation Interface, Add-Ins and Tools / Quicklinker question

« on: November 11, 2021, 04:52:29 am »

Hi,

In my MDG i have replaced legacy Quicklinker CSV with <<stereotyped relationships>> and all is now ok. Except for one small point.

In a few cases i want my users to use the quicklinker to form (suggested) relationships between two elements. However when dragging the quicklinker from the same source element to empty space, i do not want the quicklinker to (suggest) the target as a new element type. I could do this with the quicklinker csv (ie column N Create Element is blank). How can i do the same with <<stereotyped relationships>> or other meta model techniques ??

Thanks,

Jon.

13

Automation Interface, Add-Ins and Tools / Re: MDG Meta-constraints

« on: October 27, 2021, 09:22:46 pm »

Hi KP,

I've applied changes you sugggested. Still no joy :-(. See updated / generated mdg xml below. Any other suggestions please ?

<?xml version="1.0" encoding="windows-1252"?>
<MDG.Technology version="1.0"><Documentation id="dbX" name="dbX" version="1" notes="dbX Test profile"/><UMLProfiles><UMLProfile profiletype="uml2">
         <Documentation id="B0A553A8-F" name="dbX" version="1.0" alias="dbX" notes="dbX"/>
         <Content>
            <Stereotypes>
               <Stereotype name="Problem" metatype="Problem" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <stereotypedrelationships>
                     <stereotypedrelationship stereotype="dbX::solved_by" constraint="dbX::Solution"/>
                  </stereotypedrelationships>
                  <AppliesTo>
                     <Apply type="Class">
                        <Property name="isActive" value=""/>
                     </Apply>
                  </AppliesTo>
               </Stereotype>
               <Stereotype name="Solution" metatype="Solution" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <AppliesTo>
                     <Apply type="Class">
                        <Property name="isActive" value=""/>
                     </Apply>
                  </AppliesTo>
               </Stereotype>
               <Stereotype name="solved_by" metatype="solved_by" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <metaconstraints>
                     <metaconstraint umlRole="source" constraint="dbX::Problem"/>
                     <metaconstraint umlRole="target" constraint="dbX::Solution"/>
                  </metaconstraints>
                  <AppliesTo>
                     <Apply type="Dependency">
                        <Property name="_lineStyle" value="orthogonalR"/>
                        <Property name="_MeaningBackwards" value="Solves"/>
                        <Property name="_MeaningForwards" value="Solved by"/>
                        <Property name="direction" value="Source -&gt; Destination"/>
                     </Apply>
                  </AppliesTo>
               </Stereotype>
            </Stereotypes>
            <TaggedValueTypes/>
            <ViewDefinitions/>
            <Metamodel/>
         </Content>
      </UMLProfile>
   </UMLProfiles><DiagramProfile><UMLProfile profiletype="uml2">
         <Documentation id="44255F82-2" name="dbX-D" version="1.0" notes="dbX-D"/>
         <Content>
            <Stereotypes>
               <Stereotype name="dbX Diagram" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <AppliesTo>
                     <Apply type="Diagram_Logical">
                        <Property name="alias" value="dbX"/>
                        <Property name="toolbox" value="dbX-T"/>
                     </Apply>
                  </AppliesTo>
               </Stereotype>
            </Stereotypes>
            <TaggedValueTypes/>
            <ViewDefinitions/>
            <Metamodel/>
         </Content>
      </UMLProfile>
   </DiagramProfile><UIToolboxes><UMLProfile profiletype="uml2">
         <Documentation id="AAFFFDE3-0" name="dbX-T" version="1.0" notes="dbX-T"/>
         <Content>
            <Stereotypes>
               <Stereotype name="Connectors" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <AppliesTo>
                     <Apply type="ToolboxPage"/>
                  </AppliesTo>
                  <TaggedValues>
                     <Tag name="dbX::solved_by(UML::Dependency)" type="" description="" unit="" values="" default="Solves"/>
                  </TaggedValues>
               </Stereotype>
               <Stereotype name="dbX-T" notes="dbX-T" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <AppliesTo>
                     <Apply type="ToolboxPage"/>
                  </AppliesTo>
                  <TaggedValues>
                     <Tag name="dbX::Problem (UML::Class)" type="" description="" unit="" values="" default="Problem"/>
                     <Tag name="dbX::Solution (UML::Class)" type="" description="" unit="" values="" default="Solution"/>
                  </TaggedValues>
               </Stereotype>
            </Stereotypes>
            <TaggedValueTypes/>
            <ViewDefinitions/>
            <Metamodel/>
         </Content>
      </UMLProfile>
   </UIToolboxes></MDG.Technology>

14

Automation Interface, Add-Ins and Tools / Re: MDG Meta-constraints

« on: October 22, 2021, 07:13:03 pm »

Hi,

I've copied the generated mdg/xml below to help diagnose the issue. very much appreciate any help/pointers :

<?xml version="1.0" encoding="windows-1252"?>
<MDG.Technology version="1.0"><Documentation id="dbX" name="dbX" version="1" notes="dbX Test profile"/><UMLProfiles><UMLProfile profiletype="uml2">
         <Documentation id="B0A553A8-F" name="dbX" version="1.0" alias="dbX" notes="dbX"/>
         <Content>
            <Stereotypes>
               <Stereotype name="Problem" metatype="Problem" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <stereotypedrelationships>
                     <stereotypedrelationship stereotype="dbX::solved_by" constraint="dbX::Solution"/>
                  </stereotypedrelationships>
                  <AppliesTo>
                     <Apply type="Class">
                        <Property name="isActive" value=""/>
                     </Apply>
                  </AppliesTo>
               </Stereotype>
               <Stereotype name="Solution" metatype="Solution" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <metaconstraints>
                     <metaconstraint umlRole="target" constraint="dbX::Problem"/>
                  </metaconstraints>
                  <AppliesTo>
                     <Apply type="Class">
                        <Property name="isActive" value=""/>
                     </Apply>
                  </AppliesTo>
               </Stereotype>
               <Stereotype name="solved_by" metatype="solved_by" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <AppliesTo>
                     <Apply type="Dependency">
                        <Property name="_lineStyle" value="orthogonalR"/>
                        <Property name="_MeaningBackwards" value="solves"/>
                        <Property name="_MeaningForwards" value="solved by"/>
                        <Property name="direction" value="Source -&gt; Destination"/>
                     </Apply>
                  </AppliesTo>
               </Stereotype>
            </Stereotypes>
            <TaggedValueTypes/>
            <ViewDefinitions/>
            <Metamodel/>
         </Content>
      </UMLProfile>
   </UMLProfiles><DiagramProfile><UMLProfile profiletype="uml2">
         <Documentation id="44255F82-2" name="dbX-D" version="1.0" notes="dbX-D"/>
         <Content>
            <Stereotypes>
               <Stereotype name="dbX Diagram" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <AppliesTo>
                     <Apply type="Diagram_Logical">
                        <Property name="alias" value="dbX"/>
                        <Property name="toolbox" value="dbX-T"/>
                     </Apply>
                  </AppliesTo>
               </Stereotype>
            </Stereotypes>
            <TaggedValueTypes/>
            <ViewDefinitions/>
            <Metamodel/>
         </Content>
      </UMLProfile>
   </DiagramProfile><UIToolboxes><UMLProfile profiletype="uml2">
         <Documentation id="AAFFFDE3-0" name="dbX-T" version="1.0" notes="dbX-T"/>
         <Content>
            <Stereotypes>
               <Stereotype name="Connectors" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <AppliesTo>
                     <Apply type="ToolboxPage"/>
                  </AppliesTo>
                  <TaggedValues>
                     <Tag name="dbX::solved_by(UML::Dependency)" type="" description="" unit="" values="" default="Solved by"/>
                  </TaggedValues>
               </Stereotype>
               <Stereotype name="dbX-T" notes="dbX-T" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                  <AppliesTo>
                     <Apply type="ToolboxPage"/>
                  </AppliesTo>
                  <TaggedValues>
                     <Tag name="dbX::Problem (UML::Class)" type="" description="" unit="" values="" default="Problem"/>
                     <Tag name="dbX::Solution (UML::Class)" type="" description="" unit="" values="" default="Solution"/>
                  </TaggedValues>
               </Stereotype>
            </Stereotypes>
            <TaggedValueTypes/>
            <ViewDefinitions/>
            <Metamodel/>
         </Content>
      </UMLProfile>
   </UIToolboxes></MDG.Technology>

15

Automation Interface, Add-Ins and Tools / Re: MDG Meta-constraints

« on: October 22, 2021, 07:08:15 pm »

Hi,

I have defined a stereotype relationship between two element stereotypes i have defined. If a place the two elements on a diagram and use the quicklinker to add a relationship, my stereotyped relationship is on the quicklinker. All good. However if i drag the quicklinker from a stereotyped element to empty space on the diagram, the quicklinker does not offer/contain my second stereotyped element. Its the latter bit that i can't get to work. Any clues / tips ?

If uncheck Filter to Toolbox, i'm presented with the element to create on the quicklinker. The elements and connector are in the toolbox however. So unclear what i've done wrong here...

My element stereotypes have a Class metaclass and the relationships has a Dependency metaclass, with meaning forweard/backward defined.

Regards,

Jon.