IBM Domino Designer SECRETS

www.dominodesignersecrets.
com
IBM Domino Designer

SECRETS!!!
Learn to Create your Own Application

FAST and EASY
Written in Tag-Lish
Presented in Layman’s Terms
Perfect for Beginners and Non-Programmers
TABLE OF CONTENTS
Table of Contents …………………………………………………………………………….. pg 2
Introduction …………………………………………………………………………….. pg 3
Knowledge Prerequisites …………………………………………………………………………….. pg 4
The SDLC …………………………………………………………………………….. pg 5
The Different Environments …………………………………………………………………………….. pg 10
Guided Activity …………………………………………………………………………….. pg 13
A Little Reminder …………………………………………………………………………….. pg 20
Inside the Lotus Guru's Mind …………………………………………………………………………….. pg 21
Sample Flowchart …………………………………………………………………………….. pg 23
Sample Project Plan …………………………………………………………………………….. pg 30
Sample Algorithm …………………………………………………………………………….. pg 31
Creating your Project …………………………………………………………………………….. pg 32
Creating the Form …………………………………………………………………………….. pg 34
Creating the Fields …………………………………………………………………………….. pg 38
Creating the Action Buttons …………………………………………………………………………….. pg 49
Creating the View …………………………………………………………………………….. pg 54
Creating the Outline Menu …………………………………………………………………………….. pg 60
Creating the Menu Page …………………………………………………………………………….. pg 67
Creating the Frameset …………………………………………………………………………….. pg 74
Updating the Launch Settings …………………………………………………………………………….. pg 80
2 | IBM Notes Domino Designer Secrets

Introduction
Welcome to
IBM Domino Designer SECRETS
Learn to Create your Own Application FAST and EASY
This book aims to allow its readers to :

 Learn the value of IBM Domino Designer
 Understand how IBM Domino Designer works
 Learn how to create a IBM Domino Application in as fast as one day
Who should read this book?

 Beginners, non-programmers or enthusiasts who are interested in learning how to create an
application using IBM Domino Designer.
Question and Answer:
Q: Do I have to be a programmer to develop an application?

A: No.
Q: Do I need to purchase a license in order to do this?

A: No. IBM has made the Lotus Designer 8.5 free in this link >> https://ibm.co/2yezTPM
(Disclaimer: Availability of the link depends on IBM – they have the right to remove it anytime)
Q: Will I be able to create a project even if I have no knowledge in programming?

A: Yes. Just follow the steps discussed in this book.

Knowledge Pre-Requisites
What is IBM Domino Designer?
IBM Domino Designer is an integrated application development environment that lets
developers and Web site designers create, manage, and deploy secure, interactive applications.
What type of applications can be created using IBM Domino Designer?

Simple discussion database application
Customized databases from simple repository database application to a complex workflow
database applications (with automated email notification, uploading and downloading of data)
What is an IBM Domino Application?

IBM Domino applications enable people to share, collect, track, and organize information, using
Lotus IBM Domino® or the web using IBM Domino Designer.
Developers can create applications to meet a variety of business needs, including:
Workflow applications that route information.
Tracking applications that monitor processes, projects, performance, or tasks.
Collaboration applications that create a forum for discussion and collaboration.
Data integration applications that work with relational databases and transactional systems.
Dynamic applications that produce content based on, for example, user name, user profile,
access rights, or time of day.
Localization and Management applications that use IBM Domino Global WorkBench to
translate IBM Domino databases and Web sites.
Additionally, IBM Domino Designer can create IBM Domino components to be used in a larger
composite application.
Where to get the Free IBM Domino Designer 8.5?

IBM made the IBM Domino Designer 8.5 for free but you need to register to their site in order
to download. Here is the link >>
https://www.ibm.com/developerworks/downloads/ls/dominodesigner/index.html
Information Sources:
https://www.ibm.com/support/knowledgecenter/SSVRGU_8.5.3/com.ibm.designer.domino.main.doc/H_TOUR_APPLICATIONS.html
https://www.ibm.com/support/knowledgecenter/SSVRGU_8.5.3/com.ibm.designer.domino.main.doc/H_CHAPTER_1_INTRODUCTION_TO_DOM
INO_DESIGNER_CHAP.html

The SDLC – Software Development Life Cycle
The systems development life cycle (SDLC), also referred to as the application development
life-cycle, is a term used in systems engineering, information systems and software engineering
to describe a process for planning, creating, testing, and deploying an information system.
A systems development life cycle is composed of a number of clearly defined and distinct work
phases which are used by systems engineers and systems developers to plan for, design, build,
test, and deliver information systems. Like anything that is manufactured on an assembly line,
an SDLC aims to produce high-quality systems that meet or exceed customer expectations,
based on customer requirements, by delivering systems which move through each clearly
defined phase, within scheduled time frames and cost estimates. Computer systems are
complex and often (especially with the recent rise of service-oriented architecture) link multiple
traditional systems potentially supplied by different software vendors. To manage this level of
complexity, a number of SDLC models or methodologies have been created, such as waterfall,
spiral, Agile software development, rapid prototyping, incremental, and synchronize and
stabilize.
Source: https://en.wikipedia.org/wiki/Systems_development_life_cycle
We will not discuss here the different types of SDLC models (e.g. waterfall, spiral, etc...) as this
is another intensive discussion and can be created in a separate book. Such topic is an interest
of the Project Managers.
What we will discuss here are the SDLC methodologies which are:
Planning
Analysis
Design
Implementation
Maintenance

