...
“<Blank>” – A second keyword field, however without the values set. This will allow you a pre-made field set to use as a template for additional fields. Copy these and paste in the Form, changing the names accordingly. See below for further explanation.
Configuring Custom Fields
TEXT fields
Above is an example of fields used for adding a custom text field (“Edit Subject” in this case).
You will need 6 fields to configure a Text field in the UI.
IEN_CustTXT01_CRM – Add your CRM Field Name as a value. This is the value for the field from your Data Source. If you do not know the field name, you can look in the WSDL of the Data Source. In the example, the CRM Filed Name for the subject line of an Email is “Subject”.
IEN_CustTXT01_ShowIn - Add a list of Notes Form Names here in which the field should be visible. In the example, the custom field “Edit Subject” is only visible if the Memo is in the Email InBox in Notes.
You can add multiple form names as value, each field in quotes and separated by a colon, for example: v: = “EMAILINBOX” : “APPOINTMENT”.
The list of available forms are: “ALL”, “EMAILINBOX”, “EMAILSENT”, “APPOINTMENT”, “TASK”.
IEN_CustTXT01_Prop – This is a place-holder used to add the properties of a field. By Default, we set this field only to determine if the field is mandatory (“ISREQUIRED=1” means field is Mandatory).
You may add more properties as you see fit.
IEN_CustTXT01_HideIf – This is a Backend field used to hide the field in UI based on value of field IEN_CustTXT01_ShowIn
IEN_CustTXT01_Lbl - This is where you add your own field label. This label is what will be displayed in the dialog UI.
IEN_CustTXT01 – Plain Text field where the user may enter a new value from the dialog UI
If you need additional TEXT fields in the UI dialog, then copy all the fields shown above and paste them in the next row of the table. You must rename the fields to a unique value. An example is to change the number of each field up one (IEN_CustTXT02_CRM, IEN_CustTXT02_ShowIn, IEN_CustTXT02_Prop).
Also make sure to change values of all these fields and to add hide properties of IEN_CustTXT02_Lbl and IEN_CustTXT02 as shown below
KEYWORD fields
Complete all the same steps above with unique names for the keyword fields. There is one additional field – in this example “IEN_CustKW01_Values” - that needs to be added to configure the keyword values (shown below). A sample of all the required keyword fields has been provided in the iencustomform as part of the product installation.
Note: The picklist can not be read dynamically from your Data Source. It must be hard coded as shown, and updated anytime your Data Source is changed.
Final Field - IEN_AllCustFldsEnabled
After completing the above steps and all your TEXT and KEYWORD fields are set, you need to list which of those fields are to be enabled in the ‘Select Fields’ UI. These field names need to be entered as a value in the field “IEN_AllCustFldsEnabled” as shown below. Only then will the display the fields in the UI.
This field will allow you to remove fields from the UI without the need to remove them from the design.
Once the custom form is saved, your changes are in effect. It is recommended that you recompile all lotusscript once your work is complete. This will also sign your DB elements with your current ID.