List of new features in 1.0.371

To address difficulties in sending attachments when using TMmail, we recently increased the size of each e-mail capacity from 10MB to 20MB.

This does not mean that users can send 20MB attachments via TMmail. E-mail is quite ineffective in the sending of the files. When you attach a file to an email, the file is converted to a text form (base64). This text form increases the size of each attachment by approximately 30%. Because of this increase in file size, the maximum size of file you can send via TMMail is 16MB.

If you need to transfer larger files between TimeMaker users, you can use send them via a TimeMaker message instead of sending as an email. When sending via a message, you can send approximately 100Mb’s - and it will be sent quickly, even between many users.

List of new features in 1.0.361

TMmail

How does TMmail delivery work?

Let’s first start with some basic theory. You send an e-mail to x@domain.com. This mail is delivered first to your SMTP server, designated as Server1 in the diagram below. (en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol).

This server will separate the domain (x) from address (domain.com) and will determine to which server the e-mail should be delivered. This server (designated as Server 2 in the diagram below) is in the domain defined as MX record (en.wikipedia.org/wiki/MX_record). It also is an SMTP server.

Your SMTP server (Server 1) will then deliver the e-mail to the server in MX record (Server 2).

(more…)

Authorize Date Move Request - The Concept

In TimeMaker, any Production Task, Command or Plan assigned to be executed has a Target Date. A Target Date is the date by which the task needs to be completed.

At times a task cannot be executed on time and the Performer should submit a Date Move request to the Owner of the task. A Date Move request acts as notice to the task’s Owner that the task may not be completed on time, and allows the Owner to approve or disapprove the request to change the Target Date and handle the consequences of the change.

Above is a simple situation. A more complex situation occurs when the organization is composed of multiple command layers.

Let’s take an example of a simple organization:

(more…)

ANOTHER TIME MAKER POWERFUL FEATURE EXPANDED

PLAN’S USER’S RIGHTS

Plan’s user rights define the rights a user or users has over a plan or part thereof. By default, the system will grant the user rights for a plan or part of a plan based on the user function in the plan however, the plan’s Owner or a senior may grant any of the rights to any user in the system.

The following are the TimeMaker’s Plans user rights:

Owner’s Rights - Owner’s Rights gives full control over the plan and its steps.

Sub Owner’s Rights - Sub Owner’s Rights gives Performer rights to the Plan (Performer can see the plan and perform Date Move request, Clarification request, Reject, Completion Report, Redirect as well as the basic actions - Data Interchange, Query). The Sub Owner’s Rights allow the user to act as Owner on the planss sub items.

Performer’s Rights - At the TimeMaker the Planss Performer is the Owner of all the Plan’s sub items. Performer’s Rights gives the Performer the ability to perform Date Move request, Clarification request, Reject, Completion Report, Redirect as well as the basic actions - Data Interchange, Query. A user with Performer’s Right can not insert, delete, activate or deactivate steps of the plan.

Read Only Rights - Read Only Rights gives the user the ability to only see the plan and its steps with no other rights.

Limited info Rights - Limited info Rights gives the user the ability to see the Plan’s subject only. The user will not see the Plan’s body and will not see the Plan’s steps.

Inherited Right - Inherited Rights is a kind of ‘restore default rights’ right. When selecting this right the user will be assigned the rights based on his function at the plan and its steps - the Owner will get Owner’s Right and the Performers will inherent the Performer’s Rights.

(more…)

Bacause TimeMaker is more complex system than e-mail, we need different columns. In previous versions there was two columns, similar to e-mail. We called them Sent Date and Target Date. It was little confusing for end users, that the Target Date is containing Received date. Also was not possible to organize Inbox be recieving date, because production task have in Target Date it’s Target Date. Therefor we has implemented in TimeMaker version 1.0.1.289 new columns in Communication: Received Date and Tag Date.

From now date columns contains those values:

Production Task: Sent Date - date of send, Received Date - date of receive, Target Date - target date of task, Tag Date - tag date, if not set then target date

Other Items (Messages,E-mails, etc..) : Sent Date - date of send, Received Date - date of receive, Target Date - date of receive, Tag Date - date of receive