Planning
This is the phase where you gather the requirements, do the brainstorming and document the
plan. In this phase, you'll meet with the stakeholders / subject matter experts / users involved
in the process that you are trying to improve or develop. If you are part of this process, it would
be easier for you to plan. This is also the phase where you get the necessary project approvals.
This is also the phase where you create your initial timeline. The timeline may change during
the SDLC process but should be minimal. The plan should be thought thoroughly with
corresponding timeline. The most critical dates in creating a plan are the Start Date and the End
Date.
One of the best tool in creating such timeline is a Gantt Chart.

A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts illustrate the
start and finish dates of the terminal elements and summary elements of a project. Terminal
elements and summary elements comprise the work breakdown structure of the project.
Modern Gantt charts also show the dependency (i.e., precedence network) relationships
between activities. Gantt charts can be used to show current schedule status using percent-
complete shadings and a vertical "TODAY" line as shown here.
Source:
Photo Original uploader was Garrybooker at en.wikipedia
Later versions were uploaded by Abdull at en.wikipedia.derivative work: Malyszkz (talk) - GanttChartAnatomy.png, Public
Domain, https://commons.wikimedia.org/w/index.php?curid=15018988

Analysis
Systems Analysis is the act, process, or profession of studying an activity (such as a procedure, a
business, or a physiological function) typically by mathematical means in order to define its
goals or purposes and to discover operations and procedures for accomplishing them most
efficiently.
Source: https://www.merriam-webster.com/dictionary/systems%20analysis
This is the phase where you do your algorithm and flow charts. You analyze how the process
will flow and what will be the series of actions and events that will happen in the program that
you are developing. In simple terms, if you did some brainstorming during the planning phase,
this is where you connect the dots.
Algorithm
An algorithm is a procedure (or formula) for solving a problem, based on conducting a

sequence of specified actions. Source: http://whatis.techtarget.com/definition/algorithm
Source: https://www.wikihow.com/Write-an-Algorithm-in-Programming-Language

Flow Chart
A flowchart is a type of diagram that represents an algorithm, workflow or process, showing

the steps as boxes of various kinds, and their order by connecting them with arrows. This
diagrammatic representation illustrates a solution model to a given problem. Flowcharts are
used in analyzing, designing, documenting or managing a process or program in various fields.
Source: https://en.wikipedia.org/wiki/Flowchart
Photo By svg by Booyabazookaoriginal png by Wapcaplet - vector version of Image:LampFlowchart.png, CC BY-SA 3.0,
https://commons.wikimedia.org/w/index.php?curid=714537
I will not further discuss about flow chart that much. What you only need to learn is that the
rectangular symbol is a process while the diagonal symbol is a condition. You also need to know
how to put the arrows.
When you use these tools, it will be easier for you to transition to the next phase.
You are now ready to design the system.

Design & Testing
Systems design is the process of defining the architecture, modules, interfaces, and data for a
system to satisfy specified requirements.
Source: https://en.wikipedia.org/wiki/Systems_design
In System Design, the following elements must be taken into consideration:

User Interface Design
From the word itself, user-interface. This is the part where you create the design of what the
user will see and use.
Data Design
This is the part where you take into consideration what are the fields that you'll be including in
your project, which form to place them, what are the characteristics of these fields.
Why fields? Because in IBM Domino Designer or any other programming tools/languages, the
field is the object that holds and store your data.
Process Design
This one is about the workflow, other systems that may possibly integrate with the system
that you are developing, how you connect to the database and the network, how much storage
you need to consume.
Luckily in IBM Domino Designer, you don't need much to think about these things as IBM
integrates most of the things for you. You no longer need to think much about how your
application will connect to the database unlike other programming tools/languages.
In this phase, you may already develop your own application.

This is still part of the design phase, the actual creation and designing of your system.
But my advise to you is this, prior to actual development, create first the design in a piece of
paper or using a word document. This way, your development will flow smoothly as you have
your concrete plan based on carefully analyzed design.
Once you are done with your design and development, you have to test.
In each test, it's ok to find some errors especially if you are just beginning. These errors will
make you better understand how things work. Through these errors, I learned.

Implementation Phase
The Implementation phase is when the end user of your software is foremost in your mind.
During this phase you create the documentation and tools the customer uses to make informed
decisions about how to deploy your software securely. This marks the testing phase finished. All
scenarios should have already been covered during this time.
Source: https://msdn.microsoft.com/en-us/library/windows/desktop/cc307416.aspx

The Different Environments
The SIT Environment

This is the systems integration testing environment.
From the word itself, systems integration. It is the environment where integration with other
systems is being made so that any integration errors may already be addressed prior to sending
the system to users for testing.
One example of systems integration is if System A needs some fields from System B.
The UAT Environment

