|
Lotus Notes
|
SharePoint
|
|
Framesets
|
Master page
|
|
Pages – we can insert into framesets
|
Site Pages (Wiki or Web Part). We can insert the pages into the master page. But can merge it together. There is slightly difference b/w LN and SP
|
|
Navigation – Used for navigation in old version LN
Outline – Used for navigation in latest version LN
We can convert outline into the page and insert into the frameset
|
Quick Launch or Tree view
|
|
Forms
|
Forms are nothing but lists. Create a New Item in a list. Which means the columns in a list.
|
|
Fields on the form – Ln DB fields hold the values. Nowhere the values get saved.
|
Fields on the List forms – Column(field) values will be saved on the List
|
|
Configuration Forms – Which needs to be initially configured before users start working on the database because most of the important values will be fetched only from the configuration forms. These configuration forms will be accessible only the admin of that database.
|
-
|
|
Views
|
Views – Representation of list data
|
|
Shared code – we can keep Agents, outlines, subforms, fields, columns, script libraries
Images, files, style sheets, applets
Shared code can be private or shared(for reusable purpose)
|
|
Agents – we can create methods and run on particular views. These are scheduled.
The code can be written in many ways within agents.
Ex: using the formula, simple action, lotus script, imported java, java
|
Agents are nothing Timer Jobs – We can schedule these jobs. This may be OOB or custom Timer Jobs
Ex: Daily, weekly, monthly, minutes, and hours etc….
|
|
Subforms
|
Similar to Content Types
|
|
Fields (Shared Fields)
|
Similar to Site Columns
|
|
We can add subforms (reusable) anywhere within the forms. Clubbing is not possible in SharePoint.
|
We can use one Content-Type at a time to insert the data.
Solution:
1) Create a single list by clubbing form and subform fields of LN into SP
2) Create Content Type and Site columns and add the site columns to the Content Type.
We can follow the 2nd step only when we have a limited number of columns in a list to be created.
3) Or else we can create a form as list and subform as the second list and provide popups based on the requirement.
|
|
script libraries – We can create methods and use
It in Agents. The code can be reusable.
|
Reusable code.
|
|
Look up – If there is a lookup to another database, the data should be retrieved from that particular DB.
|
We can configure Managed Metadata service and create term sets and terms. Where we can store the data (text only).
|
|
Note
By default, SharePoint is 3 tier architecture.
Topology of the SharePoint Architecture: Single server, medium server, small server, and large server
In any architecture, once we configure Managed Metadata service, we can share the services (to different applications) between the farms.
|
|
Lookup to other LN DB to retrieve the subforms
|
Solution: Content Type Syndication Hub for centralization.
Create Content Type and publish it and paste the URL in the Content-Type Syndication Hub section in Managed metadata service thru central administration.
|
|
If subform is retrieved from the other database and clubbed it with the form which is in other LN DB
|
Due to the Content-Type Syndication Hub, we can get content type and use it anywhere in the entire farm.
If we want to club it together, we have to create a list or create a content type and add site columns
|
|
If there is a lookup to another database and willing to run the form just comment it { } and run and check it,
If it is a formula use – { }
Ex: { "\"serv := userver ;
@DbLookup(\"\" : \"NoCache\"; serv :BD1; \"VNO\";\"Logo\"; \"ORFormato\")\"" }
If it is a method use – %REM
Sub class name
% REM
‘ 1st line code
‘2nd line code
‘3rd line code
End Sub
|
|
ACL – Access control list - is for security purpose
Access – manager, editor, author, designer and reader etc…
Roles in LN
|
Active directory
Access is similar to Permissionlevels in SP
Roles are nothing but SharePointgroups
|