The wait is over and K2 4.7 is yours to experience now. Head over to the K2 customer portal and get your hands on it. It is worth the wait.
This release includes enhancements on end-user experience including K2 Mobile, Universal Windows App, SmartStarters, and deeper DocuSign integration. It also includes capabilities that empower technical teams with a new REST broker with Swagger compatibility, K2 Management, Application Lifecycle Management (ALM) and more.
K2 now supports SharePoint 2016 and adds key enhancements to performance, forms rules and registering web applications, which simplifies application registration and activation management for the K2 for SharePoint app.
jEyLaBs has been working with the early versions of K2 4.7 and The next PowerToolz for K2 update, Version 4.7, will be released shortly. We will support and enhance K2 4.7’s impressive array of new and enhanced capabilities with a deep focus on Test Automation.
Run PowerToolz on the server where SmartForms is installed. Go to Theme Installer node, select jEyLaBs Orange and click install. A quick IIS reset will be prompted and you are good to go.
Two additional themes, jEyLaBs Apple and jEyLaBs Mango are in the making and will be instantly available once they are released. You will be able to install them with a single click from within PowerToolz.
Please let us know what you think of jEyLaBs Orange. You can email us at firstname.lastname@example.org
The Buy vs Build argument has been around ever since we had reusable code. We face this every time we propose a solution to a customer problem. This question somes times surfaces as Cloud vs On-Prem. This also affects businesses that have invested in a legacy platform such as Lotus Notes or a homegrown system that is clearly outdated.
Do you buy a product and customise it to your needs or build a solution from the ground up to meet your requirements? Nobody writes a database or an operating system anymore. We license them and build solutions on top of them or buy products that uses these as prerequisites.
These days we are used to platforms and we have our preferred choice of toolkit.
Which way we go depends on whether we have a clear case presented. If we can meet 80% of our requirements by using a solution or product then customising the rest should be an obvious option. But what if that 20% of the requirements could cost you a whole lot more to customise or impossible to achieve? What if 10% is the most critical of requirements?
What happens if the company that produces the product or solution you are going to use as the base goes out of business or get bought out by your competitor?
What happens if you decide to build it yourself and the key people of your team go missing? What if your team couldn’t solve a critical Scalability, Performance or Security related issue with your code or integration or customisation?
What if you invest in a product and suddenly there are much cheaper and better options become available in the next 8 months?
What if you couldn’t be sure of your entire requirement set? What if your business requirements completely change in 6 months?
There are many aspects that affect which way you decide to move.
What is more important is that you consider all avenues and make an informed choice. Once you make it stick to your guns and see through it.
jEyLaBs specialised in Application platform migrations and modernisation of legacy systems. Reach out to us, if you need any help with your Buy or Build decisions.
At jEyLaBs, our daily routine mainly involves project delivery. We work on projects that apply technology such as K2 to solve serious business problems. This typically involves building apps to remove business process bottlenecks, reduce paper use, provide new ways to conduct business transactions and support executives to make precise business decisions.
Our projects have no choice but to succeed and increasingly the pressure is on us to help our customers succeed fast.
We have employed various techniques to help our K2 project delivery and perfected them over time. We dropped some outdated practices, we tuned many of the traditional software engineering practices to suit our needs and also created some drastically different ways of doing things.
I am very excited to share the following tips with you from our K2 project delivery play book. I am sure these will help your projects succeed.