This is the user acceptance testing environment.
This is where the users tests the system and verify if the functionalities are already acceptable
to them.
Prior to the UAT testing, users must already be oriented on how to use the system so that
they, in turn, will be able to prepare the necessary test scripts and test scenarios.
Users, in this part, is responsible for ensuring that all scenarios are captured and taken care of
by the system. There may be cases of systems limitation and it will be the users to decide if it is
acceptable to them otherwise a revision should be made.
The Production Environment

This is the real environment where testing was already finished and the system should have
been free from test errors.
Once the system is already deployed in production, no further revisions can be made unless
the system undergoes a change request from the users.
The system you are developing may undergo these three environment or may vary depending
on your company policies on deploying IBM Domino applications.

Maintenance
The Maintenance Phase occurs once the system is operational / implemented.

It includes implementation of changes that the software might undergo over a period of time,
or implementation of new requirements after the software is deployed at the customer
location.
Source: https://eternalsunshineoftheismind.wordpress.com/2013/03/.../sdlc-phase-5-maintenance/

Let's Get Started with the
Guided Activity

Let’s Bring Out the Master in YOU
Baby Steps to Lotus Notes Mastery… with no steps skipped.
For the last 12 years, I used to teach my teammates in creating Notes Application… and I often start with
an assignment. The tutorial revolves there and as soon as we were done with their assignments, they
eventually became experts… and they were able to create applications way better than those of what I
was able to produce.
They’ve become LOTUS MASTERS…
And that is my plan for you…
To become a Lotus Master, too.
We’ll start with an assignment and finish off revealing the Lotus Master in you, even if you are just a
beginner in notes programming or even if you’re not a programmer.

Assumptions
Prior to performing the guided activity, it is in the assumption that you have:
Have already installed the IBM Domino Designer.
Have seen other applications made in IBM Domino Designer.
Have a clear goal why you wanted to learn IBM Domino Designer.
In this guided activity, it is assumed that the plan has already been made.
The requirements, instructions, flowchart and design are already provided. All you have to do is
understand what needs to be done and apply the learnings from this book. Since this is a
guided activity, all actions that must be performed are well-written with no step skipped.

Where It Will All BEGIN
Let’s start with an early assignment. Just tell me your thoughts. You don’t need to know how to do it yet.
You just have to create a plan in your mind how the process will go.
We’ll have baby steps and I’ll guide you in each step.
For now, I am giving you something to think about. We need to exercise your mind and prepare it for a
more complex thinking later.
Assignment#1:
1. Create a database to upload and update employee details. The database will be a workflow tool
for requesting and approval for an Employee SSS Loan where the system should be able to check
whether the employee has an existing loan or has none. If with existing loan, the request must
not proceed. Otherwise, the request will go to the approver then to the implementer once
approved. Initial data is as follows:
SSS ID EXISTING EMAIL ID IMMEDIATE

EMPLOYEE LAST FIRST SSS LOAN SUPERVISOR’S
ID NAME NAME EMPLOYEE ID
987654321 jsantiago@comail.com 000005
000001 SANTIAGO JOSEFINA
987654322 ereyes@comail.com 000005
000002 REYES ERLINDA
987654323 10,000.00 mmendoza@comail.com 000009
000003 MENDOZA MARIO
987654324 rcruz@comail.com 000009
000004 CRUZ RONALD
987654325 msantos@comail.com 000005
000005 SANTOS MAY
DELA 987654326 1,500.00 cdelarosa@comail.com 000009
000006 ROSA CECILIA
987654327 logil@comail.com 000009
000007 GIL LIZA
987654328 mcabral@comail.com 000009
000008 CABRAL MARIA
987654329 rcastro@comail.com 000010
000009 CASTRO RAUL
(Implementer) SSS Processor’s email: sssprocessor@comail.com

To do this, you have to follow the instructions in items#2-3 first.

2. Create a workflow/flowchart. Minimum information: input, process, output
Requirements:
a. Each employee can create a request for an SSS loan
b. SSS Loan requests must pass through the Immediate Supervisor for approval
c. Once approved, an email must be sent to the SSS processor
d. Document status should be: Draft, Pending Approval, Approved, Processed.
 Draft: refers to documents that are saved but not yet sent for approval
 Pending Approval: refers to documents that are saved and sent for approval but not
yet approved.
 Approved: refers to documents that are already saved and approved, ready for
processing
 Processed: refers to documents that are already processed.
3. Write the algorithm of the series of events that you want your program to do for you.

Do not cheat please…
Do the assignment on your own first.
Do not proceed yet with the next module, as we will be discussing a sample for your assignment.
Allow yourself to absorb the requirements first, and then try if you can work on the assignment.
You may write your response to the assignment in the worksheet provided along with this book.

