· Architecture changes that includes Role Tailored client. Classic client still remains with two tier architecture, where as the new Role Tailored Client support three-tire model with Role Tailored Client, Microsoft Dynamics NAV Server which executes business logic and SQL Server.
· The Role Tailored client provides a single document interface (SDI) environment,
· Microsoft Dynamics NAV Server: The new Microsoft Dynamics NAV Server is a .NET-based Windows Service application that works exclusively on SQL Server. It uses the Windows Communication Framework as the communication protocol for Role Tailored clients and Internet Information Services for Web services that access it.
· Microsoft Dynamics NAV Server provides an additional layer of security between the clients and the database. It leverages the authentication features of the Windows Communications Framework to provide another layer of user authentication and uses impersonation to ensure that business logic is executed in a process that has been instantiated by the user who submitted the request.
· Microsoft Dynamics NAV Web services can be used by customers and partners who want to use business logic or use a standard interface to access data from outside Microsoft Dynamics NAV.
· To allow you to write code that targets either the Classic client or the RoleTailored client, a new system property called ISSERVICETIER has been created. If code is being executed on the service, then it returns TRUE. Otherwise, it returns FALSE. You can then use ISSERVICETIER to write code that is explicit about whether it is run on the service.
· When you design a report for the Classic client, you design the layout in Section Designer. When you design a report for the Role Tailored client, you design the layout in an RDL editor, such as Visual Studio Report Editor.
· NAV 2009 has an option to import/export the objects in .XML format also.
· Pages contain fewer triggers than forms for two reasons: The RoleTailored Client has enhanced behavior that is implemented directly into the controls that run on it. Some code previously necessary is now obsolete. Pages are designed to optimize performance, which reduces requirements for existing form triggers.
· The Role Tailored client provides a single document interface (SDI) environment,
· Microsoft Dynamics NAV Server: The new Microsoft Dynamics NAV Server is a .NET-based Windows Service application that works exclusively on SQL Server. It uses the Windows Communication Framework as the communication protocol for Role Tailored clients and Internet Information Services for Web services that access it.
· Microsoft Dynamics NAV Server provides an additional layer of security between the clients and the database. It leverages the authentication features of the Windows Communications Framework to provide another layer of user authentication and uses impersonation to ensure that business logic is executed in a process that has been instantiated by the user who submitted the request.
· Microsoft Dynamics NAV Web services can be used by customers and partners who want to use business logic or use a standard interface to access data from outside Microsoft Dynamics NAV.
· To allow you to write code that targets either the Classic client or the RoleTailored client, a new system property called ISSERVICETIER has been created. If code is being executed on the service, then it returns TRUE. Otherwise, it returns FALSE. You can then use ISSERVICETIER to write code that is explicit about whether it is run on the service.
· When you design a report for the Classic client, you design the layout in Section Designer. When you design a report for the Role Tailored client, you design the layout in an RDL editor, such as Visual Studio Report Editor.
· NAV 2009 has an option to import/export the objects in .XML format also.
· Pages contain fewer triggers than forms for two reasons: The RoleTailored Client has enhanced behavior that is implemented directly into the controls that run on it. Some code previously necessary is now obsolete. Pages are designed to optimize performance, which reduces requirements for existing form triggers.
. Field Groups: Field Groups is a new concept introduced in a table description. When a field displayed in a page in the RoleTailored Client has a relation with another table, the DropDown button displays several default fields from that table. These default fields are set from the Field Groups window, accessed from the table designer. To view the Fields Groups of a particular table:
In the Object Designer's Table list:
1. Select any table and then click Design.
2. Click View > Field Groups. The Field Groups window of that table
opens.
In the Object Designer's Table list:
1. Select any table and then click Design.
2. Click View > Field Groups. The Field Groups window of that table
opens.
. Using Administration-->RoleTailored Client-->Profile, we can change the default role center for the user.
No comments:
Post a Comment