This overview explains what a Web Part Request is. It describes the relationship between a Web Part Request template and a Web Part Request in Navision. It also describes the relationship between a Web Part Request in Navision, the Web Part Request properties and the Web Part in SharePoint.
You define the Employee Portal Web Parts you want to make available to your users in SharePoint by creating Web Part Request in Navision. A Web Part Request defines the format of the Web Part, the data that it will present, the basic properties of the data and the control elements that will be used for interaction and to navigate between Web Parts. In other words, it defines the data the Web Part will request from Navision and how it will be presented in the Web Part.
Each Web Part Request is based on a Web Part Request template. This means that you can create different Web Part Requests for different user groups but based on the same Web template. These Web Part Requests will make up your Employee Portal.
You can define Web Part Requests for different purposes. You can choose from the following three types:
List (to show a list of items)
Card (to show a record in a card)
Header + Line (to show a header with attached lines)
In the Web Part Request table, you can find a fourth type of Web Part requests called System. The System Web Part Request is defined by the program to be used for certain actions. You can read more about this type of Web Part Request in Creating an Action.
Web Part Request Templates
A template in Employee Portal is similar to a template in a word processing application. It is a document that contains formatting and, sometimes, generic text or other content. However, actions for interaction and navigation remain to be filled in on the individual Web Part Request. You can use one Web Part Request template as a model for creating many Web Part Requests.
When you design a template, you decide what properties (attributes or characteristics) you would like the parts based on that template to have. You decide the layout of each Web Part and what types of information will be included. You can then create many Web Parts that are based on the same template but contain different information.
For example, if you create a Web Part of the type List, you can use the same template as basic for many list Web Part Requests. You can then add characteristics to the Web Part Request to change the list Web Part request to suit your needs. This can be done by adding or removing fields and tabs and by defining actions and lookups.
Web Part Requests
Once you have set up Web Part Request templates for your portal page, you are ready to create the individual Web Part Request that will make up your Web Part. A Web Part Request must be assigned to a user group to be made available to the users assigned to the group.
When you select the template that you want to build your new Web Part request on, the properties from the Web Part Request template will be copied to the new Web Part Request. Some of the properties will have a default value from the Web Part Request template, but you can change the value. Define control elements in the Web Part Request such as actions buttons and links to allow interaction and navigation in the Web Parts. Once you have filled in values for the properties and the controls, the Web Part Request is complete and will be available on your portal page.
Multilanguage in Web Part Requests
The Web Part Requests are multilanguage enabled as the rest of Navision. The multilanguage features make it possible for you to offer the texts displayed by the Employee Portal in captions in several languages, on Web Part titles, tabs, actions and so on.