APPRENTICE’S RESPONSE to the ASSIGNMENT:
Yes, that’s you! You are now officially my apprentice.
 YOUR INPUT-PROCESS-OUTPUT (What are your inputs (e.g. the files and the fields to be used in your
application)? What should you do with your input to achieve the desired output? What will be the
result of your process (e.g. reports)?
 YOUR FLOWCHART (How will your input and process work together to derive the output? Who will
be your actors? What will each of the actors do?)
 YOUR ALGORITHM (Step by step process on what should the script do next e.g. change of field’s
value, document status, send an email, etc…)

A LITTLE REMINDER
Whether you did the assignment or not, we will be discussing on how you could have done it.
I would just like you to try to absorb what we are trying to do in the assignment.
The reason I asked you to do it is for you to be able to plan for your sample “PROJECT”.
Remember, “If you fail to plan… you plan to fail!”
So if you really want to learn and absorb what I am about to teach you… then, do your assignment.
Do not proceed to the next page if you haven’t even tried responding to what I wanted you to do.
ABSORB!
LEARN!
Did you know that when you are trying to learn new things, your brain is creating new nodes/neurons in
your brain that makes you a bit more intelligent than your old self?
You might tell me, “I am not a programmer… I cannot do this!”
Let me tell you that I have taught a doctor, an accountant, a real programmer and they all started with
an assignment similar to what I wanted you to do.
Let this sink in: “Everything is possible. All things can be learned! It’s just a matter of mindset.
Whatever you tell yourself on whether you can or you can’t… you are right!”

INSIDE THE LOTUS GURU’s MIND
Our general task is in assignment #1, while the rest of the requirements and how to do it will be
answered in your response to assignments #2 and #3.
Let’s now create a possible answer for assignments #2 and #3.
Based on the given information, we can derive the input, process and output.
Input:
- Upload file
- Request
Process
- Validation if the employee already has an existing loan
- Workflow approval from request creation, approval and implementation
Output
- Processed/implemented request
- Reports/Views

INPUT
From the upload file, we can also think of the fields that we’ll need which is the headers/column titles of
the upload file.
SSS ID EXISTING EMAIL ID IMMEDIATE

EMPLOYEE LAST FIRST SSS LOAN SUPERVISOR’S
ID NAME NAME EMPLOYEE ID
1. Employee ID
2. Last Name
3. First Name
4. SSS ID
5. Existing SSS Loan
6. Email ID
7. Immediate Supervisor’s Employee ID
You may then think of the other fields essential for your workflow process.
1. Request reference number

2. Status of the request
3. Audit trail log
4. Date filed
5. Date approved
6. Date implemented
7. Remarks

PROCESS
For us to be able to plan how the application will behave, we need to create a flowchart.
In a flowchart, we need to find out who will be the “actors” for each task, so in our assignment, we will
have: the Requestor, the Approver and the Implementer.
The Requestor will be any of the listed employees.
The Approver will be any of the listed Immediate Supervisor depending on who the requestor is.
The Implementer will be the SSS Processor whose email is sssprocessor@comail.com.
Sample Flowchart
Requestor Approver Implementor
Start Create Request

Approve? Y Send Request to Implement
Implementer request
N
Y w/ loan? End
Request will be
N tagged as NOK
Send Request to
Approver
Note: Since this is a workflow, each arrow means that there will be a change in the document status
along with the log and the time stamps plus an email notification to the next “actor”.

Detailed Flowchart
You can design your flowchart as granular as you want it to be. The more detailed it is, the more that
you can easily convert these flowchart symbols into programming codes.
We will still start with the creation of request.
However, this is not as simple as creating the request.
There are other details such as: which fields are needed to be filled up, so we can add an input box
containing the list of fields.
Employee ID*
Last Name*
First Name*
SSS ID*
With Existing SSS Loan
(Y/N)?*
Email ID*
Start Create Request Immediate Supervisor's Save Request
Employee ID*
Request reference number
Status of the request
Audit trail log
Date filed
Date approved
Date implemented
Remarks
Right after the input box, we need to validate if the required fields (or the items with asterisk) were
properly filled out, so we will need a decision box represented by a diamond.
Employee ID*
Last Name*
First Name*
SSS ID*
With Existing SSS Loan
(Y/N)?*
Email ID*
Start Create Request Immediate Supervisor's Save Request
Employee ID*
Status of the request
Audit trail log Required
Date filed fields
Date approved filled-up?
Date implemented
Remarks
Each decision box is answerable by a Yes or a No.
The NO scenario.
You have to think about what will happen if the answer is a Yes and what will happen if the answer is a
No. On a usual scenario, having a ‘No’ results to prompting an error message and the process will go
back to the previous activity. Let’s illustrate a ‘No’ scenario.
Employee ID*
Last Name*
First Name*
SSS ID* Save Request
With Existing SSS Loan (Y/N)?*
Email ID*
Immediate Supervisor's Employee
ID*
Status of the request Required
N
Audit trail log fields Prompt Error
Date filed
filled-up?
Date approved
Date implemented
Remarks
The YES scenario.

Employee ID*
Last Name* Save Request
First Name*
SSS ID*
With Existing SSS Loan (Y/N)?*
Email ID*
Immediate Supervisor's Employee N
ID* Required
Start Create Request fields Prompt Error
Status of the request filled-up?
Audit trail log
Date filed Y
Date approved
Date implemented
Remarks Save Request
Push email
notification to
approver with a
link
Prompt confirmation message

that the request was
successfully saved.

I used a connector A (for which you can use any letter or number) to indicate that a process will
continue on the next page.
Here’s what will happen when the approver receives the email and clicks on the link.
Request’s status will be changed to

Approver receives the email Approve ‘Rejected Request’ and the system will
N End
and opens the request push an email notification to the
(Y/N)? requestor that the request was rejected
by the approver.
Status will be changed Implementer receives the email notification,

to For Implementation implements the request and update the
and the system will document’s status to implemented.
push an email
notification to the
implementer with a link The system pushes an email notification to
the requestor that the request was already
implemented.
At the latter part of this ebook, we will convert this detailed flowchart into Lotus Scripts.
When you think you are lost, just follow the arrow heads.
Don’t worry, I’ll be with you in this journey. We’ll be discussing things in every detail.

OUTPUT
The output, more often than not, is referred to as reports.
In Lotus Notes Designer, reports are created thru VIEWS… but before we dig in, let’s design what types
of reports do we need and how each reports/views will look like.
Reports:
1. My Requests
2. View by Status
3. View by Date Created
4. View by Requestor
5. Cancelled Requests
For uniformity, let’s display all the fields from our input in our output plus the status of each requests.
Each view will just vary on the column sequence depending on which report you are viewing.

Questions to think about:
 In our flowchart above, what do you think is lacking?

 Do users simply create and create and create requests? Don’t they edit or view the documents
they’ve created?
 Do you think there is a need to validate who can view/access the document for reading?
 Do you think there is also a need to validate who can edit the document?
 If your answer is yes to the last two questions, create two decision boxes (diamond) to validate:
o Who can view/access the request document
o Who can edit the request document
 Once done, where do you think these decision boxes must be placed? Please draw your own
version of the flowchart incorporating the two decision boxes.

The Apprentice’s Edited Version of the Flowchart

Sample Project Plan
Always remember, if you fail to plan, you plan to fail.
With you having the input-process-output and a flowchart, you are almost set to completing your
PROJECT PLAN.
Without this, you might get lost in the process.
This will serve as your guide on what should you do next or how far are you in your project.
For this project, this will be our step by step process:
1. Create the blank application

2. Create the form
3. Create the fields
4. Create the edit, save, exit action buttons.
5. Create the view.
6. Create the upload script.
7. Create the outline menu.
8. Create the page menu.
9. Create the frameset.
10. Update the launch settings… and voila! You will already have a working application once you were
able to perform these ten (10) easy steps. Scripting is another set of processes that I will go in detail
a little later. Scripts will make your application more secure and more sophisticated. Don’t get to
much excited as we will reach that stage. For the meantime, let’s discuss first about algorithms.

Sample Algorithm
An algorithm is very much similar to a flowchart, just narrative.
It contains the detailed, step by step process. To help you understand what an algorithm is, please
continue reading and try to absorb the things I am about to discuss.
This will be our algorithm for processing the request (assuming that we were already able to upload the
employee information). It is also a ten (10) step process that discusses what each of the workflow
participants/actors will do to the request document.
1. The requestor will create the request document.

2. When the requestor hit save, the application should validate if the requestor was able to fill-up the
required fields.
3. Once the required fields were validated, verify if the requestor is qualified to make a loan by
checking if the employee table if he/she has an existing loan.
4. If the employee has an existing loan, tag the request document as NOK, send an email to the
requestor informing him/her that he/she is not qualified due to his/her existing loan. The request
document must no longer be editable.
5. If the employee is qualified, send an email to the approver/immediate supervisor based on the
employee table.
6. The approver must be able to have the OK or NOK button. OK for approve and NOK for reject.
7. If the approver OK’d the request, send an email to the implementer.
8. If the approver NOK’d the request, send an email to the requestor informing him/her that the
request was rejected. The document must no longer be editable.
9. Once approved, the implementer will then receive the email and process the request. Upon request
fulfillment, he/she shall update the document and tag it as implemented.
10. Once implemented, the system will prompt the user that the request was successfully implemented.
Now that you understand the input-process-output, flowchart and algorithms, I may say that you are
already equipped in understanding the process and may start creating your Notes Application.
We will start first with the basics, read on…

CREATING YOUR PROJECT
Requirements:
1. Installed IBM Notes Domino Designer

2. Plan and Algorithm (which is part of your Assignment and was discussed in this
book)
3. A little background in IBM/Lotus Notes
4. (Optional) Have watched, liked and subscribed to my YouTube tutorial
Creating the blank application

As discussed in my free video tutorial, you need to have an IBM Notes Domino Designer installed in
your PC/Laptop before you start this project.
Upon opening your Domino Designer, the welcome screen will be displayed. You may opt to read
what’s written there as it will also guide you on how Domino Designer works and how to use it.
a) Click File > Application > New to create a new application.

