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

Pages: [1] 2
Use the link bottom right of this very page.


Thanks! Going to wait for reply on my last more detailed question, just to make sure this issue is not self-inflicted due to incorrect usage of Call Activities.


Is the global re-usable process (activity/child diagram) being called, stored outside of the project browser package/folder structure  that you are exporting?   If so that could be the reason it gets dropped.

I was hoping you could elaborate on this a bit more, as you may have identified one cause of our broken link to Call Activity issues.

If we identify an activity or sub process as a candidate to become a Call Activity (global re-usable process), what is the correct usage if it is needed by another higher/lower level process branch?

For example, B. is the parent process and contains and uses Call Activity B. As modeling progresses into other branches, we discover the same Call Activity can be used by parent processes B.1.2.4 and B.

No, what is the procedure for completing that?

No, it is part of the same package/folder structure.

We are using Call Activities (BPMN 2.0) within our business process diagrams, and then linking them to their relevant diagrams.

We also each have to work locally and then use XMI Export, the XMI Import Merge up to the client's master repository. (I use the Direct merge option as I am the only one currently on the team using ver 13.0 EA.)

After the Import completes the link from the Call Activity to the Child diagram for it, is dropped and has to be added back in manually on the repository copy.

The main reason to use XMI Export/Import is the lack of SVN being deployed and used by the client. The team and I are hoping that will change in the very near future, although I personally feel the client will need to make additional improvements regarding network and DB optimization too.

General Board / Re: Refresh all diagrams after updating style
« on: December 18, 2016, 11:38:13 am »
Thanks everyone for the feedback! I'll try these Monday. And yeah this is a standard element/artifact Checklist, which literally gives a custom 'list' of items to check off as completed, in our case a simple status progress. (I'm actually hoping to convince the client to replace it though.)

General Board / Re: Refresh all diagrams after updating style
« on: December 16, 2016, 05:36:10 am »
Yup, know about the keyboard shortcuts and menu access. Issue is it does not apply changes 'globally' as noted above to all identical elements in all diagrams, just that diagram you are currently in.

General Board / Re: Refresh all diagrams after updating style
« on: December 16, 2016, 02:05:34 am »
I have a similar issue and request. It clearly states in the ver 13.0 User Guide, topic, Set an Element's Default Appearance, that you can apply an appearance change to all diagrams containing that element. The one I am now having to target, yet again is the default appearance for the Checklist element, lite blue background color, client wants it white.
<Quote from topic.>
All elements that you use have global default appearance settings for:
•The fill, border and font colors
•Font styles, including font face and size
•The border thickness

You define these settings on the 'Preferences' dialog. However, you can change the default appearance for a specific element on all diagrams on which it is found, using the 'Default Appearance' dialog.
</Quote from topic.>

I have yet to discover how to get this to work, in my prior versions of EA and now 13.

Bugs and Issues / Sparx Systems Cloud Services [2003] error
« on: November 09, 2016, 01:40:03 am »
Received this pop-up/error message during import of an XMI file, size is 102MB.

Sparx Systems Cloud Services [2003]

Transmission error communicating with server.
The operation timed out.

EA version 12.1. 1224 (Build: 1224)

Our current work configuration is: We all work locally on models, export our models via XMI and hand-off to a team admin with a centralized local of EA that consolidates and combines the individual XMI via import. That is then exported from the admins local and imported to the EA repository.

The prior team admin was using a laptop with 8GB, and the one I've been assigned has only 4GB (3.88GB usable.) I'm curious if this is contributing to this as uploads are and always have been painfully slow.

Automation Interface, Add-Ins and Tools / Re: Office MDG Performance
« on: November 05, 2016, 09:42:36 pm »
Yes, and still an issue over a year later. My guess is either not optimized or cannot be optimized.

Sure, the UI that allows defining the decision table has a fixed layout. But you can then choose to render the decision table in either way defined by the specification. The editor itself doesn't have basic behavior like re-ordering. I didn't know that previously. It's comments like that that I was hoping for when I was asking for specifics. If you look at what we have and identify a few improvements that would make you want to use it, they are much more likely to happen.

The decision tables are available to the code generation templates, which means they can be used for any language or platform. Although I don't think there are default templates for many.

Right, so you can have business rules as columns or rows; Table orientation, section 8.2.2 of the spec. That is at best a primitive and beginner's implementation of the DMN spec. regarding decision table structuring.

It needs to be far more flexible and Excel spreadsheet-like. Decision and rule authors need the ability to add an additional header cell and multiple sections for more than one set of Conditions (Inputs) and/or Conclusions (Outputs). This is something that has the potential to be a tool used by the less technical business folks, who in most or many cases intimately know the rules and decisions of a business.

Your developers can just look at the table examples in the spec., and read Bruce Silver's blog on the topic too. Mr. Silver contributed quite a bit to the evolution of the spec from 1.0 to 1.1, while writing a book on the topic, "DMN Method & Style".

As already stated somewhere in the form, I have several use cases for using the decision table feature, but for me it is useless just because of the “very primitive” implementation.

As I remember it is even not possible to rearrange things, apart of deleting and adding anew.

I cannot imagine who gets value from that feature with the current implementation.

@ PeterHeintz - Thanks for helping drive my point by posting and chiming in! And yeah, as I've gone through BPMN 2.0 based process flows, I've had to do exactly that; delete and add new as part of rearranging the rules.

@ Simon - "any decision table in the specification" is subjective. And I can tell tell you specifically, no you cannot currently model any of the decision tables in the spec. Simple, very very limited ones, yes. Decision tables; it is all about structure and choices of layout that make it powerful. That and being able to generate code for business rule engines. Please read Bruce Silver's latest book and/or website on the topic:

Other tools are moving forward, at at least impulse power, while EA & Sparx isn't even in the game yet, or just barely. As it stands now, I'd either have to resort to Excel spreadsheets to get the decision table layouts I need for clients (I now have templates for these), then link those to my Business Rule Tasks, OR use another tool entirely. The later negates my using and renewing my Ultimate license annually.

General Board / UID and PW for dashboard.eap file from webinar?
« on: September 26, 2016, 05:25:42 am »
This webinar: Creating Charts in Enterprise Architect to Aid Decision Making

When trying to load it in EA, you get a popup asking for the repository UID/PW.

Simon M,

Thanks, have already done that and the correct reference is BPMN Business Rule Task, not BPMN Business Task as you noted in your reply.

The issue is your current Decision Table & Editor functionality; very primitive. Table layout is limited. Interaction via the editor regarding rows and columns; primitive.

So as it is in 12.1 it does not even remotely support the full DMN 1.1 specification for decision tables.

Pages: [1] 2