Help Me With Integrate eSign in CMS

Help me with integration sign use cms

hi everyone we're going to get started now we're thrilled to have everyone cheer for our webinar co-hosted with our partners at CMS integrating existing systems with a CMS so during the webinar will be exploring how one client tackle the challenge of integrating a legacy system with their CMS to handle storing and sharing content privately while maintaining a public-facing platform with many user roles and permissions so we have to learn experts here we have friends pencil a solution architect at our tech solutions over here and we have James and Tesar our director of engineering at CMS so we're thrilled to have both of these subject matter experts with us today a little bit about Jason I so jason from jhe's PMS and our director of engineering at ms his primary focus is the product as it relates to our d and the building out of features and solving issues within the product Brent from architects began working in software over 20 years ago and is an early adopter of agile starting with extreme programming in 2000 as a solution architect at architect friend focuses on four areas sales support solution quality growth of architects top and external thought leadership so we're thrilled to have them both here with us today I'll hand it over to Brent to get us started that's it for thanks a lot early I really glad to have everyone here today with us thanks a lot for making the effort to join us you'll be able to join the conversation today only one I can where they can drink the conversation yep so we will be live tweeting some of this webinar and you know anything that we feel we'd like to share with our audience anything you like to share with us I feel free to join us so we have the dot PMS handle as well as our architect handle and you'll see that we'll be using the hashtag into great CMS super thanks a lot to dms and Jason as well today for joining ass so let's temper again get started talking about who we are first of all architect ray we're custom software design firm we focus on a couple of different areas we have practices for strategy design engineering and cognitive analytics this is really important when building software from the strategy perspective to understand what to build so the software is viable and does the design it appropriately to understand whether to make sure that it's usable by the with user focused design practice we we focused on a consistent agile process to deliver based on speed and quality we are early agile adopters and have had years and years of experience of this as well as many many clients we work with those startups mid-sized and enterprise clients so we do everything from brand new product development updating existing products as well as loads of complex system integration as well we really focus specifically on custom Java and JavaScript solutions and we are very cloud friendly i would say cloud first but we also support you know working with on-premise solutions as well so that's a little bit of an architect Jason mind telling us a bit about CMS sure Dodson as we've been our been around for for quite some time to dating dating back and into the 90s uh we had come come around during when everybody was looking for what management and that over over time as we design solutions we eventually put all of those pieces that we had done for clients into a product and in hence CMS was born Dodge Ness is a very community driven project and product um I think this is this is a very good thing for those that use dot CMS and for partners like architect who who use dot CMS because doxy mouse has really built by and for people who actually use the product but without sacrificing the enterprise nature of software which which businesses would demand dot CMS has built for integrations and as is shown on the slide here I think api's we where the rest api's ability to get data in and out of the system content in and out of the system being able to play very friendly with the other pieces of software in the sandbox is very important for us so we could kind and we'll talk about this a little bit later on we can do is as much or as little as you want dot CMS is also very focused on customization and being able to not just use as much or little as you want but even use it kind of how you want to be able to use it so while we have a lot of functionality oh you're able to customize your able to have extension points you're able to put your own custom logic things of this nature in into dot CMS and use it in a way that makes sense for your business we're also very much focused on flexibility on scalability this means you want to run one you can run one you want you need to run five six ten dot CMS's that's that's fine or many more the ability to scale whether it be in the cloud as brent was just talking about or even on prem of course a lot of people use a mixture of those two solutions which dot CMS will play friendly with and has a lot of different options for you as well and moving forward just the ability to grow to scale on demand and have more advanced deployment strategies these things are very important to us as a product both now and as we move forward you can continue on Brent great thanks Jason so I'm also a little bit about CMS integration in the enterprise these days of course Enterprise is no no one's running one a piece of software inevitably what happens is we've evolved a set of platforms that bring a load of capabilities to be to the business and anything new coming into that that ecosystem is going to have to play very well in a potentially very diverse sandbox so when it comes to CMS you got a lot of touch points to your business and any CMS solution is very likely to benefit from integration with those existing enterprise platforms so just a few example targets here would be figure single sign-on Authority so folks who are you know already go to log in they don't have to create a new one forget to CMS platform specifically the marketing automation campaign you got your CRM platform there could be reports being generated from your business intelligence platform you may want to be feeding into your your CMS for use on your website or you know again used with all those all those other those systems like the marketing automation platform and then you know you're going to still have some your your own custom middleware services that have been developed me but I've under like architect that you're going to want to driving content out of or or into the CMS as well and give them especially that you know even to enterprises that have got the same platform deployed you know the configuration and the use cases are going to be really varied and and as a result you're still going to probably need some sort of custom solution to to enable your content management system as well as I get it playing well with those other other systems in space so then take you to our specific client challenge that we're going to talk about today we were working with an Internet technology company they were they were sort of stranded on a legacy system and this had a number of issues so you've got to know a lot of aging websites where they're running probably about 10 websites and these are running across diverse CMS instances so this content is not consolidated into one now one instance as well as across different CMS technologies and those are even small medium and large as CMS CMS technologies so you've got folks that are working offline traditional traditional document doctoring style workflow which which is not being aggregated Danny into any kind of central system so you have no no can you know no consistent auditing of content or versioning of content or any specific publishing workflow either so folks essentially are working in an ad hoc manner they're sending documents around legal duck everything from legal to external marketing publication just sending it around my email and trying to track it all with you know those those many parallel threats that you result that result when you're working just through through that sort of system what this does in terms of web publishing is require this offline content aggregation when you're building contest for web it's really a different authoring situation than than a traditional document traditional document you can write the content inside you can add images you can send it to your friend by email and you can say that content is done you can say that document is complete when it comes to building for web you need to aggregate images need to aggregate files you need to embed links you know that relate to other pages in the ecosystem and you need to put text on to a web page that lives in some specific context and that's a web context and that's a web page and that's a template as well as the CSS and the styling that actually renders that onto the page so this is much more complicated and what happened then is when you're doing offline and authoring in this way you put all these different pieces together that is the text snippets the image is figure out where the files are and then you send that all through through bottleneck through a person so you basically put that into a ticketing system that a person is going to pull off pull out and then they're going to go effect that change in the public website so you know when you've got ten different instances and various technologies well an author in the enterprise cannot just don't start changing content necessarily so this is the way that this organization has has broad organization has brought some organization to the process is to say well we're going to have a dedicated web team so that at least we've got the same set of hands working in this system but without sort of direct to web authoring capabilities where everything can be aggregated in situ and different cross-functional team members and collaborate in place in the same place it's a much more inefficient process so in the end everything is going to go through someone else and Matt the pen that someone else has got to actually make the final decisions on how that gets published to the web meaning the original authors are essentially left out of the process or meaning that there's a very inefficient publishing process so it's got to be aggregated organized into that ticketing system pulled off the change made published to some system and then invite all people to come and provide feedback at that point maybe they say that's not quite right so the whole thing is going to start over again so now two ads at that point this is also an organization that had that has a very multi national presence in multinational community so we're talking about seven plus languages here this semi translation burden actually has a multiplying effect when it comes on when you apply it to these content and efficiencies so you've just done that wants to get the city include content out what I am going to do it again for every other language and then when it comes to making an edit of course you've got the exact same translation verb to come to recap so some of the challenges of company me I that we that we face we were able to uncover their unique business needs they had a document management platform in place for their enterprise assets so this became a constraint on the system the idea here was how can we create all of those enterprise assets as well as all that web content holistically given that they really do need different treatment as I mentioned there and also how can we support multiple enterprise and web content authoring use cases you had you know all kinds of all kinds of ways to create content in this in this current ecosystem how are we going to support those in a streamlined fashion in the future state and then also how we're going to integrate with the existing mature translation workflow that they work very hard to to optimize there's you know everything from from how much how much it costs to to get a translation done is affected by this this existing translation workflow so it didn't make sense to walk in and just start changing that up from under their feet so how do we help the client well first of all why architect we're the only platinum CMS partner in North America so we were we were clear to us to take on the integration system integration of this magnitude we have got loads of experience in web content management and and general CMS migration as well as having worked with dub CMS you know we really know the ins and outs out of the different different assets of the different tools that CMS provides from for plugins to content as a service we're very familiar with these things we also apply a design thinking in an agile engineering method of methodology so when it comes to getting in there and trying to sort out the challenges that are presented by this by this complex system of stakeholders in this case very large organization it really helped to have a partner like us to come in and consider their problem our problem so that our strategist can begin understanding and dissecting what it is that they that they need what it city care about and trying to figure out those end points and how to solve them for that customer we've also got experience with complex enterprise system integrations outside of CMS so you know where there are economies of scale or you know mind share that we've already got that we can apply from previous problems we've solved to this specific problem that or not that are not exactly always TMS related when it comes to a really complex integration Jason Jason's going to speak a little bit now to tawag of CMS was the vendor of record sure and and I think we would have been darve record here and it speaks a little bit to what i was saying here a little bit ago when I was introducing the product in it it really comes in as you see in the slide here firm ease of use it speaks to the fact that that dot CMS is is one built for integration and not just for integration but being able to be your content store your content of record being able functionality and features like that yeah you would expect out of a CMS like workflow but without and sometimes when people hear workflow they think oh no this is scary workflows big and I've been in large workflow systems well dot CMS brings the benefits of workflow it brings the benefits of a content search the benefits of content storage arm whether you know and as its mentioned here that dynamically uh we bring back without are always adding some of the the extras the the heaviness of it d we have a very Street where our approach is to be minimalistic not overly minimalistic but in a in a way that is easy to use in a way that is intuitive and again I think that all of this really is built on the foundation that CMS is really driven by the needs of those people who run it where when enterprise products but we're not in a price product who builds software in a box are our thinking is not well let us go let us build all these features and then tell people what they need as a company and as a product what's very important to us is the feedback of those who are using it the requirements of those who are using it and that makes as why documents was selected here by by the claw by the client and for the business needs in Dodge CMS was a good fit because we have come across many of these problems with with many different clients and many different sectors of business and many different partners and such and as we've come across those problems we seek to build them in a very streamlined intuitive kind of way into the system and no tool solves everything and but the dot CMS's is an excellent platform and for doing this kind of work and we were thankful that at least in this case we were able to work with with architect on the solution if thank you sir so we let our content strategist loose on the problem we worked with I work with the organization and we started uncovering a lot of different pain points a lot of different requirements these are some of them you know how do we actually define where the content should live and how should we get to the final architecture the final solution these are some of the input some of the some of the client cotton comments that we heard so what was our program well first of all we go into the discovery phase we want t set goals in a vision statement and want to really collaborate on what the expectations are going to be Trista sixth successful project so we'll set those goals will will get a lineman on them and then we'll come back and revisit them at the end of the project rank ourselves a little bit on them what identify everything the client knows already what are your existing biases what sort of metrics do you have you know how much content are we talking about how many websites and things like this and then also what's the technical ecosystem so what sort of parameters are we working within you know is our is our approaches or is our recommended technology solution going to going to work in your ecosystem this is your business so you're going to have to take this on at the end and we're going to phase two which is user centric design we want to understand the user the user journey mapping these are the needs that want the values in the behaviors of the actual users in the system in this case there are loads of users there are users that are coming to websites and their users that are maintaining content and authoring it behind the scenes there are also there also systems operators that have to deal with the complexity of any sort of integration that we that we recommend okay so so there are a lot of people to balance here as well as you know what are the high level stakeholders in the organization want to get out of this this is consolidated approach so we capture the current user flow of the offering flow site and then we streamline that into a desired future state so that we can figure out how the architecture is going to actually support that we come into requirements definition where we're identifying clear constraint from all of that all that preparatory work that we just discussed and we're solidifying these cases as older identifying specific pain points and any accelerators to the process so this is where we can come in as technical leaders and actually say we've got some good ideas here we work with these sorts of systems before and you know we would go we would take this fork in the road not the other again it's a client's business so you know they may take our recommendations they may not but certainly we're going to we're going to put our foot in in and argue for what makes sense for us and we want we all want to be working on a system that makes sense and a really real fight for that you know we act as a partner for our client so you know you can imagine us a little bit as a as a as a software engineering department within your company's who's trying to get the right thing done so that we all live in the indices nicest place possible then we come to our recommendations where we outline the final final findings and the strategy and then it's just the architecture that supports the business before working into the implementation phase where we can build it out will be discovered during that bring down those phases well as I mentioned we had a number of different actors it's very complex we've got internal content and external content and therefore internal and external users we've got people approving content as well as offering it other those have also got people publishing it we've got the rights to say send this under the web now or send this out to to the content sorry send this out to a marketing campaign we have a lot of different use cases we ended up with interesting cases like long-form offline coffee being offered say in Microsoft Word documents as well as online just you know a few paragraphs here and there that need to be integrated aggregated in with them with some wet has web content with some images and some file links will send cases for fire-and-forget publishing where someone wants to just add a snippet of content at a file at a report and that's just going to get consumed onto the web without anyone actually touching it in between then we've got subject matter expert and web publishing approval so we've got a couple different layers of approval there whether were the original content is the file or the document has to be approved and then the actual content aggregation on the website house will also be approved and then we have translation request which as I mentioned is it is it major major john for this fits organization we came to understand assistant responsibilities how the different systems are going to play well together so we have this is constraint to use a document management system for files media and and that sort of thing as well as well as to have the the web publishing arm where we r dot CMS comes so so you know we have this content system of record concept as well as all the work clothes approval that are required to get content push through those workflows and and also the accessibility so you know we're dealing along with how can we build it and build modules that are hooking in naturally with these systems a lot of API integration in the sort of thing finally we had different types of content so we've got internal web content we've got static assets we've got customizable use your web content so this leads us to structured content types this leads us to different treatment for a file that's just going to be a related file to a piece of content and we need to deal with all these different categories of content holistically so that we can systematize how their food from the various systems and how they are displayed on the front end without having to treat everything like a snowflake finally some of the streamlining of workflows to just optimize what folks are doing today and make the make the technology solution something that's actually a future direction and not just a mirror of what they're dealing with today so this is going to bring an optimization in streamlining so as I mentioned that that big client constrain was that assets are going to be sort in a dms we don't necessarily need our content stored at the MS but but this is the businesses choice so so we're going to just we're going to go with that we analyzed ways around that and in the business decided no we want to go this way and that's fine so I'm going to store their assets so they're out that's like documents and media and a document management system and this is going to perform a number of capabilities in the overall solution such as storage backup versioning does tribution and tagging as well as retrieval and translation of assets and of course translation was such a big big pain point for this organization that having a content in one system that and all translations initiated from one system was a huge benefit and this really really justified the decision to use to use the DMS this way they're storing private content that's never intended for web so they don't even want the chance for someone to reverse a permission flag or anything like this and allow this content to be exposed into the web ecosystem and then of course we need content creation tools for documents and media and the DMS does support these so you can have you can have your offline editors you can have your mobile editors and these are going to connect very well to your DMS and allow updates and content lock and all this sort of features so well that CMS offers these capabilities the client impose this constraint and so that's part of our solution another part of the interesting interesting solution that's going on here but next we need to organize the content for the web so the client needs to operate sites but the DMS is missing don TMS is really superior support for overlaying web concepts on to content so what do I mean by that well I called on CMS in this architecture the web publishing platform so files and media the DMS are agnostic they just live there in folders but duct EMS is allowing you to organize your content into pages on sites these are displayed by templates with styles that's very different than a word doc sitting in a folder so further to that what about web search when you can search your DMS and that's going to be a Content a system of Records for everything that's there but all you're going to do is find it be able to access and change it that doesn't enable external users to actually find that content on your website web search is a very different problem so you need the web context you need to see the the link that leads you to that piece of to that page with a piece of content to store and dust EMS is very powerful indexing and searching capabilities and and allows you to organize your content into this into this web content so dub steamers also has very powerful content aggregation and authoring and publishing tools so I contend that you can actually publish live to the web without a preview otherwise all you're doing is publishing to some some other server some some staging server or something like this or you can invite people to go look at it or you can go to getting yourself but then when you need to change something you're in a long feedback word to go back get it change to get it published again and then go look at it again very different from that is the image you know it media authors as well as text like long-form text and content authors collaborating to aggregate the content in place and then looking at it as they've done so and then talking about it and saying this image is not looking right here maybe we need to change CSS behind the scenes let's talk to the development team or simply I don't like the words that you're using their let's change that and then and it will just push button publish it up so the idea here was to integrate god CMS the web publishing platform with the DMS the next line so a Jason did you want to mention a little bit about how dot CMS is playing that role sure I I think you kind of kind of hit on it there Brent as far as where at least in this in this particular use case offering kind of that that separation of content from the presentation of it which you know as you mentioned I mean we got seimetz can do but do you want its own but also in this case provides excellent integration to be able to come on and provide that separation and even if needed the the workflow that would allow the push through the stages of as content moves through its stages as far as the web publishing is is concerned um you know it's going to offer here the client to even the ability to disseminate content differently say a to be able to take its binary assets say something and that would be like taking something an image and resizing it could be as simple as that or taking content to PDF it if they need and anything of that nature whether it be image controls or editing controls built right in or even just out of the box you know server process side processing that yeah I have my image I I want to crop it I want to do this with it these are just simple examples but but probably very common examples as well as providing the rest interfaces into the content store and even for the things that are in the web publishing side of it to be able to have any search capability whether it be coming from some input on the presentation layer or even just being able to login in search in uh you know have a very fast and powerful search of what would even be available within the web publishing side of the house here I I think it's a lot of what you spoke to brand but kinda just a quick summary I think of where dot CMS of speaking yes super and that's a good that's a good transition to our next slide action which is about the the solution so um rest a few guys figure prominently here let's talk about the we'll get to that on the next slide I guess but let's talk about the overall integration solution features so integrations are software solutions these are full-featured custom custom development efforts that but to me are not so different from from from a new product development or from product upgrade so as a resulting you too many of the same things in equality so you know architect suppose automated test suites for all the software that we build you know at the unit at the integration at the end to end or functional level as well as at the performance at the performance level furthermore security is very important so you know the appropriate you I accessed by user and system role is critical here we're going to model all these things using CMS don TMS is workflow features and n roll and system access features and we're going to integrate those those permissions across the DMS and web publishing platform to make sure that people can only see the content that they're really entitled to and furthermore this goes this goes double for the API you know would be very easy to roll out a solution and not think about how the API is actually going to go to be secured but you know sir the system roles are going to read access and and we might want to actually even log people in as as themselves for certain for certain accesses through the system which is which is any truck to so furthermore maintainability the solutions been expected to live a long time so we're going to employee appropriate law greg r again from any of the custom software that we built which is going to roll up all those all those all those system logs from all the custom software that's built it and in fact even the duck CMS logs that come out to deploy those out to to a to a log aggregation stack and allow appropriate monitoring so that people can slice and dice using like it like an elk stack with elastic search again as TMS also features to be able to filter all the log information that's being aggregated and and just look at the level of detail that they want create custom dashboards and see the help of these running servers as well as any any pain points or warning or trouble trouble spots that are arising and furthermore automated deployment is something that we live and breathe by so you know these these devops concerns are read in our blood and you know anything that we built we needed basically we need an automated deployment to our to our development servers we need a regular automated deployment to our staging systems and then we need to push button deployment to our production systems as well so what kind ms integration features do we come up with well it's going to play the role of enterprise system of record for private and public assets we're restoring content types here documents and media the idea here is to get the public content separated from the private content and to have it organized into syndication channels so now we're going to create something like a web channel or web channel one web channel 2 and that's the republished executing middleware which can consume by REST API everything that's been flagged for publisher syndication by the business furthermore we've got channels exporting the assets out to CDN so we've got public CDN assets and then we're going to export the content and the metadata over to GMs so when we start talking about including these images of those images they're not just local to CMS but they're also pulling off of this pulling out from the CDN what's sitting there for you know for performance reasons and then we've got additional channels as well so you know there's a requirement here that we can publish certain reports up to Salesforce that we can publish certain content out to internal internal collaboration software so they've got they've got custom applications and they've got and they've got deployed platforms as well and we're going to want to integrate these these channels with all of these all of these systems furthermore there's the idea that we're going to want to generate URLs and know what they are beforehand so that we're not ending up with some system generated business that's hard to deal with and this is this is crucial for publishing out to the CDN as well for that matter so we're going to have human readable URLs and there's going to actually be sort of an association with the translated version where all the translated content in the DMS is going to be associated with the original and this thing that folks can find the original they can find everything associated with it and then as the originals version into minor or major versions we can also have automated translation automatically triggering these translation requests out u on any edits so you know the first time content comes into that system and someone's working on it they can say this needs to be translated and they can just push but that's custom code that's been deployed to the DMS but then when something changes in the future you've got our automated request that's treating and triggering out as well because we know that this content needs to be needs to be translated when it comes to dot CMS and its role in the architecture it's playing the role of web publishing platform as we mentioned and then we've got all the public enterprise content being syndicated out into the dust EMS toolset so now you can do web authoring and content aggregation working in this sort of web web studio mode with CMS and all the content is coming from everything that's getting published into your DMS at the enterprise level in addition we've got the public web search be driven by CMS because it's going to provide search results in the appropriate web context we have this note in of working on the content based on the contacts so the idea here was that if you've got a web author maybe someones committing some long form some long form web copy to the DMF and that's getting synced over to the CMS for use of that in that content aggregation or offering use case but what if they want to k2 that now now that they see that living there on the web page in the live preview they might want to just affect a small change or a big tank so this message acetates two-way synchronization but what we can do is given the you know the openness of these api's with with CM is content management interoperability standards well we can do a check out in a check-in behavior using does CMS's custom workflow tests so now we can literally put a button there in the dot CMS you lie but a user can say check this out make a change and then check that back in for the more we've got an existing single sign-on capability in the enterprise so we want to use that for the percent rly manage user credentials and access to all systems you know we've just added two systems that folks have to log into whereas previously this is the domain of some technical staff but now this is this is just your regular user so they you know they're less likely to want to manage additional credentials so that's a real quality of life by integration there as well as making sure that credential managing and consistent way in a consolidated way across the enterprise right furthermore once we're treating content holistically now we can build we can build systems around our application so we've got known meta data around this around this content so for example we're building now a website widget and that website which is going to allow that's built into CMS that's on a CMS content so it's a piece of duct Ionesco what is going to do since we've got this non metadata in that system is we can say expose all previous content versions and we can say expose all alternate languages now this happens to be an organization that has a certain mandated measure of transparency so what they do is they keep all previous versions of all content they've ever published to the web which is which is you know serious mouthful they keep it all available so that everyone can always see what's happened what changes have been made so in their use case this is very complex content management use case whereas normally folks we just want the latest version to display we have both the use case of display the latest version as well as allow navigation to all previous versions as well as allow all navigation to alternate languages and all their previous versions so certainly there are there are dots EMS features that allow us to do the internationalisation pieces of the pages and you're just going to see that you know the the translated content when you switch to the Arabic version when you switch to the French burger that's fine you're going to see that content just because of the way doc CMS worse it's organized but in addition users can can go browsing for for old versions of those things or or specifically go navigating that way if they feel like it finally the the DMS has an asset version awareness so as I said you can publish either the specific versions of something from a Content perspective or you can publish a canonical URL that refers to but that's more of a link that refers to the latest version of that content so in the case where someone wants the latest to be displayed we can achieve a use case but in the case where someone doesn't want to onion you know unintentionally how content change which again is is a mandated requirement for these folks then you can you can achieve that use case as well okay now I'm going to turn over to Jason stuff a little bit about i dub CMS and some of the some of the industries where does EMS systems have been deployed in big enterprise sure sure and as you can see here these are just a four of the sector's where we've been able to accomplish similar similar types of integrations in solving these types of business cases that brent has been sharing with us and we're architect has been successful and in da GC mass quite frankly has has been successful and this I think that the sector's show to Brent's point and what he's speaking about if you start thinking about these sectors you realize the types of integration they need if you're familiar at all medical medicals got HIPAA regulations and education which is mentioned here as their purple right regulations as well and as you they have systems that maintain data and they need to be able to use those data in certain systems are needed to be used within these sectors simply because of federal regulations or things that they have or an education whether it's a student formation system or online course management whether at the blackboard or even some some other type of solution or homegrown solution within any of these sectors and dot CMS has been able to come in solve the needs in much the same way that that brent has been sharing his expertise and architects expertise are here in we've been very successful whether it the emergency room wait times whether whether it be searching of physicians whether it be indexes for financials in in banking and insurance type work we were in all of those in a number of government solutions not not here in the US and in and abroad as well and and really accomplished in much the same way using a lot of the same type of expertise and solutions that Deborah has has been sharing it with us and from architects expertise so we could move on maybe the next slide bruh so in chat a little bit about the best practices when it comes to integration as I mentioned before we really really consider ourselves a partner with clients and our clients echo this so you know once you've been engaged with them they keep us they keep us engaged and they keep on working with us for for our technical expertise and our ability to just get in there work through the existing bias you know acknowledge it and surface additional additional requirements and pain points that they might not have so we want to get want to get everything that you know and we want everyone to just start thinking in an innovative way as well and work outside of their existing assumptions so you know around the spaces to you know you as I said before you might come to us with with expectations of what technology to use and that's fine certainly we'll talk all about that but we do consider ourselves opinionated technology leaders and we work we work on our own on our own reference architecture on our own technology stacks and we do have specific specific stats in the job and the JavaScript space that we prefer over others and that we've worked on and matured ourselves so you know we're always going to translate the solutions into technology that's appropriate for the client but but we're always going to bring our technology technology leadership to bear as well and try and try and help make the best the best product decisions overall another big aspect of how we how we do software delivery is to deliver business value very early in the process as well as often so through through a appropriate you know understanding of the business value you know we're going to start with a problem definition we're going to break that down into some some some epics at a very low level of granularity that that help everyone who's working on this project understand how to communicate about what the requirements really are and this kind of a seed from the problem into the initial way to break that problem down into business value and you know into in two counts of business value that then result in backlog development and story writing is really a great way to then have a release a release plan on a you in a product roadmap that the user understands the clients or that the client understands that any stakeholders like users might understand as well as very important for translating into technology so the technology team has to be able to consume this information and then turn it into release packages that achieve specific results things like here's our our initial launch here is a feature set release here is the stability release and then furthermore we really we're always going to be as we choose you know the first slice of business value that we can release for for user testing purposes just to gather feedback along you know up to like every sprint release that built incremental e on that is weird as well an agile development organization up to each release and the goals for that release or we're always incorporating State Quarter stakeholder feedback so every sprint includes includes our client to the user acceptance testing and decide this is appropriate this is not appropriate or this is what we have to do next and I Jason's going to mention a little bit of those guys at CMS sure I mean I think here just continuing on with talking about best practices and we would certainly rely and we certainly have expertise here but also rely on partners like architect and their expertise here but just just a few few comments to as we close here regarding best practices and building on what we've already talked about this has been mentioned the number of different here in the last little bit of our webinar ever use cases unique businesses are unique it's it's one of the things that makes Taksim that's great and architect also a very very needed an excellent partner because that's understood and businesses are unique as might there isn't it one size really does not typically fit all and well maybe you could make it work there needs to be some ability to be flexible both by those who are doing the implementation and also by the product and and that's really what we spoke through here today so just understanding hey I have a unique case and then what is my case and I need understand the problems I need to understand the business needs I need to be before I start building before I start integrating its sure let me let me grab all the software and install it all but that doesn't always get you where you want to be and sometimes it's more confusing when I don't understand the problem so one I understand you that the unique or what is unique about my case I understand the problems I understand and grab the scope of what out what are we trying to solve as we're trying to integrate then we need to consider what data is going to be stored where so in this particular use case that we've spoken through today there was a ready document management system in place and there was already a solution that was very specific to the business that had to stay regarding multi late regarding how files are translated in and how they're managed within their system are they and maybe in this case I think they were using word or office or some type of solute product like that and it was integrated into their document management system in addition to that they had this whole process on how files got or how content got translated well we need to understand how is where's it going to live is that data 0 is going to be pulled from the document management system is it going live in dr. yes is going to live in both places are we going to be sinking a lot what's the expectation how how near time does that data need to be of course as you start incorporating more years and more publishing and systems to push through when I make a change what needs to happen before that thing becomes life and does that meet the business requirement so as you're talking about integrating this is really important howlive does that data need to be how we you know how many your timer or real-time a lot and that's what i mean by how live so you need to think about where do i want things to live and why do they want them to live there and as a final comment we at least a dot CMS would suggest to you that that fewer gears is better this is the the old less is more saying and a fewer gears that you have you the battery you don't you don't want to have unnecessary pieces or unnecessary cogs because again you start talking about work playa dension did earlier and I at least in my experience in interacting with clients workflow systems that can get very complex and can often be daunting when all you need is is a B and C and yes it's great that they provide a through z but very very very few people use D through cision most people are using a B and C and if I don't need the rest often they just make my life harder so I think as we look at integrating with what exists and we look at implementing software and our experience it's always worth considering why am I doing this do i need this and you know often the answer is yes but it is a good question as you're integrating in looking at software and even looking at new softwares you're looking at products white dot CMS you know do i need this what's it going to solve for me and if I do bring this in what you know what should stay which should not stay where are things living what do I really need to suffer great thanks Jason yeah softwares definitely can be a challenge to maintain and less is more i go to agree so that contains the main portion of our webinar today and well pass it over to orally to moderate the Q&A alright guys thank you so much Jason and Brent that was fantastic so much to hear about so much to explore we do have time for a couple questions we've had a few things come in during add sessions so I'll read them out loud in and ask the two of you to address them a few it so first questions here is when you say we can use as much or as little of dot CMS as we want does that mean if I already have a system in place like a dms I should keep them so Jason I feel it a question for you sure sure um I the answer I think is yes assuming you know the business requires it if you know if they don't I mean consolidation into into one platform is is certainly also an option um but again i really think that it speaks to the lessons more thing it speaks to the the concept of what is the business requirement it goes back to understanding the scope understanding the business problem and then when i do that that's when i asked this question obviously the use of little or use as much as you want of something e before asking that question you're asking question of well how much do i want to use i need to understand the scope i need to understand the business problems i need to understand the business requirement and by understanding these i'm able to understand okay how much do i want to use what makes sense for me to use and and so i think its business dependent but but for sure the answer is yes as the business require yeah I've seen this too I mean I considered a CMS a real I thought this was our night maybe Jason doesn't like me to say it that way but it certainly can do so much it's I think it's rare that any client would use every single feature of the platform and so as a result you've got to really analyze your business needs and say what are we trying to get done here and is this specific is this the right place to achieve it you know cut some software might be required in a place where it looks like something would be easy but you know just jumping in with TV first might leave you with a maintenance headache later on whereas maybe a little bit more you know upfront development costs could actually satisfy your use case and address like you know the performance concerns and scalability concerns to use the users use case scenarios in in a much better way software is not done you know when it's done so you know you've got it you've got to maintain it for the life that is going to be used and that's got to be a big concern later when you're choosing which way to go on something great thanks so much guys so we have time for one more before we wrap up here uh so someone asks there are some items in my DMS that cannot be shared with the public how does that PMS handle that if the two systems are integrated that's a good question if you want me to speak did you want me to speak their run yeah Jason okay so so so you're asking there are some items dms that cannot be shared at the public so i guess we're trying to figure out in this case for maybe security right like how does house dot CMS going to be able to deal security it's kind of a broad question I'll try to give kind of a broad abroad answer and you you know maybe give a specific or two but obviously not Smith has securities at the heart of what we do and is extremely important to us including the security of content as brent was mentioning earlier there's a lot of business cases where i need to ensure that content that should not be out on the public does not make it out on the content on the bubble as I was saying in some of the sector's we work with education financial medical dd's are these are sectors that we work with where it's not it's important for the business and the business will stay a lot of it on top of that is government in federal regulations that require that data not be out there right there very very very bad things happen for medical industry when when data that should not be released is released or even education and certainly no be true finance as well so I mean we have we have full ACL within the system that means that your access control lists that means that all of our our content can be protected it can be exposed to just only if you're a particular role or one of many roles or a particular user or never make this public or always make this public or only show this to anybody who's logging in any any of these kinds of things are possible they're certainly data that would never be exposed say on a presentation layer or in the front and all of that would be controlled within the system and obviously can be customized and as far as whether everything was living within our product or in da GC ms or whether we were integrating another one there's really lots of different options and lots of different ways that we would provide to deal with the security concerns here and really the protection of data which nowadays I mean many businesses they are their data I'm going without their day today they would cease to exist so and that's probably true of most businesses so these things are vital importance I know to us at CMS and I'm certain the architect as well for sure there's so much guys it's been a pleasure having you on with us and thank you to all our attendees I hope that the session was enjoyable for you as much as it was for us and we'll be in touch with you tomorrow as well with the recordings so feel free to share that with any colleagues or friends who might find it useful and until next time thanks so much everyone nice local but thank you