I
inwolkdevevaluation
Guest
The concept of portals is to expose the functions to external users or customers. Hence the need to label the fields in such a way the audience can relate to. For Example, I want to expose the form which can capture enquiry as a Lead record. When I define the portal page for Lead, it will have fields like Lead / Lead Category etc. It is not feasible to expose such field labels on public form. The labels for instance can be changed to service required instead of Lead Category. Most of the frameworks I have worked with expose "Web Field Label" property for each field defined in the object. This Web Field Label or call it Portal Field label can be set as Mandatory at the Object's field level and default populated with the Field Label and if required can be overridden by the user. To build more flexibility, portal page can offer to override the Portal Field Label at the portal page level. This is critical for us as we need to otherwise carry out more development work just because we can label the field appropriately. E.g As a workaround we may have to create a separate object with desired field names and have a trigger to convert the required data into lead record. This just adds unnecessary overheads. Please assist. Imran
Continue reading...
Continue reading...