List of new features in 1.0.332

List of new features in 1.0.323

List of new features in 1.0.316

From today version’s numbering of any TimeMaker product will be in new format. Until now we was using <Major Version> . <Minor Version> . <Minor Minor Version> . <Release>.

New format is: <Major Version> . <Minor Version> . <Release> . <Build>. What it means?

Major Version is used forMajor breakthrough, like implementation of own programing language, etc..

Minor Version is used for new milestones. We are now looking for 1.2, which should bring final version of new plans, meeting, TMMail, Editor, etc..

Release is to differenciate daily created versions.

Build is only for internal purposes and it may happen that it will not be increased between Releases.

List of new features in 1.0.1.311

List of new features in 1.0.1.309

List of new features in 1.0.1.307

NEWER, EXCITING AND EVEN MORE AMAZING IN TimeMaker - Leadership Software

SENIOR DATE MOVE FEATURE EXPANDED

THE PROBLEM:
In TimeMaker (like in life) Production Tasks , Commands and Plans have Target Dates and sometimes they need to be moved.

The mechanism for moving a Target Date is:
1. The Performer of the task realizes he is not going to complete the task by the assigned Target Date.
2. The Performer asks for a Date Move from the Owner of the task.
3. The Owner of the task may or may not approve the date move request.

At times it happens that the Owner of the task is the junior of the Performer and so the Performer of the task has Senior Rights (he can act as an Owner in regards to the task) and so has the ability to Bypass as Owner . In such a case, it sometime dose not make sense for the Performer (who is a senior of the Owner) to ask for approval to move the Target Date. The senior should have the ability to move the date without asking his junior for approval.

THE HANDLING:
As of version 1.0.1.293, TimeMaker allows the senior, as part of his Senior Rights options, to execute a Date Move without asking for approval from the Owner (his junior).

The mechanism for moving the Target Date in this case is:
1. The Performer of the task realizes he is not going to complete the task by the assigned Target Date.
2. The Performer uses his Senior Rights and uses Bypass As Owner option and executes a Date Move.
3. The Owner of the task receives a notification that the item’s Target Date has been moved.

In a case when the Owner wants to move the date of the task the Owner will execute a Date Move and the Performer (If diffrent than the Owner) will get a notice of the change in the target date.

All Tasks are assigned by an Owner to a Performer with a date for completion called a Target Date. At times, the Performer cannot complete the assigned Task by the Target Date. When this occurs, the Performer requests a Date Move to allow more time for completion of the Task.

To request a Date Move, the Performer clicks on the button . If the Task was assigned by an Owner other than the Performer, the Owner will receive the Date Move request. The Task remains in the Performer’s Inbox at the original Target Date until either accepted or rejected by the Owner of the Task.

When received by the Owner of the Task, the Date Move can be accepted or rejected. If accepted, the Task moves in the in the Performer’s Inbox in accordance with the newly approved Target Date. If rejected, the Task must be completed by the Performer prior to expiration of the original Target Date. If the Task was assigned by the Performer to him or her self (meaning, the Performer is also the Owner), the Date Move is automatically approved.

Read the rest of this entry »

List of new features in 1.0.1.305