Messages

1

PCS General Board / Re: Problem with creating new elements in Prolaborate: technology not recognized

« on: May 31, 2022, 02:01:41 am »

Hi Geert,

Thanks for pointing this out!  I've followed the link and meanwhile i've reported it as a bug also. 
Allthough I'm still curious if other users have also experienced the same behaviour, and/or if it might be "fixed" in higher versions of EA / prolaborate.
and/or there might be a workaround?  Maybe I missed out a screen in prolaborate where you can create a single element instead of the "bulk creation" / excel alike interface?  OR any other workaournd?

kind regards,
Joris

2

PCS General Board / Re: Problem with creating new elements in Prolaborate: technology not recognized

« on: May 30, 2022, 11:01:38 pm »

here is a "test" MDG that you can use to reproduce, it contains one tagged value that is an enumeration. 

Instructions: 
- Save the following as .XML file, and import it in your EA repository.
- Go to prolaborate --> add modeling language --> import the same XML file.
- in EA:  create a class with "TestTech" as stereotype from this technology.
check the properties of the created element.  If correct, you'll see a propery called "CustomTag", with as value "Value1", and it shows a dropdown limiting the possible values to "Value1, Value2, Value3"
- in prolaborate:
   - navigate to the element, check if you see the same dropdown.
   - try the "add elements" button, and add a new element of "testtech" stereotype
   - navigate to the element just created and check if you see the dropdown or not.
   

Code: [Select]

<?xml version="1.0" encoding="windows-1252"?>
<MDG.Technology version="1.0"><Documentation id="001" name="TestTechMDG" version="0.1" notes="This is just a test"/><UMLProfiles><UMLProfile profiletype="uml2">
<Documentation id="D3063694-C" name="TestTechProfile" version="1.0" notes="testtechprofile"/>
<Content>
<Stereotypes>
<Stereotype name="TestTech" notes="">
<AppliesTo>
<Apply type="Class">
<Property name="isActive" value=""/>
</Apply>
</AppliesTo>
<TaggedValues>
<Tag name="CustomTag" type="enumeration" description="" unit="" values="Value1,Value2,Value3" default="Value1"/>
</TaggedValues>
</Stereotype>
</Stereotypes>
<TaggedValueTypes/>
<ViewDefinitions/>
<Metamodel/>
</Content>
</UMLProfile>
</UMLProfiles></MDG.Technology>

3

PCS General Board / Problem with creating new elements in Prolaborate: technology not recognized

« on: May 30, 2022, 07:39:41 pm »

Hi,
I’m running into trouble in Prolaborate (v3.6.0.0) when creating new elements of a stereotype belonging to a custom made MDG technology:  the newly created  elements are not recognized as being part of the technology that was used.

Some more explanation:  When pressing the “Add Elements” button in prolaborate, and selecting the correct stereotype, the “excel alike” interface seems to behave as expected: the predefined tagged values appear as columns, the tags that are defined as enumerations show the dropdown menu with the correct possible values etc..     After successfully committing, the new elements have been created, they have the correct stereotype, but the tagged values (although they have the correct name) are not seen as part of the technology: Tags that should have been enumerations are now just a “flat” string where you can type any value, the tags are also not recognized by the prolaborate user interface “profile” we configure, etc..
When consulting the newly by-prolaborate-created elements in EA (v15.2.1559), we see the same “wrong” effect: They carry the correct tags… but these appear under the “tagged values” tab instead under the tab belonging to the technology, and none of the built-in restrictions on  the values of these tags  (like enumeration, structured datatypes etc..) are applied.

Anyone else experienced the same behaviour and/or has a solution?  I really hope we can fix this, because at this moment it’s a “show stopper” for embracing Prolaborate as a tool for a business users in our company. 

4

Automation Interface, Add-Ins and Tools / Re: SQL Query that reports 1..* related elements as comma separated list on one row

« on: March 16, 2022, 09:04:42 am »

Hi Geert,

