Disable Task Occurrence dropdown list

Hi Nicola,

you could put all tasks into a specific folder where the modelling people have no access rights to. Maybe you could then schedule a report that runs at night and moves your objects into that folder.

Best,

Veronika

Hello Veronika,

I do not think, that is feasible, because these tasks need to be visible to the modeller. He is in the course of creating them and every step he models adds to the list of hits.

I think this is a valid point. You never want to reuse tasks in a process, because from a methodical point of view this does not make sense, while the resource objects (roles, application systems, risks etc.) need to be reused as much as possible. I would suggest you report an idea on https://aris.ideas.aha.io/

Idea: In a method filter you should be able to define symbols in the context of a model type for which the automatic search for existing definitions is disabled. In other non-process model types you may well want to be able to search for definitions of a function object, so you can reference them. So this feature should be specific to the model type and symbol type.

Hi M. Zschuckelt,

I somewhat disagree. I want to see where people complete the same tasks. So, for me (as also in other system reusability for tasks/functions (whatever you want to call it)) is crucial when it comes to process harmonization and standardization. So not being able to reuse tasks does not seem reasonable to me. (and most likely it doesn't help Nicola, now ;) )

I personally like the implementation in Architect a bit better, where I can actively search for occurence copies. However, if you implement a proper folder structure including permissions, then the likeliness is anyhow reduced that you find objects that carry the same name. 

Just my two cents :)

Best,

Veronika

Hello Veronika,

if you reuse tasks you create a mess on definition level. A task that occurs in multiple processes has got the superset of all predecessors and successors from all processes where it occurs on the definition. The same applies to the resources it uses: In one process it may be carried out by role A, in another by role B etc. and you only have one FAD. It also poses a serious risk with regard to the ownership of the task (and its description): Which process owner shall use his language to describe the task? You've only got one object! Do you want to deny process owners authority over parts of their process? In the end they might not want to be held accountable for it.

If you want to get a grip on reusable functionality I recommend to build a capability architecture and/or service architecture and use them as resources for the tasks, which are unique in each process.

Regards, M. Zschuckelt

EDIT: If you can read the object, you can create an occurrence copy. So the folder structure alone won't help you to avoid reuse. You would have to hide away (no read permission) most of the process landscape from the process modeller, which is not the best idea, if you do not want them to reinvent the wheel.