User Modules

Task, project & quality management
Contacts and directories module (CRM)
Web management and automation
Human resources
Asset management module

Technical Modules

Sabre plugin module
Enterprise Architect connector

System Modules

The AyMINE framework module
System services

Effect of the task on the right to modify the attached object

It is possible to assign objects to a task that are processed within the task. The task can then give those who process it the right to modify the attached objects, under the conditions specified below.

The responsible employee in charge of the task assigns the objects to be processed to the task. When assigning, it shall be verified for each one individually that the worker has the right to modify the object itself. If he does not have this right, the object is not attached to the task for processing but for information. In general, therefore, by assigning an object to a task, it is possible to delegate to someone the right to process the object, provided that the delegator has this right.

Including an object in a task does not generally give you the right to see objects that a collaborator without a task does not have the right to see. Thus, by assigning a task, it is not possible to access information that would not be accessible without the task.

Whether or not you grant the right to process an object depends on the setting of the Work Method flag and the way you are involved in the task.

Influence of the role in the task team

Only workers who are on the task team (see the team tab for the task) can be granted the right to participate in the task. Workers are generally automatically included in the team when the task is given to them. Thus, it is usually not necessary to create a team manually. But the important thing is that people are automatically included in the role of collaborators, i.e. with the right to process objects.

People in team roles have the right to process objects:

  • Collaborators
  • Decision maker
  • Verifying
    The Responsible person also automatically has the edit right, but they don't get it through the task.

Conversely, the right is not acquired by the role:

  • Consulting
  • Auditing
  • Unspecified role
    So, if you want advice from someone, for example, but they should not actively interfere with objects, you should assign them to a team with the role of consulting worker. This role is never set up automatically, it should be done by the worker ideally when the task is created.

In addition to the role, the status of the collaboration also matters. The standard is the state active and the right grants. However, if the engagement state is different (request, rejected, completed), the worker does not have the right. Thus, it is possible to take away a team member's right even before the task is completed by changing the team member's engagement status to completed. (This can be done by the worker himself.)

Meaning of the Work Method field options

The Work Method flag can be set directly in the task, but only if the task is not derived from a sample task. For derived tasks, the flag is always derived from the template and cannot be changed directly in the task. The method is thus defined by the methodology.

The method has the following options:

Does not work with objects

In case of this option (it is the default for new tasks, i.e. the default), the task does not affect the rights to handle attached objects for any team member.

The performer can change

With this option, only the person to whom the task has been assigned has the right to modify objects.

Context note:

  • Multiple tasks may be attached to an object, and some may give other workers the right to modify the object.
  • The responsible worker who created the task cannot change the object while another worker is in charge of the task. He temporarily loses rights that he would have had if not for the task.
  • The rights of people who have the ability to modify the object but are not involved in the task are not affected by the existence of the task.

In general, setting this option does not create a lock on the object and is mainly used to specify the work within the task.

The entire team can change the

With this option, anyone has the right to change the object as long as the task is active. The person who is currently working on the task has this right, but so does everyone else in the team.

This option is especially important to use when multiple people are actively working together on a task. Examples of such tasks are, for example, the development of strategies or even the preparation of contracts.

Managed step by step

This option behaves in terms of rights in the same way as the Executor can change option, i.e. only the worker who executes the task always has the right to intervene. The behavior of the whole task is different, because the task has clearly defined steps and responsibilities. Workers then have no possibility to terminate the task, it terminates automatically after the last step is completed. For each role in processing, the manager must assign workers.

This option cannot be set manually for a task. It is defined by sample tasks that contain a sequence of steps.