Share your experience using Eclipse DocOrigin BCC

We use this product for issuing company checks.

OnlineCheckWriter helps a lot and with this software, it makes the job easy. It helps with my check writing, then if I have the wrong ones, they have a tool that helps to check and correct errors. This is important to the organization.

The most valuable feature is that it ensures that my check writing is correct. It is very important for an organization to help avoid problems.

OnlineCheckWriter guarantees that you are satisfied with their product, and consumers would be proud of the product.

The features are advanced, which makes your work easy and guarantees that you are satisfied.

The software should be optimized further.

Widgets need to be more specific.

I would ask the vendor to please do their best to make more improvements and maintain customer satisfaction with the product. 

Stability-wise, this is good software.

This is good and convenient software and we have had no trouble with scalability.

Technical support is very responsive.

OnlineCheckWriter is the first such solution that we have used.

My advice is to look at OnlineCheckWriter, it helps you a lot.

We evaluated other options online.

Overall, this is a great idea and a good product. If you are looking for check printing software, or bank account slip then this is for you.

We use the product to get an understanding of hotspots, code health, and team dynamics. It helps us understand which section of the codebase is under active development and changing more often than others. This is very informative and helps narrow down the focus to a smaller part of the code base. We have been using this product on-premises on various projects and get insights that are not there in any other tool we have looked at so far.

We have the ability to generate reports, use API keys, and integrate this into pull requests with Git or Azure DevOps and get it into our CI/CD pipeline for continuous monitoring.

CodeScene helps us understand the evolution of the codebase and identifies hotspots which help to focus on action planning and not worry about every issue in the codebase. This makes it easy to focus on areas that will give immediate benefits.

If we need to roll out, there are changes in the team composition, or we have an attrition case, CodeScene allows us to understand who is doing what instead of relying on just a statement from an architect or project manager. This data-driven methodology is what sets it apart. The simulation that is available is another great way to plan future action plans.

The three main aspects we like are:

1. Hotspots: This is the core of the product and helps us to focus on the smaller and most impactful areas of the codebase.

2. Code Health and Code Complexity: This helps us understand the issues and what we need to fix and how. CodeScene provides a summary of the method and function level and helps focus on a smaller section of the files instead of looking at everything all at once.

3. Knowledge Map: This helps us understand team dynamics such as how developers have worked on the code and how fragmented the code is. There's information around knowledge loss and knowledge islands that is very informative.

Wild card search options across different sections would be very helpful. For example, having the ability to find all those files which have a knowledge loss of 100% and have a code health score of 1 could be very useful. 

The generated reports could be improved further. 

The ability to do an open-source vulnerability check (SCA) would be also helpful since SCA also relies on a static codebase. 

Some of the views could drill down between each other so that we could move from one view to another and be able to link the information provided.

I've used the product for almost a year.

I didn't use another solution.

The setup is very easy. It has both a Docker option and a standalone option for on-premises or a SaaS cloud option. Licensing costs are reasonable given the functionalities.

I didn't look at other options.