Team collaboration software today
Project planning app 2021? Find out the security requirements before building. Look at authentication, authorization, network topology, impersonization etc. What level of logging is needed? On success? On failure? How should these recepients be administred? For how long should the log be saved? common mistakes when developing integrations: One developer is assigned to develop the integration. Leaving non-updated code, dependency to the developer and to the tech used. Declaring a system to be not open for integration. There are a very few systems today that is totally closed and cannot be integrated. Big datasets are moved back and forth – only send the data that has changed.
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 details on https://www.copyl.com/en/software/meeting-organizer. 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.
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. Discover even more info on https://www.copyl.com/.
Don’t copy data between different microservices: Never change the data from another microservice directly. Instead use REST calls to the API of the other microservice. If other microservices are having an interest in the change of state – publish events to let all subscribers getting information about the change. You can either use a PubSub solution from your cloud vendor or use Copyl Integration Platform to report events and subscribe to them in other services.
