Team reports software right now? 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 on resource planning. Get reminded before a contract reaches a deadline. We will send you an email before any important deadline on your contracts. Your colleagues will get the email if they are conntected to the contract.
What is Contract Lifecycle Management? Contract Lifecycle Management (CLM) automates the process from contract initiation to contract signing and renewal/termination. You get a better visibility of your spending and revenue sources, as well as greater efficiency in your contract process. That results in lower costs for administration and mitigates the risk of paying suppliers that is terminated. Copyl has a free version of the Contract Management system (see below) that you can start using to keep track of your contracts and other documents.
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. Find extra info at copyl.com.
Copyl communicates with the user in all the steps of an transaction in your Saga. You configure the status in the API and Copyl transports it to the user. Each step in the Saga transaction has a compensating action that starts upon error in the transaction. When designing the API and the Saga structure there are some things to consider. The Saga will do each request anonymously. You can add headers to the request but cannot run as a user request with jwt. The Saga will have inparameters and then keep track of all data that are returned from each request in the transaction. This data can be used for other requests in the same transaction. You need to plan for all the data that is needed in the requests and their compensating actions when you design the api.