![]() MCC users can collaborate more efficiently while dealing with their tasks thanks to the built-in messaging system. All the widgets can be filtered, which makes them even more useful. We really liked the task summary widget that sums up all the work in a sharp-looking doughnut chart. What we found useful are customisable widgets that can be added to MCC dashboards. The calendar view provides a neat look at deadlines while the task board allows you to change task statuses quickly by moving task cards between columns. Task management features are helpful and transparent. For example, allowing users to edit only their own tasks or to change task assignment without a possibility to edit any other information would be a valuable addition to the existing permission set. The possibility to bulk add users using a CSV file will for sure come in handy when setting up MCC for the first time.Īll existing features are useful, but the set of permissions could be expanded to make them more robust. You can quickly add new users, create teams, assign them to projects and manage their permissions. Admin featuresĪdmin features are simple and intuitive. We’d certainly welcome such a possibility in upcoming versions. If you used Flare projects bound to source control before, you will be able to quickly start working with MCC-bound projects.Ĭurrently, you can’t perform source control tasks directly from the MadCap Central portal. Depending on the chosen model, you use the new MadCap Central window, the Source Control tab, or both. You perform all source control tasks, like push and pull, from Flare. ![]() It is certainly good to have that choice if you already have a source control solution in place, and you don’t want to abandon it after moving to MCC. In the dual-bound model, you use a system like SVN or Git, and MCC serves as an additional repository. In the single-bound model, you use MCC as your primary source control system. Source controlĪs far as source control goes, MadCap thought of two alternative solutions – a single-bound and dual-bound model. The whole process is quick and intuitive.Īt this stage, only MadCap Flare 2016 r are integrated with MadCap Central, which means you need to consider additional costs and potential issues related to upgrading Flare, unless you’re planning to get the new Flare version anyway. You upload and import projects directly from Flare, using the new MadCap Central window. MadCap Central Review Flare integrationĪs we would expect, the new platform is designed primarily with Flare projects in mind. We decided to spend some time with MCC to see if companies providing technical communication services, like 3di, could consider it as the primary tool for day-to-day work. The idea of handling all those processes with a single tool sounds great. A cloud-based, centralized solution for project hosting, build automation, task management and team collaboration – this is what MadCap Central (MCC) is meant to be.
0 Comments
Leave a Reply. |