b) A dialog box will appear for you to specify the location and filename of the application that you
want to create and whether it will be copied from an existing template.
For this exercise, use the following information:
Server: Local
“Local” means that the application being developed will reside in your PC and not yet on a server. If you have your
development server, you may specify it here.
Title: Loan Application
You may have your own title for this project.
File name: loan.ntf
You may rename the file too.
I’m letting you use the ntf file extension which stands for “notes template file” instead of an nsf since this application is
still residing in your local PC. Once your application is ready for implementation in production, you may simply use the
template to replace the design of your production application. Don’t you worry if everything I just said is a little bit
overwhelming, I’ll explain further in the latter part of this book.
Encryption: Do not locally encrypt this database
You have to set this as not locally encrypted otherwise you cannot run your application locally in your PC/laptop.
Template: Blank
Since we are about to create an application from scratch and not copying any template, we will select Blank.
c) Click OK.

d) Domino Designer will give you a screen similar to this:
e) Congratulations! You are now able to create your very first blank notes application. From here,
you may now create your very first form.

Creating the Form
A form is used to create the notes document that will store the information, through the use of
fields, within your database. A form may contain fields, labels, pictures, tables, action buttons, etc…
You may create a form in two ways:

a) Click Create > Design > Form or
b) Simply click ‘New Form’ from the screen.

