USA/Canada: 866.259.2454 | International: +1.418.907.5184

The tale of two icons

In AceProject 4.7, we introduce non-mandatory dependencies. Those are dependencies that don’t require the predecessor task to be completed before the successor can start. For example, you don’t need to be done buying presents before you can start wrapping the ones you’ve got already.

Graphically speaking, we needed an icon that people would click to switch the dependency from mandatory to non-mandatory.

And that’s where things get interesting

How do you symbolize mandatory? Our graphic designer, Michel,  and I looked up on Google images and in icon banks, we could not find a consensus, a standard symbol that would mean mandatory. We didn’t want to invent something. If you need to explain your icon, you’ve defeated the purpose of using an icon.

This is when Michel had a great idea: why not use the line that illustrated the dependency between tasks so show whether it’s mandatory? A dotted line () would mean non-mandatory, and a solid line () would mean mandatory.

The solution was simple, but the road to reach […]

By |2009-02-17T15:48:00-05:002009-02-17|

AceProject 4.7 in the works

We’ve started testing phase 1 of AceProject 4.7 last week. So far, we’re really impressed with Pascal’s work. Not only is the software working as expected, but there are very few bugs to fix.

Phase 1 was mostly focused on improving task dependencies. Most AceProject users will tell you task dependencies are very rigid in AceProject. We use only hard logic: the predecessor task must be completed before its successor can start. Dates are mandatory. It makes it difficult to use task dependencies efficiently in the current system.

In AceProject 4.7, we introduce non-mandatory task dependencies. For dependency chains that can accept flexibility and overlap between tasks, you’ll be able to start a task even if its predecessor is not completed.

(Click to enlarge)

Even better: if your task doesn’t have dates or has incompatible dates with the predecessor, AceProject will propose some dates to you in a pop-up, so you don’t need to remember when the previous task ended.

(Click to enlarge)

We are […]

By |2009-02-09T20:44:00-05:002009-02-09|

How to get the most out of AceProject, Part III: Printers

Moving a brochure from an idea to a layout to an approved proof to a box of printed copies is no easy task.

With AceProject, printers can move files from one process to the next, and make sure that all the approvals are given before the file goes to the next process.

Create users for each production step in your workflow

At most printers, there are workstations near the presses. Those are not necessarily assigned to specific users. If you want to create a workflow that doesn’t depend on who’s running this part of the workflow, simply create users based on the process.

However you’ll need to make sure there is an email associated with this user, so they can receive email notifications.

Involve your clients

If you often work with the same clients, you can even give them access to AceProject, with limited rights, so that they can upload files, request quotes, or approve work before sending it to press.

Set Finish-to-Start […]

By |2008-12-16T14:54:00-05:002008-12-16|
Go to Top