Software development environments and techniques age and eventually expire. And so it is with SoftBridge Language (SBL) used within Tungsten Automation (formerly Kofax) Capture since its inception to script automation and extend user experiences.
Tungsten warned of SBL’s planned deprecation after adding support to Capture several years ago for more modern languages and techniques. Finally, with the release of Capture 11.1, SBL was completely removed, necessitating a refactoring of any remaining SBL scripting before upgrading Capture.
Of course, some software development environments live on due to the high cost of replicating business logic developed over decades, and some classic languages just lend themselves to easily solving certain workload problems. But for some environments, like Microsoft’s Visual Basic Version 6, enterprises were forced to move on whether they were ready or not.
In the case of refactoring SBL scripts, it can be a simple matter and not as complicated and time-consuming as you may think––depending on the overall complexity of a script’s intended purpose.
However, there are considerations, regardless of complexity, that any refactoring effort should follow. Some of the more important ones include:
Goals: Before starting the effort, defining the goals of refactoring the software is important. Goals can include improving performance, enhancing functionality, improving maintainability, or simply updating the technology stack.
Budget and resources: Refactoring software can be expensive. It is important to have a clear budget for the project that covers all aspects, including software development, testing, and contracting human resources with proper software stack and target environment development skills.
Timeline: A realistic timeline should consider all the steps involved in the refactoring process, including planning, development, testing, and deployment.
Technology stack: The choice of the technology stack is important. The new technology stack should be well-suited for the needs of the project, should support the required functionality, and be consistent with enterprise software standards.
Codebase: Scoping the effort requires analysis of the existing software. That analysis can find areas of the code that will benefit from modern techniques or better functional approaches.
Remember that the codebase may include elements external to the script, like Windows DLLs. One example of a new functional approach may be to transition data lookups using application-specific databases to access an enterprise data warehouse. Another example is a consolidation of external functionality into the mainline code of the new script.
Testing: Refactoring requires comprehensive testing to ensure the new software meets the refactoring goals and is free of bugs. The codebase analysis can identify test cases and help define both automated and manual test activities.
Refactor with Confidence
Transitioning SBL scripting to more modern techniques in Tungsten Capture is a project you can confidently take on with appropriate planning and perhaps a bit of professional guidance. With this in mind, the Genus team invites you to take advantage of our no-charge overview of refactoring SBL in Tungsten (formerly Kofax) Capture 11.1.
Our expert team will provide you with insights into various techniques, such as re-code/refactor .NET, C#, and more to replace re-built functions within Capture. The Genus team is standing by to guide you through this process and discover the added benefits of upgrading to Tungsten Automation TotalAgility.
As you know, Genus is committed to delivering exceptional customer service and helping you achieve your business goals. Get in touch with our team to learn more about how we can help with your refactoring.
👋 Reminder: Get more useful content, expert tech tips, and timely articles delivered to your inbox ~ Subscribe to the Genus Blog!