Messages

16

General Board / Re: Change values in workflow script

« on: October 09, 2018, 09:39:21 pm »

Hi Geert,

with your support I managed to implement my addin using VisualStudio and C#. Thanks a lot, I've learned a lot from this.

17

General Board / Re: Status property of diagrams

« on: October 09, 2018, 08:52:55 pm »

Hi Geert,

now I understand your point, and I agree.

Nevertheless I think that it would be a useful feature, e.g. for use in (workflow) scripts or addins. There is a version property in diagrams, so they are prepared for a development process with changes. A status property could represent the current development status.

Packages have a status property using a EA.Element class member variable, although they are no requirements. I find it useful to add EA.Element class features to Diagrams, too.

18

General Board / Re: Status property of diagrams

« on: October 09, 2018, 08:33:17 pm »

Thanks, Geert, for the explanation of the status coloring (and again for the other help you gave me).

And also thanks to PeterHeitz for the (partial  ) agreement.

Regarding the diagram as a requirement element I can't agree. E. g. an use case diagram is an 'official' way to represent a customer requirement. Why should I place an use case diagram if I additionally have to write a text requirement that describes the same issue? If I did that I would have to edit both in parallel in the case of changes, which is a serious source of errors and inconsistencies. Am I wrong here?

Of course the use case will result in several functional requirements in a latter stage of developing the architecture of a system. Since these have a dependency relationship to the use case diagram they can (and have to) be changed when the use case has changed.

On the other hand e. g. an activity diagram is part of the modeling. In my opinion it should be able here to set a status to represent the state of completion or development from a kind of 'draft' up to the finished and fixed state that tells the developer(s) that the can start to implement this activity.

19

Suggestions and Requests / Status property and tagged values for diagrams

« on: October 09, 2018, 07:30:47 pm »

For using diagrams in requirements engineering, it is needed to have at least a status property and tagged values in diagrams, as they are available in elements.
Maybe is should be possible to add an element reference to a diagram as packages have it (EA.Package.Element). In my opinion this can solve the problem since all element properties will be available to a diagram too, then and it should be able to do that without a database change (adding diagram to the t_object table).

Maybe there are more requirements engineers that have an opinion about that theme?

20

General Board / Re: Status property of diagrams

« on: October 09, 2018, 06:53:53 pm »

First, thanks to all for the answers. I will try to make a suggestion in the Suggestions and Requests part of the forum. Maybe it helps  .

Unfortunately it also seems not to be possible to add a tagged value to a diagram. The 'new tagged value' button is greyed out when I select a diaram.

This is very disappointing since so I can't use diagrams for requirement engineering.

Edit:
Additonal question: What means the setting 'Shaow status colors (all diagrams)' if I can't set a status to a diagram?

21

General Board / Status property of diagrams

« on: October 09, 2018, 03:16:14 am »

Hi all!
Why don't have diagrams a status property like elements and packages have? Or if the have it, why can't I see it in the properties dialog?

I'd appreciate any help, thanks!

22

General Board / Re: Change values in workflow script

« on: September 08, 2018, 06:31:32 am »

Hi Geert,

thanks again to you, for your helpful hint and for your wishes to me. After some searching I got it to find the description of these events. Indeed I managed to overlook the whole broadcast event chapter before
But now I know how I will proceed after my holidays and I can enjoy them better. THX!

Jörg

23

General Board / Re: Change values in workflow script

« on: September 07, 2018, 10:29:44 pm »

Thanks to your help (here and on your page https://bellekens.com/2011/01/29/tutorial-create-your-first-c-enterprise-architect-addin-in-10-minutes/) I managed to create a simple addin in C#.
Now I'm looking for the appropriate event to get notified when a user changes the status of an item. The only ones I found were "EA_OnOutputItemClicked" and "EA_OnOutputItemDoubleClicked", but the information about these are very rare. Is one of these Event functions the right one for my purpose? And, if you could be so kind (and patient  ), could you give me a hint how to proceed?

I cloned your Framework from Github, but at the first view I didn't find the part that could help me here, although it seems to be helpful in a later stage of my pursuit to make requirements engineering more secure in EA.

Thanks again till here!

P.S.: Since I have to go to holidays today    it might take a while until I will be able to proceed with my task. So please dont be angry if I don't answer for a while.

24

General Board / Re: Change values in workflow script

« on: September 07, 2018, 05:21:37 pm »

With other words: No?

25

General Board / Change values in workflow script

« on: September 06, 2018, 02:20:04 am »

As said in the title I would like to change item values in a workflow script. More exactly, I want to automatically increase the version of a requirement if a specific user (or a member of a specific group) changes the status to 'Approved'.

Unfortunately I seem not to have access to any repository items (Repository object) in a workflow script. I managed to change the Version of the current selected element in a script in the 'Normal' group by calling the script in the scripting console.
When I include the script in my workflow script, it tells me (in the System Output window) that the variable 'Reposotory' is not defined.
Even if I try to call it using the App-object (GetObject(,"EA.App") and get App.Repository object; I know it is marked as read only) just makes the Application freeze for a while and finally doesn't change the version but gives a message:

Timeout invoking script   
AllowStatusUpdate("Implemented","Mandatory")   

Is there any way to achieve my goal?

26

General Board / Re: workflow script not called

« on: September 06, 2018, 12:29:54 am »

I don't know how, but I solved one of my problems. In my project I was able to disallow Status update by setting the return value of the function to false. I wasn't aware that I have to reload the scripts to make changes effective. 
Also the Message about the type conflict I  accidentially make disappear after some changes. I just edited some stuff which was generating an error (I wanted to test 'option strict', which isn't available here and added some text after the PreAllowStatusUpdate function header), deleted the inserted stuff, reloaded the script and the Message was gone.

Edit: P.S.: How do I mark a topic as solved?

27

General Board / Re: workflow script not called

« on: September 05, 2018, 07:17:50 pm »

Hi Dermot,

thanks for your reply. I already had downloaded the example and have read all the documentation for workflow scripts I could find.
Yesterday in the example project I had a weird error message about a type conflicht in PreAllowStatusUpdate, after a restart this was ok again. But also in the example project the workflow functions seem not to be called. E. g. I logged in as a support member and was able to edit tags, although I shouldn't. There also was no message output (just tested again).
All I see in the System Output window (script tab) is "VBScript workflow engine created". The System tab is empty.

Do you have any idea what else I could test? Does the 'Session.Output" function basically work in workflow scripts?

Edit: I added PreAllowStatusUpdate and AllowStatusUpdate functions to the 'Validate' script (direct copy fom the default workflow script template) and set the return value of AllowStatusUpdate to false. ThenI saved the script and reloaded the project. Not only the changes of the status of an element (in the Properties/General dialog) are still possible, the type conflict message for PreAllowStatusUpdate comes again. Even after deleting the PreAllowStatusUpdate function from the script (and save and project reload) the message appears in the System Output window's 'Script' tab.
Something really goes wrong here and I have no clue how to proceed to get it working.

28

General Board / workflow script not called

« on: September 04, 2018, 10:24:06 pm »

First, Hi to all here in the Forum!

I'm pretty new to EA Scripting and I want to edit the workflow script. I created a new workflow script set the return value of AllowStatusUpdate to false. Nevertheless the status is changed. I added some output to the functions (Session.Output) but nothing appears in the system output window. It just seems not to call the functions. Same happens with the other functions (chenge version, phase, ...)


I'm really helpless in this point. Can anybody tell me what I do wrong here? I would really appreciate any help.