thank you VERY much for this fine piece of SQL magic!!!
I applied it to my "half way" query.. and it works!   and I probably will be using this pattern a lot in many other use cases.

grtz,  Joris

here's the result:

Code: [Select]

SELECT t_object.ea_guid AS CLASSGUID, t_object.Name, t_object.Note,
Replace((
  select STUFF((
select distinct ',' + s.Name
from  t_connector cs
inner join t_object s on s.Object_ID = cs.End_Object_ID and s.Stereotype = 'capability'
where cs.Start_Object_ID = t_object.Object_ID
  FOR XML PATH ('')
),1,1,'')
), ',', char(13) + char(10) ) as [Capabilities],
VendorName
from t_object 
-- look for associated vendor
left join (select vendorconnector.Start_Object_ID, thevendor.Name as VendorName
from t_connector vendorconnector
inner join t_object thevendor on (  thevendor.Object_ID = vendorconnector.End_Object_ID )
where (thevendor.Stereotype = 'company'))
AS vendorjoin
ON vendorjoin.Start_Object_ID = t_object.Object_ID -- left join with answer
-- basic conditions for the resulting t_objects
where (  (  t_object.Stereotype = 'tool' ) and  (t_object.Object_type = 'Component')  )
ORDER BY t_object.name


5

Automation Interface, Add-Ins and Tools / SQL Query that reports 1..* related elements as comma separated list on one row

« on: March 15, 2022, 10:40:00 am »

Hi,  I'm struggling with a SQL query for reporting on a software catalogue based on the following model elements in EA:
- we use components  to represent software tools (stereotype "tool"),
- each tool can have one vendor associated to it (component with stereotype "company"),
- each tool can have many capabilities associated to it (activities with stereotype "capability").

I try to create a SQL query that has this desired result:

name  | notes                     | vendor   | capabilities
----------------------------------------------------------
tool 1 | description of tool 1 | vendor x | cap1, cap2, cap3
tool 2 | description of tool 2 | vendor y | cap2, cap4

The hard part is: the comma separated list of capabilities.
I'm halfway: I created a query that results in the correct collums, but has too many row (each for one of related capabiliies):

name  | notes                     | vendor    | capabilities
-----------------------------------------------------------
tool 1 | description of tool 1 | vendor x | cap1
tool 1 | description of tool 1 | vendor x | cap2
tool 1 | description of tool 1 | vendor x | cap3
tool 2 | description of tool 2 | vendor y | cap2
tool 2 | description of tool 2 | vendor y | cap4

We use a SQL Server DB, (and EA 15.2).

Here's the "halfway" query - I know the answer probably relies on SQL functions like STRING_AGG, but I can't find how to apply..
----------------------------------------------------------------------------------------------------

SELECT t_object.ea_guid AS CLASSGUID, t_object.Name , t_object.Note , VendorName , Capability
from t_object 
-- look for associated vendor
left join (select vendorconnector.Start_Object_ID, thevendor.Name as VendorName
            from t_connector vendorconnector
            inner join t_object thevendor on (  thevendor.Object_ID = vendorconnector.End_Object_ID )
            where (thevendor.Stereotype = 'company'))
         AS vendorjoin
         ON vendorjoin.Start_Object_ID = t_object.Object_ID -- left join with answer
-- look for associated capabilities
left join (select capabilityconnector.Start_Object_ID, theCapability.Name as Capability
            from t_connector capabilityconnector
            inner join t_object theCapability on (  theCapability.Object_ID = capabilityconnector.End_Object_ID )
            where (theCapability.Stereotype = 'capability'))
         AS capjoin
         ON capjoin.Start_Object_ID = t_object.Object_ID -- left join with answer2         
-- basic conditions for the resulting t_objects
where (  (  t_object.Stereotype = 'tool' ) and  (t_object.Object_type = 'Component')  )         

ORDER BY t_object.Name
------------------------------------------------------------------------------------------------------
Any help would be greatly appreciated!!