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 - OpenIT Solutions

Pages: [1] 2 3 ... 37
1
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).

2
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.

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

4
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.

5
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.

6
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.

7
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.

8
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>

9
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>

10
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.



11
Automation Interface, Add-Ins and Tools / MDG Meta-constraints
« on: October 22, 2021, 01:47:42 am »
Hi,

I'm just looking at replacing my Quicklinker CSV with a meta model (stereotyped relationships etc). One bit i can't figure out from the docs and various vidoes out there - if i use the quicklinker on a diagram and drag to an empty space - how to i specify which valid element stereotypes and connectors to display ? Any hints ? Docs that explain ?

Regards,

Jon.

12
PCS General Board / Re: Query Driven Doc Gen fails
« on: October 21, 2021, 07:11:33 pm »
Hi Phil,

I have lots of SQL fragments in my docs and build docs using scripts/sql - all seems fine via PCS (and direct OLE DB connection). Only difference by the sounds of things is that we are using OLE DB with the PCS database connection not ODBC. But if PCS is working - ie you can view content in WebEA etc... then this is unlickly to be the issue...

13
General Board / Delete results from model search that uses costom SQL ?
« on: October 15, 2021, 09:27:41 pm »
Hi,

I have a model search using SQL. Although i include the CLASSGUID and CLASSTYPE and can view properties. I've noted that if i right mouse click on a row in the search results i don't get the option to Delete the element. I do get this option with built in searches and those built using the Query Builder.

Is there any magic i can apply - names columns etc in SQL that will allow users to delete an element in the search results of custom SQL queries ?

Does the question make sense ?

Regards,

Jon.

14
PCS Bugs and Issues / Re: Inefficiency PCS Composite Diagram at WebEA
« on: September 14, 2021, 05:36:50 pm »
Hi,

This is a configuration in WebEA. You can either click to open composirte diagram, show mini property sheet and then click on its composite diagram link or open main property sheet. See https://sparxsystems.com/enterprise_architect_user_guide/15.2/pro_cloud_server/configure_webea_via_web.html and then https://sparxsystems.com/enterprise_architect_user_guide/15.2/pro_cloud_server/edit_webea_model_connection_settings.html

Regards,

Jon.

15
PCS General Board / Re: Prolaborate 4.0
« on: September 09, 2021, 06:48:09 pm »
Was there any indication of a release date for v4 ?

Pages: [1] 2 3 ... 37