Dialogs are new in Dynamics CRM 2011, and offer significant new process automation capabilities for organizations using Dynamics CRM.Dynamics CRM developers are familiar with writing JScript to customize the user experience, and with extending CRM’s functionality via custom HTML pages and graphic files stored on the server. But in CRM 4.0, it was difficult to re-use JScript, and CRM Online couldn’t take advantage of custom HTML pages and other external files. Web Resources, new in CRM 2011, can be thought of as virtual files that would normally be placed on a web server but now can be stored in the Dynamics CRM database.
The “Is Default” field was added to this CRM 2011 team form to easily distinguish between the default team and custom team. Users (team members) can be added and removed from custom teams. The CRM system maintains the users in the default teams.
CRM deployments can now have different forms. For example, the audit users can have a different opportunity form layout than the finance users. Access to forms is controlled by the user (or team) security role. A form can be designated as a “fallback”, or default, if a user doesn’t have an explicit access to the form. The user will receive an “Access Denied” error when attempting to open a form that their security role doesn’t allow.
CRM 2011 allows multiple forms compared to the single form for CRM 4.0. Each CRM 2011 form is maintained separately, meaning if a new field created, the field must be added separately to each form.