The look and feel, along with the ease of use of the solution's web modeling version, is an area with certain shortcomings. The web modeling part can be a bit complex or difficult for new users of the solution. Simplifying the look and feel to make the web modeling part easy to use can greatly improve iGrafx.

The solution could benefit from improvements to its interface. More specifically, when compared to other tools, the process modeling features lack symbols or object types that are used to represent the information or data within the process. By improving this, the user will have a more varied gamut of tools to showcase the information they have within the process.

Not all processes are the same. We have many types of domains, and all those domains have different types of processes. Adding additional symbols or object types would enable us to better express ourselves, which would result in a more detailed and accurate process.

iGrafx would also benefit from including more diagrams like other solutions offer, along with BNM, which has constructs that can be used.

If the price of the solution was more competitive, it would have made things easier for our company to extend the usage. Because we are mostly Microsoft-oriented, there are people more inclined towards Visio than iGrafx.

I'd like to see additional features such as a multi-language option which is currently only possible if you publish in Java. I'm publishing in HTML and it's not possible to use multi-language. The same applies concerning the ability to increase and decrease size which would provide extra functionality when publishing. If you're not in the cloud and you're a single user, these things would make a difference. 

With iGrafx, the implementation and the licensing were pretty complex. Now they have simplified it, so that problem has lessened. They had a very elaborate setup. Depending on the implementation type of module and type of users, they had different account types to be created. It used to get pretty hard to convince people to use it based on what is required. However, luckily, they simplified it.

iGrafx is working on integrating a process mining tool as part of the solution itself. I'm looking forward to that. We’re excited to get to the point where you can build the processes from the data which you have from the other systems.

There are a few areas iGrafx which could improve, probably the biggest area would be to support iOS as well as PC, so clients don’t have to emulate PC on an iOS platform.

I would like to see a lower price, although when used correctly, you can have a good return on your investment.

Its licensing can be better.

Process mining isn't so clear yet. 

I would love to see a template and shapes for customer journey mapping.

There is room for improvement in the printability of the flows. The workflow or the shape — if I'm working on a cross-functional, multi swim-lane workflow — can sometimes get very big, and it's not easy to have a printable and readable version. This is a big problem, so I have to print it on an extremely big A3.

Something that is found in Visio but is not found in iGrafx, or at least I haven't found it, is that it allows me to have a multi-page or multi-sheet process. I'm able to split a process across many pages rather than having one big process on a page. I can link between these pages with an off-page reference.

Also, dragging and dropping shapes is not as user-friendly as in Visio. In Visio, it's very easy to work with shapes and in very few minutes you can plot a whole, multi swim-lane, cross-functional process. In just a few minutes or within an hour you can make one that is very complicated. Or, during a meeting, you can do one in Visio without being distracted by the complexity. In iGrafx, that part is not that easy. iGrafx can produce very sophisticated workflows that can cover a lot of detail. This sophistication is not always bad, but it's not always good.

Finally, one more problem that I hate with iGrafx is that the format of the files or the flows is usually in an extension called igx. igx is very a very specific format that I can't access or deal with except in iGrafx. If I'm going to edit these workflows in Visio later on, I have to use a converter. I've only found one converter, in all the online forums, to convert an igx file to a Visio file. And it's another cost, of course. You have to pay for it. So if you are using iGrafx and decide at any point that it's not meeting your expectations, you have to pay for this converter, and not only the cost for the new software. The output from iGrafx should be in a format that's more accepted by other kinds of software that deal with the workflows.

There are some minor issues where the arrow naming does inherit the right naming when creating a break down chart.

I used the single license product. The entire suite can manage complex organizations, linking it with ERP, but it is not so easy to link it to a new ERP. You have to develop specific software to do so.

The enterprise suite works on the internet and you can manage the organization structure and all the processes related to it. I think that an iGrafx partner could be more exhaustive in the description.

Unfortunately, I haven't been able to find a reseller in Mexico. The product needs better product distribution.

It would be nice to have a Spanish user interface available to us.

In the next release, I would like to see more layers like three, four, and five. It might be possible but I haven't seen it yet. 

It would be helpful to be able to do more analytics and generate reports on historical documents that have already been uploaded to the server.

I would like to see better communication between the sensor process team and the end users.

They can reduce the cost of the product and make it easily accessible for consultants.