Book a Demo

Author Topic: Way not to display owning activity on synchronized action pin?  (Read 9480 times)

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Way not to display owning activity on synchronized action pin?
« on: January 09, 2018, 10:07:54 am »
I configure an action as type CallBehavior, configure Call to point to an existing activity, and synchronize the parameters, so that action pins appear on the action in the calling diagram. Great!

The action pin names on the calling diagram include not only the parameter name and type, but are preceded by the name of the called behavior (activity). An example: "Apply pointing origin offset.PointingOriginOffsetAlg.Algorithm".

The information is correct, but I want to suppress the name of the called behavior on the calling diagram, since this is noise for the intended audience. I haven't figured out how to do this (without manually changing each parameter name, which is time-consuming and breaks the synchronization). Is there a way?

peterc

  • Guest
Re: Way not to display owning activity on synchronized action pin?
« Reply #1 on: January 09, 2018, 09:34:15 pm »
Not sure about action pins specifically, but on some elements the source of an element is hidden by unchecking "Show Namespace" found by right clicking on the diagram, select properties and then the Diagram selection and then within Appearance.

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Re: Way not to display owning activity on synchronized action pin?
« Reply #2 on: January 10, 2018, 02:55:04 am »
Thanks for the reply. I already tried changing that setting, but the value in this checkbox makes no difference for this case.

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Re: Way not to display owning activity on synchronized action pin?
« Reply #3 on: January 10, 2018, 07:00:10 am »
I probably will just want to show the names on the diagrams. I will link to types, but those do not need to appear on the diagram, and certainly the name of the called activity does not.

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Re: Way not to display owning activity on synchronized action pin?
« Reply #4 on: January 10, 2018, 09:18:36 am »
Well, now, here is something.

If instead of:
creating an action, then changing the property of the action to be CallBehavior linked to an activity

I do the following:
drag the activity I want to invoke onto the calling diagram, select Invocation, and opt to include all inherited items, the effect is the same except that the action pins do not have the invoked activity name displayed. (The parameter names and types seem to update more automatically if I change them on the called activity as well.) This might work for me.

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Re: Way not to display owning activity on synchronized action pin?
« Reply #5 on: January 10, 2018, 09:32:36 am »
I guess in the latter case I did not provide a name for the action, so it just has a type.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Way not to display owning activity on synchronized action pin?
« Reply #6 on: January 10, 2018, 10:47:05 am »
I guess in the latter case I did not provide a name for the action, so it just has a type.
Have you tried deleting the name in the former case?  Now that you've observed the latter behaviour?  If it's consistent good, else maybe another EAUI?

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Re: Way not to display owning activity on synchronized action pin?
« Reply #7 on: January 10, 2018, 11:06:19 am »
Somewhat surprisingly, that path doesn't work. I even tried a number of orders of doing things that I thought might yield positive results for one reason or other, but none of these worked.

The way that works is a good way, at least.