c) Name your form then click OK.
d) Your new blank form will appear. Let me walk you through the different frames of your notes
application.
 This is your full screen.

 Here is your blank form within your work pane.
 This is called your programmer’s pane where you put your notes formulas and lotusscripts.
 Here is your applications navigator which displays your design elements.

Creating the fields
A field is a value holder. It stores the value that the user has provided. Using a field, you can retrieve
those stored information.
 In creating these fields, it would be better if you also create table(s) for proper field alignment
and aesthetics.
 How to create tables?
o Click Create > Table
o Input the number of rows and columns that you want your table to contain then click
OK.

o You may adjust the column width by dragging the column dividers or by using the ruler
 Make your table similar to this table so as to help you organize your data
 Highlight the center column then update the table properties and make the left and right
border, zero.
 Create the field labels

 Create the Fields – use a unique, distinguishable field name
> Position the cursor where you want to place your field then click Create > Field.
> Determine the type of fields you’ll be creating

Field Data Types
Text
This is the default and the most commonly used data type. It can contain alphanumeric string, date or
number but interpreted as string. The indicator that you have used a text data type is the T sign found at
the bottom right of the field.

Number
This data type is used for mathematical calculations or if you simply want it to be displayed as a numeric
data. The indicator that you have used a number data type is the sharp sign (#) found at the bottom
right of the field.

Date/Time
This data type is used for displaying dates and/or time. The indicator that you have used a date/time
data type is the number 16 enclosed in a square at the bottom right of the field.

Dialog List
This data type is used to display a selection of one or more values that the user may select. The indicator
that you have used a dialog list is the arrow down icon found at the bottom right of the field. This may
or may contain multiple values. It can work similarly as the radio button or the checkbox.

Check Box
This data type enables user to select more than one value in a given list. The indicator that you have
used a check box is the square icon found at the left side of the field. Use this if you need the input to be
selected is more than one, otherwise, you may use the dialog list or the radio button.

Radio Button
This data type restricts user to select just a single value in a given list.

Names
This data type is used to look up to the names within the address book list.
Password
This type is used for collecting values with a mask or any values typed will be displayed as a specified
character (e.g. asterisk *).

> You may preview the form by clicking the preview icon ( ) to see the difference of each
field. Make sure you save the changes you’ve made so that it will appear in the preview.
 Know the fields relevant to your application; Distinguish which items are mandatory by putting a
red asterisk (*) beside its label within the form.

Creating the Action Buttons
This is the action pane. This is where you create your action buttons. Add icons for aesthetics.
If you are unable to see the action pane, go to the right-most border and drag it. It is simply hidden.

Create the action buttons by following these simple steps:
(1) Right-click on the empty action pane then select ‘Create Action’. Do the steps
repeatedly until you were able to create the four buttons: New, Edit, Save and Exit.
(2) Name your action buttons
(3) Add icon for aesthetics

(4) Select the action buttons which you want to be displayed in the right-most portion of
the screen (e.g. Exit button).
(5) Preview your action buttons by clicking the preview icon ( ). Make sure that you’ve
saved your work so that changes will take effect.

You may notice that your window title in the uppermost portion of the screen is (Untitled), you may
update it by clicking anywhere within the form then on the programmer’s pane, input your desired
window title.
(6) Add Notes Formulas to your actions.

(a) New
 Double click the action button ‘New’ then in the programmer’s pane, type-in
@Command([Compose];"":"";"Loan Request")

Do the same to the other action buttons using these formulas:
(b) Edit - @Command([EditDocument])
(c) Save - @Command([FileSave])

(d) Exit - @Command([FileCloseWindow])
CONGRATULATIONS!!!
You have now created your very first form  (if you have followed all my instructions in this module).
Creating the View

A view is used to display the contents of each field within a document/form.
To create a view:
1) Go to Views then click New View.

2) Name your view, click the ‘Copy From…’ button and select ‘Blank’ then click the OK button.
If you name your view enclosed in a parenthesis, it becomes a hidden view. We’ll discuss more
about it later.
3) Your newly created view will now be a part of your view list.

4) When you create a view, be observant on the checkmark under the icon with an x in it.
5) Once any of your views has that check, go to the Design Properties and you will see that your view
is, by default, set to be prohibited from being modified.

