Video instructions and help with filling out and completing Why Form 2220 Liability

Instructions and Help about Why Form 2220 Liability

A very good afternoon everybody welcome to this session on self-service alm through lifecycle services just before we get started here quick show of hands how many of you are on Dynamics 365 today that's a good number ok and yeah so we will go ahead and recover this session so obviously all of you who are on Dynamics 365 are very familiar with lifecycle services we have continuously been evolving the service itself the cloud service ATS lifecycle services but most recently we have made a really strong push towards making everything more self-service so many of you are used to the process of logging a service request waiting for some time there's a lead time and then you get back your service request and then your action gets performed but a lot of that you will see that we are show today is more self-service in nature so that's definitely one of the big focus of what we have and what we will focus on in this particular session we will focus on some of the recent changes but also some of the more upcoming changes in the next few months so that you get a good idea on what to expect in general my name is Mira Maha Bala I'm the group program manager for lifecycle services the cloud platform the on-premises platform and I have with me Manali hi everyone I'm Manali Dougray I'm a program manager on the platform team some of the areas that I work on is lifecycle services update management as well as telemetry monitoring and diagnostics so you will see a lot of those areas showcased here today as well great so let's get started with especially for people who have attended lifecycle services sessions before you probably have familiar with this slide I actually dabbled with changing this out a little bit but really does convey that we are trying to support the entire application lifecycle and it does it well so what has changed is probably what is below that bar if you're familiar from the past so let's start right there with the the first part which is the define face a big part of your planning as you planned for your application itself we have a set of tools that's available as part of lifecycle service services we have the methodology that's been shipped a while back and it's been essentially orchestrated by our solution architecture team within Microsoft but of course it's available for you to start as a starting point for you to extend as you see the need for your specific vertical for your specific business same thing with Business Process Model the BPM we do ship standard out-of-the-box BPM and we you all go ahead and extend it as we certainly create specific specific bpms that cover their business processes and that is something that we continue to support task guides really nice cool feature which allows you to add what the business does play it back played back on ax itself played back on FN o itself and then see how it runs through the various processes primary purposes of BPM is of course fit gap analysis that you can do and then you can add work items as you see fit based on the gaps track it and use it for project management something that we also support is configuration through the BPM we allow you to essentially put put together data packages that you can put to specific environments you can deploy them in specific environments based on the processes and what data did they need or what C data they need to in order to orchestrate that particular process itself as you will see that whole section and define is black we are not going into it in a whole lot of D we're not going into any detail in that entire fray for to that entire phase in this particular session primarily because there we have much more ground to cover but that all of that still does exist and we are continuing to improve all them and it is something that you you should leverage if you haven't seen it already or haven't used it already the next phase that I have up there is the face and build or the develop face or the implement phase and this is where you would actually go ahead and build build your project together so some of the things that are useful in this face first off we with a standard subscription of fnot you get three environments right you get the dev test or the build environment you get the UAT or the sandbox environment and then you get the production environment so all three environments are available as part of your standard subscription we have made some infrastructure improvements to this environments that I will talk through in the next few slides but the environments continue to stay as they were and that you know of no off from the past We certainly have a set of build tools that we ship and it's also available integrated with VSDs the entire developer environment this is an area that we are making a lot of investments and you will hear a lot more around the entire dev ALM process in the coming months not in this session but definitely more a lot more detail in the coming months that we will share and then there is the notion of upgrade this upgrade from ax 2012 we support a migration from 2009 and the upgrade that we're focusing on in this particular session is actually the upgrade that we do between major versions so 7.2 to 7.3 7.2 to 8 or 81 and so on so that is something that we will focus on a little bit more in this particular session and then there's test automation we've had test tools before available that you can run on

100%
Loading, please wait...