Information models software by Copyl? Autogenerate your App’s Actions! It is really super-easy to generate all available Actions in your API/App by pointing out the OpenAPI/Swagger file. Copyl Integration Platform parses this file and adds all available Actions together with information about fields needed. Even the documentation is available in CIP afterwards. You need to manually start the parser from the administration interface of your app. You can delete any unwanted Actions afterwards and you can also hide them when generating the Swagger file.
Copyl started out from our own needs. We had an agency with 30 consultants and we were planning them all in an Excel sheet. We love Excel but we quickly got different planning in the projects and in the resource planning. We needed something more connected. And something that we could follow up in the time sheets and billing process. After a few years with this planning system we got a call from a big organization in Sweden that needed a ERP system. We scanned the market for them, not able to find a perfect match. We had a meeting and we showed them we showed how we managed our own resource planning. Instantly the customer said that they wanted that system. Copyl 1.0 was born. This was 2011. See even more information at https://www.copyl.com/en/software/contract-management. Copyl saves you a lot of time, money and energy. You will feel more ease and earn more money when you don’t have to keep track of all commitments and deadlines.
Access your Contracts from anywhere: There is no need to install any app and you can access all contracts and features via your mobile phone or tablet. Connect documents to your Contracts. Connect documents your Google Drive or upload directly to Copyl. Both signed documents and appendix etc can be connected. Electronic Signatures shortens process: Have your counterparts sign the contract and documents via an Contract Signature Request sent directly from Copyl user interface. The Contract is locked upon the first signature and everyone can access the contract afterwards.
When are microservices a bad design choice? If you are building a small application, or just building a prototype, it’s much easier to build a monolithic application. If the application doesn’t need to scale to multiple server instances it’s ok with a monolith. A middleway is to build a loosly coupled monolith that communicates internally via SOAP. You can also use some kind of user authentication that will send the user data in each call to the api. This is usually done by JWT (Javascript Web Token). We also recommend you to use Azure Active Directory (AAD) B2C tenant for your external users. We also recommend you to use an API Managment tool that will hide your api:s addresses, minimize requests, help you with versioning and also documentation. Read extra information on https://www.copyl.com/.
It’s a common issue that developers that are new to the design concept of microservices create too many service. A common design for a e-commerce solution is to have one microservice for Billing and another for Payment Collection. The Payment Collection microservice usually depends on Billing and Billing depends on knowing when a payment has been done. That’s a good reason to have both functionalities in one microservice.