6) Make sure that you uncheck it while your project is not yet tested and final. If this remained
checked, all changes will no longer apply to your design elements when you refresh/replace your
design in production.
7) Open the selected view to edit the contents (via double click or right click then open).
This will be your default view. The first column has a sharp sign (#) header.

8) Create additional columns as needed by right-clicking on a column then select Insert New Column.
9) Label your columns by double clicking on each item then input a title.

10) Assign values to be displayed in each column. Make sure you’ve chosen the correct field for each.
11) Customize your header and content fonts.

12) Preview your work. Look for this icon .
You have just made your own view. You can create as many views as you needed.

Creating the outline menu
The outline is commonly used for managing menu items. You can also use the navigator but this one is
more user friendly.
Here’s a sample menu created using an outline:
An outline, within the Domino Designer, looks simply like a set of buttons aligned together which you
can indent and outdent depending on your preference.
It forms part of the Shared Elements together with Sub forms, Fields, Columns and Navigators. In this
eBook, we will only discuss the essentials and we will not cover all the elements as they are seldom
used.

How to Create an Outline?
1) Go to Shared Elements > Outline then click New Outline.
2) Name your Outline then click OK (you may name it ‘Menu’).

3) Click ‘New Entry’.
4) Name your outline entry.

5) Repeat steps 3 & 4 until you have completed your desired menu entries.
6) Fill in the content section of each outline entry.

a) Select Type.
 Choose Action if you are to invoke an event using Notes Formula (e.g. creating a new
document).
 Choose Named Element if you are to invoke an existing Notes Element (e.g. opening a view)
 Choose Link if you are to open an hyperlink.
 Choose URL if you are to open a webpage.

b) Input Values.
 If you choose Action, you need to know the Notes Formula to invoke what you want Notes
Designer to do. For creating a new document, you may use:
@Command(Compose;FormName)
You may learn more about Notes Formulas in the Appendices portion of this ebook.
 If you choose Named Element, choose the type of element: Page, Form, Frameset or View.
The most commonly chosen option is ‘View’.

c) Select the chosen element you want to display.
d) Input Frame name. Fill-in this option only if you have a frameset and you wanted your element
to be displayed in one of your frames, otherwise, leave it blank. I’ll explain later why the Frame
input is ‘Right’.
e) Repeat steps 6a to 6d until you have all your elements filled in with values.
f) Here’s a guide for each of your elements as sampled. P.S. You should have the views created prior to
calling it in the outline entry.
 Create New Request
(1) Type: Action
(2) Value: @Command(Compose;””:””;”LoanRequest”)
(3) Frame:

 All Requests
(1) Type: Named Element - View
(2) Value: “(All Requests)”
(3) Frame: Right
 By Status
(1) Type:
(2) Value:
(3) Frame:
 Draft
(2) Value: “(Draft)”
(3) Frame: Right
 For Approval
(2) Value: “(For Approval)”
(3) Frame: Right
 For Implementation
(1) Type: Named Element
(2) Value: “(For Implementation)”
(3) Frame: Right
 Done
(2) Value: “(Done)”
(3) Frame: Right
 By Request Date
(2) Value: “(By Request Date)”
(3) Frame: Right
 By Employee Number
(2) Value: “(By Employee Number)”
(3) Frame: Right
 Exit
(1) Type: Action
(2) Value: @Command(FileCloseWindow)
(3) Frame:

7) (Optional) You may input preferred icons/images in each of your outline entries.
8) Once finished with the outline entries, you may now save it and create the page menu by clicking
Use Outline.

Creating the Menu Page
1) Upon saving the outline and clicking ‘Use Outline’, a new page will be created embedding the
outline. This will serve as your menu.
2) You can customize the embedded outline as you please.

a) Insert white spaces at the top by putting the cursor at the left most portion of the page then
press the Enter key twice or thrice.

b) Right-click the outline then select the Outline Properties.
c) Name the embedded outline as ‘Menu’.

d) Select the following attributes:
 Type: Tree Style
 Title Style: Simple
 Twisties: Show twisties and OS Style
 Width: Fit to Window
 Height: Fit to Content
e) Go to the next tab with the ‘a’ symbol.

f) Select the following:
 Sublevel Font
 Calibri
 Normal: Black; Selected: Red; Moused: Blue
g) Click ‘Set All to Same’ button so that Top Level Font and Title Font will acquire the same
attributes.

h) Go to the 3rd tab for the background colors.
 Select ‘Sub-Level Background’.
 Normal: None; Selected: Light Yellow; Moused: Light Blue
 Set all to Same
i) Go to the 4th tab

j) Select Sub-Level Layout, then change the Entry > Offset to 0.200 then click Set All to Same.
k) Click Save. The system will ask you to provide a page name.

3) You may opt to name the page upon saving or by naming the page manually by going to the Page
Properties.
4) Once saved, you may preview your page. You may try hovering your mouse to each of the outline
entries.
5) Congratulations! You now have a menu. Your next task will be to create a frameset.

Creating the frameset.
1) Go to Framesets, then click New Frameset.
2) Name your frameset and set the number of frames. For this example, we’ll choose 2.

3) Name your frames.
a) Name your first frame as ‘Left’;
b) Name your second frame as ‘Right’.

4) Choose what you wanted to display on your first frame.
We’ll display here the menu page we recently created with an embedded outline.
a) Choose the following:
 Type: ‘Named Element’ ‘Page’;
 Value: ‘pgMenu’
