Book a Demo

Author Topic: Version 15 Beta bug: Service can't trigger another service  (Read 3373 times)

Stephan Amsbary

  • EA Novice
  • *
  • Posts: 14
  • Karma: +0/-1
    • View Profile
Version 15 Beta bug: Service can't trigger another service
« on: June 08, 2019, 05:35:31 am »
I can't get an ArchiMate Service to trigger another Service, this would negate the concept of SOA. This wasn't a problem with v13.5. I found a way to work around this issue, but thought it best to bring it to your attention.

It can properly create a trigger from process to service.

Help, Stephan Amsbary
« Last Edit: June 08, 2019, 05:43:11 am by amsbarys »

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Version 15 Beta bug: Service can't trigger another service
« Reply #1 on: June 11, 2019, 09:15:35 am »
I'm afraid you'll have to describe in a little more detail what you are doing.

The quicklinker offers me Triggers and Triggered By for any combination of Service types.

Try disabling 'Filter to Toolbox' in your quicklinker menu. Does that help?

If I choose a specialized view that doesn't include Triggering for my diagram type it won't be offered. Equally, if the view doesn't include a particular Service that won't be offered as a new element type.