Anti-Hollywood: No Actors, only Roles in TargetProcess


In the new 2.18 release we got rid of an obsolete entity that existed in TargetProcess since primeval times and caused lots of questions and confusions from our customers. We removed Actors.

That’s how the workflow edit screen looked previously — each entity state was supposed to have an Actor, and Actors were supposed to be managed for this single purpose:

manage-actors

Roles were supposed to be managed as well in another screen. This added confusion — what is Actor, what is Role, where Actor should be applied, where Role etc.  Now Roles are used for workflow setup as well, and there are no Actors anymore.

roles

In a nutshell, Actors were waste. We’re looking now to make TargetProcess less clicky, more crispy and laconic. So we said “bye” to Actors and now go only with Roles.

  • debbie
    Hi,
    At the moment we have a catch all actor of developer which allows many roles (developer, team leader, product owner etc) to see the state in their dashboard if the entity is assigned to them.
    Will you now allow people to have multiple roles?
  • There is no restriction to assign Developer on bug verification for example. You may do it if you want.
  • anadin
    Yay! nice move guys, this certainly is a big step towards a 'more crispy' Target Process :)
blog comments powered by Disqus