5) Now, choose the element you want to display on the ‘Right’ frame. Let’s just display the view ‘By
Employee Number’. To do this, choose Type: ‘Named Element’ – ‘View’; Value: ‘(All Requests)’

6) Now, this is where your outline entries’ frame attribute make sense. Remember the step 6d from
the outline entries where I told you I’ll explain later why we needed to put ‘Right’ as the frame?
If you can’t remember, it’s this one:
This means, that whenever you click the outline entry, it will be displayed in the ‘Right’ frame, which
is the 2nd frame we created on your frameset… remember?
7) With all these said, you have to make sure all your outline entries are properly set-up so that it will
work the way you wanted it to. Try previewing your frame and clicking each outline entry.

Updating the launch settings
You’re almost done creating your first basic application.
You already have the form(s). Check.
You already have the views. Check.
You already have the menu using outline and page. Check.
You already have the frameset. Check.
Whenever you create a new application, a bookmark is created in your workspace. However, when you
try clicking your bookmark, it opens the default view and not your menu frameset. Have you ever
experienced that?
Let’s try it with our raw application. Try opening it through the workspace by double-clicking on the
bookmark.

What we needed to do now is to set-up how your application will launch by updating the launch
settings.
1) Right-click on the application then select Application > Properties.
2) Go to the 5th tab then select ‘Open designated Frameset’ on the first field.
3) Select Name:‘Menu’
4) You’re all set. Try it out. Congratulations! You have just created your first basic application 

Thank you for reading this book and for reaching this page.
I hope you have learned something from it. Sorry medyo hindi sya totally TagLish, may mga vocabularies
kasi in IBM Domino Designer na hindi kayang tagalugin… but I hope naintindihan nyo yung mga topics
discussed in this book.
Please don’t forget to subscribe to www.dominodesignersecrets.com for more tips and promotional
messages.
This eBook is free and forever will be.
Again, thank you and hope you’ll enjoy your journey learning the IBM Domino Designer.
Copyright 2018
www.dominodesignersecrets.com
Manila, Philippines

IBM Domino Designer SECRETS

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

IBM Domino Designer SECRETS

Hochgeladen von

Copyright:

Verfügbare Formate

www.dominodesignersecrets.

IBM Domino Designer

Learn to Create your Own Application

2 | IBM Notes Domino Designer Secrets

This book aims to allow its readers to :

Who should read this book?

Question and Answer:

Q: Do I have to be a programmer to develop an application?

Q: Do I need to purchase a license in order to do this?

Q: Will I be able to create a project even if I have no knowledge in programming?

3 | IBM Notes Domino Designer Secrets

What type of applications can be created using IBM Domino Designer?

What is an IBM Domino Application?

Where to get the Free IBM Domino Designer 8.5?

4 | IBM Notes Domino Designer Secrets

5 | IBM Notes Domino Designer Secrets

One of the best tool in creating such timeline is a Gantt Chart.

6 | IBM Notes Domino Designer Secrets

An algorithm is a procedure (or formula) for solving a problem, based on conducting a

7 | IBM Notes Domino Designer Secrets

A flowchart is a type of diagram that represents an algorithm, workflow or process, showing

8 | IBM Notes Domino Designer Secrets

In System Design, the following elements must be taken into consideration:

In this phase, you may already develop your own application.

9 | IBM Notes Domino Designer Secrets

10 | IBM Notes Domino Designer Secrets

The SIT Environment

The UAT Environment

The Production Environment

11 | IBM Notes Domino Designer Secrets

The Maintenance Phase occurs once the system is operational / implemented.

12 | IBM Notes Domino Designer Secrets

13 | IBM Notes Domino Designer Secrets

Baby Steps to Lotus Notes Mastery… with no steps skipped.

They’ve become LOTUS MASTERS…

And that is my plan for you…

To become a Lotus Master, too.

14 | IBM Notes Domino Designer Secrets

15 | IBM Notes Domino Designer Secrets

SSS ID EXISTING EMAIL ID IMMEDIATE

(Implementer) SSS Processor’s email: sssprocessor@comail.com

16 | IBM Notes Domino Designer Secrets

17 | IBM Notes Domino Designer Secrets

Do the assignment on your own first.

18 | IBM Notes Domino Designer Secrets

Yes, that’s you! You are now officially my apprentice.

19 | IBM Notes Domino Designer Secrets

Remember, “If you fail to plan… you plan to fail!”

You might tell me, “I am not a programmer… I cannot do this!”

20 | IBM Notes Domino Designer Secrets

Let’s now create a possible answer for assignments #2 and #3.

21 | IBM Notes Domino Designer Secrets

SSS ID EXISTING EMAIL ID IMMEDIATE

1. Request reference number

22 | IBM Notes Domino Designer Secrets

The Requestor will be any of the listed employees.

The Implementer will be the SSS Processor whose email is sssprocessor@comail.com.

Start Create Request

23 | IBM Notes Domino Designer Secrets

We will still start with the creation of request.

Start Create Request

However, this is not as simple as creating the request.

The YES scenario.

Prompt confirmation message