[Perl-workflow-devel] Making activity configs local to workflow/state?

[Alexander K. <ak-...@cy...>]

Hi all,

I've been stumbling over the fact that activity names are global
a lot lately. For example, we have different workflows that have
activities with the same name that should actually do different
things.
IMHO, activity names should be local to their workflow and (maybe?)
even their state. What do you all think about it and if you agree
with me, how would we go on to change the behaviour (possibly while
still being backwards-compatible)?

Best regards,
  Alex
-- 
Dipl.-Math. Alexander Klink | IT-Security Engineer
        ak-...@cy... | working @ urn:oid:1.3.6.1.4.1.11417