Minimum Tracking
It is recommended that Task Tracking is always enabled, however minimum task tracking is suited to small teams with highly trusted developers. Using this approach, there is only one task per system. All developers share the same task. (Refer to Share Task IDs.)
Only system internal task tracking activities are performed. There is no locking of objects. You cannot export by task. You cannot inquire on task history in any meaningful way.
Using *NONE (or equivalent Task ID)
You must follow the steps as described in Set Special Task ID.
A single permanent task such as *NONE can be created. Developers do not have to be authorized to this special Task ID. This task is generally never set to closed (status CLS) or finished (status FIN). If the *NONE task is closed, another Task ID such as *N01 can be created.
When you use this method, there will be no lock performed on the master system when an object is checked out because everyone is allowed to access the object.
Other forms of task tracking can be used in combination with this method. For example, you can create normal tasks that use Full Task-Oriented Tracking .
Sharing Task ID or Profiles
Another method of performing minimum task tracking is to create a normal Task ID and then authorize all developers to share this task ID. This approach can be used with Independent Visual LANSA Systems which cannot use Special Task IDs.
Another option of performing minimum task tracking with Independent Visual LANSA Systems is to allow developers to share a common user profile. Because locks are performed by workstation, not by user, Visual LANSA can still perform object locking.
Also See