Activity for RapidASDev for Oracle
-
Domen Dolar modified a comment on discussion Hints and Tips using RASD
The re is simple build in way to add label-description from pop up LOV into tbe block. 1.Create LOV. The LOV have id and label values. 2.Set LOV to the filed where shall be triggered. Field is type of INPUT (or null) In this case when you double click on field the LOV will be opened in pop up window. 3.In the block where is your field create new field with name: fieldnamewhereissetlov +** LABEL ** like: USER_ID - is fiealed with LOV Users then we create field USERIDLABEL The result is: ** Additional...
-
The re is simple build in way to add label-description from pop up LOV into tbe block. 1.Create LOV. The LOV have id and label values. 2.Set LOV to the filed where shall be triggered. Field is type of INPUT (or null) In this case when you double click on field the LOV will be opened in pop up window. 3.In the block where is your field create new field with name: fieldnamewhereissetlov +** LABEL ** like: USER_ID - is fiealed with LOV Users then we create field USERIDLABEL The result is: **Additional...
-
The re is simple build in way to add label-description from pop up LOV into tbe block. 1.Create LOV. The LOV have id and label values. 2.Set LOV to the filed where shall be triggered. Field is type of INPUT (or null) In this case when you double click on field the LOV will be opened in pop up window. 3.In the block where is your field create new field with name: fieldnamewhereissetlov +** LABEL ** like: USER_ID - is fiealed with LOV Users then we create field USERIDLABEL The result is: **Additional...
-
The re is simple build in way to add label-description from pop up LOV into tbe block. 1.Create LOV. The LOV have id and label values. 2.Set LOV to the filed where shall be triggered. Field is type of INPUT (or null) In this case when you double click on field the LOV will be opened in pop up window. 3.In the block where is your field create new field with name: fieldnamewhereissetlov +** LABEL ** like: USER_ID - is fiealed with LOV Users then we create field USERIDLABEL The result is: Additional...
-
The re is simple build in way to add label-description from pop up LOV into tbe block. 1.Create LOV. The LOV have id and label values. 2.Set LOV to the filed where shall be triggered. Field is type of INPUT (or null) In this case when you double click on field the LOV will be opened in pop up window. 3.In the block where is your field create new field with name: fieldnamewhereissetlov +** LABEL ** like: USER_ID - is fiealed with LOV Users then we create field USERIDLABEL Additional tips:
-
The re is simple build in way to add label-description from pop up LOV into tbe block. 1.Create LOV. The LOV have id and label values. 2.Set LOV to the filed where shall be triggered. Field is type of INPUT (or null) In this case when you double click on field the LOV will be opened in pop up window. 3.In the block where is your field create new field with name: fieldnamewhereissetlov +** LABEL ** like: USER_ID - is fiealed with LOV Users then we create field USERIDLABEL Additional tips:
-
The re is simple build in way to add label-description from pop up LOV into tbe block. 1.Create LOV. The LOV have id and label values. 2.Set LOV to the filed where shall be triggered. Field is type of INPUT (or null) In this case when you double click on field the LOV will be opened in pop up window. 3.In the block where is your field create new field with name: fieldnamewhereissetlov +** LABEL ** like: USER_ID - is fiealed with LOV Users then we create field USERIDLABEL
-
-
RASD_RESULTS
-
RASD_LIBS
-
RASD_HTML
-
RASD_EXECUTE
-
RASDC_TRIGGERS
-
RASDC_TEST
-
RASDC_SQLCLIENT
-
RASDC_SQL
-
RASDC_PAGES
-
RASDC_LINKS
-
RASDC_HTML
-
RASDC_FORMS
-
RASDC_FORMS
-
RASDC_BLOCKSONFORM
-
RASDC_BLOCKSONFORM
-
RASDC_BLOCKSONFORM
-
RASDC_BLOCKSONFORM
-
RASDC_FIELDSONBLOCK
-
RASDC_CSSJS
-
RASDC_BLOCKSONFORM
-
Documentation
-
Documentation
-
When form is created we can start adding diferent blocks on it. 1. First we will add block where we can edit content. On "Form" page fill data for new block. Setting Value Description Block B10 Name of block must contain only letters, numbers, sign '' and must be started with letter. Table, View, Synonym EMP ... T List of DB objects you have access Rows 15 Number of rows in table (0 - all from DB, 1 - one, ...). If Rows are 1 and Bck / Fwd not checked labels of fields on form are left of fields othervise...
-
When form is created we can start adding diferent blocks on it. First we will add block where we can edit content. On "Form" page fill data for new block. Setting Value Description Block B10 Name of block must contain only letters, numbers, sign '' and must be started with letter. Table, View, Synonym EMP ... T List of DB objects you have access Rows 15 Number of rows in table (0 - all from DB, 1 - one, ...). If Rows are 1 and Bck / Fwd not checked labels of fields on form are left of fields othervise...
-
RASDC_TRIGGERS
-
RASDC_TRIGGERS
-
RASDC_TRIGGERS
-
RASDC_TRIGGERS
-
When you create SQL LKOV you get message like: select 'Code or Id stored in DB' id, 'Description shown insted of code' label from dual --Important! The length result in ID must be less than 100chars and result in LABEL must be less than 500chars! In RASD, an LOV query must always return two columns with mandatory aliases: * id → the value that is stored in the field (primary key, code) * label → what the user sees in the list (description) so LOV must have at least two cols one named id and other...
-
You can use below settings for on blocks. You can use them in any trigger. BLOCK#SET.pcommit := false/true/null BLOCK#SET.pselect := false/true/null BLOCK#SET.poutput := false/true/null If you set values to true or false these override setting from pages. So if you have block X on page Y and you would like to hide it on output you can set output := false or if you don't have block on one page and you set output := true the block will show. To set default values you set them to null.
-
You can use below settings for on blocks. You can use them in any trigger. BLOCK#SET.pcommit := false/true/null BLOCK#SET.pselect := false/true/null BLOCK#SET.poutput := false/true/null If you set values to true or false these override setting from pages. So if you have block X on page Y and you would like to hide it on output you can set output := false or if you dont have block on one page and you set output := true the block will show. To set default values you set them to null.
-
To activate READONLY attribute to DATE field you have to do two thinks. In DATETIME picker global settings (rasd_datepicker.html) add beforeShow code. This setting will imapact to all your forms. Added code: beforeShow: function(i) { if ($(i).attr('readonly')) { return false; } }, Like in rasd_datepicker.html <script> $(function() { $("#:NAME" ).datetimepicker({ beforeShow: function(i) { if ($(i).attr('readonly')) { return false; } }, dateFormat: ':DFORMAT', timeFormat: ':TFORMAT' :PROPERTIES ,showOn:...
-
When you create SQL LKOV you get message like: select 'Code or Id stored in DB' id, 'Description shown insted of code' label from dual --Important! The length result in ID must be less than 100chars and result in LABEL must be less than 500chars! so LOV must have at least two cols one named id and other label. 1.sample of classic LOV select deptno id, ename label from emp t order by id, label 2.sample with empty value. Usually used at SELECT elements. select '' id, '' label from dual union select...
-
For those who don't know PL/SQL and know other languages here are some tips using it: set value - use operator := logical operators = , <, >, !=, <> for end of line use ; 1.Anonymous Block (Basic Structure) Every PL/SQL program follows this structure: DECLARE -- variable declarations BEGIN -- executable statements EXCEPTION -- error handling (optional) END; 2.Variable Declaration DECLARE ** v_name VARCHAR2(50); v_num NUMBER(8,2) := 5;** BEGIN v_name := 'John Doe'; rlog('Name: ' || v_name); rlog('Num:...
-
For those who don't know PL/SQL and know other languages here are some tips using it: set value - use operator := logical operators = , <, >, !=, <> for end of line use ; 1.Anonymous Block (Basic Structure) Every PL/SQL program follows this structure: DECLARE -- variable declarations BEGIN -- executable statements EXCEPTION -- error handling (optional) END; 2.Variable Declaration DECLARE ** v_name VARCHAR2(50); v_num NUMBER(8,2) := 5;** BEGIN v_name := 'John Doe'; rlog('Name: ' || v_name); rlog('Num:...
-
For those who don't know PL/SQL and know other languages here are some tips using it: set value - use operator := logical operators = , <, >, !=, <> for end of line use ; 1.Anonymous Block (Basic Structure) Every PL/SQL program follows this structure: DECLARE -- variable declarations BEGIN -- executable statements EXCEPTION -- error handling (optional) END; 2.Variable Declaration DECLARE ** v_name VARCHAR2(50); v_num NUMBER(8,2) := 5;** BEGIN v_name := 'John Doe'; rlog('Name: ' || v_name); rlog('Num:...
-
For those who don't know PL/SQL and know other languages here are some tips using it: set value - use operator := logical operators = , <, >, !=, <> for end of line use ; 1.Anonymous Block (Basic Structure) Every PL/SQL program follows this structure: DECLARE -- variable declarations BEGIN -- executable statements EXCEPTION -- error handling (optional) END; 2.Variable Declaration DECLARE ** v_name VARCHAR2(50); v_num NUMBER(8,2) := 5;** BEGIN v_name := 'John Doe'; rlog('Name: ' || v_name); rlog('Num:...
-
For those who don't know PL/SQL and know other languages here are some tips using it: set value - use operator := logical operators = , <, >, !=, <> for end of line use ; 1.Anonymous Block (Basic Structure) Every PL/SQL program follows this structure: DECLARE -- variable declarations BEGIN -- executable statements EXCEPTION -- error handling (optional) END; 2.Variable Declaration DECLARE ** v_name VARCHAR2(50); v_num NUMBER(8,2) := 5;** BEGIN v_name := 'John Doe'; rlog('Name: ' || v_name); rlog('Num:...
-
1.You can see where in code is variable used by clicking on a 'Where is my code button' (last icon at field settings). 2.This opens new window where you can see all the lines where variable is used and in which trigger. By clicking to trigger name you will acces to code. Thanks to Pavel who prepare this topic.
-
1.You can see where in code is variable used by clicking on a 'Where is my code button'. 2.This opens new window where you can see all the lines where variable is used and in which trigger. By clicking to trigger name you will acces to code. Thanks to Pavel who prepare this topic.
-
1.You can see where in code is variable used by clicking on a 'Where is my code button'. 2.This opens new window where you can see all the lines where variable is used and in which trigger. By clicking to triger name you will acces to code. Thanks to Pavel who prepare this topic.
-
1.You can see where in code is variable used by clicking on a 'Where is my code button'. 2.This opens new window where you can see all the lines where variable is used and in which trigger. Thanks to Pavel who prepare this topic.
-
1.You can see where in code is variable used by clicking on a 'Where is my code button'. 2.This opens new window where you can see all the lines where variable is used and in which trigger. Thanks to Pavel who prepare this topic.
-
Datatable basic 1. Official documentation site: https://datatables.net/ 2. Default values of DataTable are stored in JavaScript variable _rasd_dataTableProperties const _rasd_dataTableProperties = { "responsive": false, "bJQueryUI": true, "aaSorting": [], "oLanguage": { "sSearch": "Search on table", "sZeroRecords": "No data available in table" }, "bPaginate": false, "pageLength": 10, "bLengthChange": true, "bFilter": true, "bSort": true, "aaSorting": [], "bInfo": false, "bAutoWidth": false //have...
-
Datatable basic 1. Official documentation site: https://datatables.net/ 2. Default values of DataTable are stored in JavaScript variable _rasd_dataTableProperties const _rasd_dataTableProperties = { "responsive": false, "bJQueryUI": true, "aaSorting": [], "oLanguage": { "sSearch": "Search on table", "sZeroRecords": "No data available in table" }, "bPaginate": false, "pageLength": 10, "bLengthChange": true, "bFilter": true, "bSort": true, "aaSorting": [], "bInfo": false, "bAutoWidth": false //have...
-
1.Create new trigger with NEW_ACTION and add your own code ( you can use prebuild procedures like 'pselect' and 'poutput' ). In field to set action name you can add: - constant-> 'Trigger1' - variable-> TEST,… - function-> FN(args). 2.If you set variable you can add it into form 'F' add new filed named like action and set its type to 'Submit'(or something else). 3.This will create new element (button) that will call trigger that you created. You can see your new action in trigger list. Thanks to...
-
1.Create new trigger with NEW_ACTION and add your own code ( you can use prebuild procedures like 'pselect' and 'poutput' ). In field to set action name you can add: - constant-> 'Trigger1' - variable-> TEST,… - function-> FN(args). If you set variable you can add it into form 'F' add new filed named like action and set its type to 'Submit'(or something else). This will create new element (button) that will call trigger that you created. You can see your new action in trigger list. Thanks to Pavel...
-
1.Create new trigger with NEW_ACTION and add your own code ( you can use prebuild procedures like 'pselect' and 'poutput' ). In field to set action name you can add: - constant-> 'Trigger1' - variable-> TEST,… - function-> FN(args). If you set variable you can add it into form 'F' add new filed named like action and set its type to 'Submit'(or something else). This will create new element (button) that will call trigger that you created.
-
Single line comment -- comment 2.Multi line: /* comment */ 3.Foldable block of code: ~~~ ---- name code ---- name ~~~ In RASD: 4.Shortcuts: Unfold all: CTRL+I, Fold all CTRL+U. Thanks to Pavel who prepare this topic.
-
Single line comment -- comment 2.Multi line: /* comment */ 3.Foldable block of code: ~~~ ---- name code ---- name ~~~ In RASD: 4.Shortcuts: Unfold all: CTRL+I, Fold all CTRL+U. Thanks to Pavel who prepare this topic.
-
1.Add documentation by clicking the Documentation button next to an element. 2.A window opens where you can write and save documentation. The documentation is also stored to metadata of the form. Thanks to Pavel who prepare this topic.
-
1.Add documentation by clicking the Documentation button next to an element. 2.A window opens where you can write and save documentation. The documentation is also stored to metadata of the form. Thanks to Pavel who prepare this topic.
-
1.Add documentation by clicking the Documentation button next to an element. 2.A window opens where you can write and save documentation. Thanks to Pavel who prepare this topic.
-
Debug mode (π) 1.Enter debug mode by clicking on small pi sign at programs version. The page will refresh and pi sign will be shown at every element. 2.Hover over topmost pi sign to open textfield. Copy link of your form (RASD development link), paste it in textfield and click submit. In program you will se many pi chars. From all you can acces to your code 3.Hovering above pi signs will show new buttons: a. PL/SQL of the block b. Trigger of the block c. RASD editor for the element or other links...
-
Debug mode (π) 1.Enter debug mode by clicking on small pi sign at programs version. The page will refresh and pi sign will be shown at every element. 2.Hover over topmost pi sign to open textfield. Copy link of your form (RASD development link), paste it in textfield and click submit. In program you will se many pi chars. From all you can acces to your code 3.Hovering above pi signs will show new buttons: a. PL/SQL of the block b. Trigger of the block c. RASD editor for the element If you click for...
-
Debug mode (π) 1.Enter debug mode by clicking on small pi sign at programs version. The page will refresh and pi sign will be shown at every element. 2.Hover over topmost pi sign to open textfield. Copy link of your form, paste it in textfield and click submit. Hovering above pi signs will show new buttons: a. PL/SQL of the block b. Trigger of the block c. RASD editor for the element
-
Use of Global Variables - GV is not very common. When you check field for GV means that every post of this field will have inital value from submit - inital action. field - value can change over the process field#GV - value is set at submit and it is not changed With that you can check your current value of field with submitted value any time in the process (in select, commit, ...) 1.GV checkbox on field can make field value as a global variable making it accessible from other forms. 2.How to use...
-
Example usage of GV variable. 1.GV checkbox on field can make field value as a global variable making it accessible from other forms. 2.How to use global variable set on 'BLOK3' and field 'TEST': 3.Example: This code makes 'BLOK2TEST' show error if you change value. You have to declare another variable('TEST') and catch exception because global variable is not initialized yet. If setting Rows in BLOCK is set 0 meands that the list is dynamic. Because of taht you have to use this code: DECLARE TEST...
-
To perform a form submit or button action with the Enter key, use JavaScript: $(function() { var fields = $("#*BLOK1*_DIV .rasdTextC, .rasdTextD"); $(fields).each( function() { this.addEventListener("keypress", function(event) { if (event.key === "Enter") { event.preventDefault(); document.getElementById("*BLOK1POLJE2_1_RASD*").click(); } }); }); }); This example clicks button 'BLOK1POLJE2_1_RASD' when Enter is pressed in any field inside 'BLOK1' that is type '.rasdTextC' or 'rasdTestD' (if you want...
-
1.'VS' checkbox will open new editable values for the FIELD in the in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected field. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. #SET.visible true/false #SET.disabled true/false #SET.readonly true/false #SET.required true/false #SET.error string #SET.info string #SET.custom string - attributes of element like title="RASD" 4.Example: Show info 'Enter valid number!' IF NOT...
-
RASD shortcuts Shortcuts in all pages CTRL+S = SAVE CTRL+Y = Compile Shortcuts in code windows(Triggers – Procedures, CSS, JS source) CTRL+SPACE = Variable list CTRL+F = Search CTRL+I = Fold open CRTL+U = Fold close ALT+G = Jump to line F11 = Maximize window Additional shortcut in SQL client window CTRL+ALT = get DML code of your objects Thanks to Pavel who prepare this topic.
-
1.Create and configure newLOV in "LOV in Links" page. 2.Create new LINK or TEXT field with this LOV. 3.Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. 4.Create another LINK with 'Link to form(F)'. 5.Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. 6.Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Pavel...
-
To perform a form submit or button action with the Enter key, use JavaScript: $(function() { var fields = $("#*BLOK1*_DIV .rasdTextC, .rasdTextD"); $(fields).each( function() { this.addEventListener("keypress", function(event) { if (event.key === "Enter") { event.preventDefault(); document.getElementById("*BLOK1POLJE2_1_RASD*").click(); } }); }); }); This example clicks button 'BLOK1POLJE2_1_RASD' when Enter is pressed in any field inside 'BLOK1' that is type '.rasdTextC' or 'rasdTestD' (if you want...
-
To perform a form submit or button action with the Enter key, use JavaScript: $(function() { var fields = $("#*BLOK1*_DIV .rasdTextC, .rasdTextD"); $(fields).each( function() { this.addEventListener("keypress", function(event) { if (event.key === "Enter") { event.preventDefault(); document.getElementById("*BLOK1POLJE2_1_RASD*").click(); } }); }); }); This example clicks button 'BLOK1POLJE2_1_RASD' when Enter is pressed in any field inside 'BLOK1' that is type '.rasdTextC' or 'rasdTestD' (if you want...
-
1.'VS' checkbox will open new editable values for the FIELD in the in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected field. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. #SET.visible true/false #SET.disabled true/false #SET.readonly true/false #SET.required true/false #SET.error string #SET.info string #SET.custom string - attributes of element like title="RASD" 4.Example: Show info 'Enter valid number!' IF NOT...
-
1.'VS' checkbox will open new editable values fort his block in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected block. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. #SET.visible true/false #SET.disabled true/false #SET.readonly true/false #SET.required true/false #SET.error string #SET.info string #SET.custom string - attributes of element like title="RASD" 4.Example: Show info 'Enter valid number!' IF NOT REGEXP_LIKE(BLOK3TEST,...
-
1.'VS' checkbox will open new editable values fort his block in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected block. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. #SET.visible true/false #SET.disabled true/false #SET.readonly true/false #SET.required true/false #SET.error string #SET.info string **#SET.custom string - attributes of element like title="RASD" 4.Example: Show info 'Enter valid number!' IF NOT REGEXP_LIKE(BLOK3TEST,...
-
1.'VS' checkbox will open new editable values fort his block in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected block. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. #SET.visible true/false #SET.disabled true/false #SET.readonly true/false #SET.required true/false #SET.error string #SET.info string *#SET.custom string - attributes of element like title="RASD" 4.Example: Show info 'Enter valid number!' IF NOT REGEXP_LIKE(BLOK3TEST,...
-
1.'VS' checkbox will open new editable values fort his block in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected block. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. #SET.visible true/false #SET.disabled true/false #SET.readonly true/false #SET.required true/false #SET.error string #SET.info string *#SET.custom sring - attributes of element like title="RASD" 4.Example: Show info 'Enter valid number!' IF NOT REGEXP_LIKE(BLOK3TEST,...
-
1.'VS' checkbox will open new editable values fort his block in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected block. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. 4.Example: Show info 'Enter valid number!' IF NOT REGEXP_LIKE(BLOK3TEST, '^\d+(\.\d+)?$') THEN BLOK3TEST#SET.info := 'Enter valid number!'; END IF;
-
1.'VS' checkbox will open new editable values fort his block in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected block. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. 4.Example: Show info 'Enter valid number!' IF NOT REGEXP_LIKE(BLOK3TEST, '^\d+(\.\d+)?$') THEN BLOK3TEST#SET.info := 'Enter valid number!'; END IF;
-
1.'VS' checkbox will open new editable values fort his block in 'Triggers - Procedures' such as visible, disabled, readonly… These functions can be used to modify selected block. 2.Set 'VS' value to true. 3.Use SET functions in 'Triggers - Procedures'. 4.Example: Show info 'Enter valid number!' IF NOT REGEXP_LIKE(BLOK3TEST, '^\d+(\.\d+)?$') THEN BLOK3TEST#SET.info := 'Enter valid number!'; END IF;
-
RASD shortcuts Shortcuts in all pages CTRL+S = SAVE CTRL+Y = Compile Shortcuts in code windows(Triggers – Procedures, CSS, JS source) CTRL+SPACE = Variable list CTRL+F = Search CTRL+I = Fold open CRTL+U = Fold close ALT+G = Jump to line F11 = Maximize window Additional shortcut in SQL client window CTRL+ALT = get DML code of your objects Thanks to Paule who prepare this topic.
-
RASD shortcuts Shortcuts in all pages CTRL+S = SAVE CTRL+Y = Compile Shortcuts in code windows(Triggers – Procedures, CSS, JS source) CTRL+SPACE = Variable list CTRL+F = Search CTRL+I = Fold open CRTL+Y = Fold close ALT+G = Jump to line F11 = Maximize window Additional shortcut in SQL client window CTRL+ALT = get DML code of your objects Thanks to Paule who prepare this topic.
-
RASD shortcuts Shortcuts in all pages CTRL+S = SAVE CTRL+Y = Compile Shortcuts in code windows(Triggers – Procedures, CSS, JS source) CTRL+SPACE = Variable list CTRL+F = Search CTRL+I = Fold open CRTL+Y = Fold close ALT+G = Jump to line F11 = Maximize window Additional shortcut in SQL client window CTRL+ALT = get DML code of your objects Thanks to Paule who prepare this topic.
-
RASD shortcuts Shortcuts in all pages CTRL+S = SAVE CTRL+Y = Compile Shortcuts in code windows(Triggers – Procedures, CSS, JS source) CTRL+SPACE = Variable list CTRL+F = Search CTRL+I = Fold open CRTL+Y = Fold close ALT+G = Jump to line F11 = Maximize window Additional shortcut in SQL client window CTRL+ALT = get DML code of your objects Thanks to Paule who prepare this topic.
-
RASD shortcuts CTRL+S = SAVE CTRL+Y = Compile Shortcuts in code windows(Triggers – Procedures, CSS, JS source) a. CTRL+SPACE = Variable list b. CTRL+F = Search c. CTRL+I = Fold open d. CRTL+Y = Fold close e. ALT+G = Jump to line f. F11 = Maximize window
-
1.Create and configure newLOV in "LOV in Links" page. 2.Create new LINK or TEXT field with this LOV. 3.Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. 4.Create another LINK with 'Link to form(F)'. 5.Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. 6.Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule...
-
Create and configure newLOV in "LOV in Links" page. Create new LINK or TEXT field with this LOV. Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. Create another LINK with 'Link to form(F)'. Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule who prepare...
-
Create and configure newLOV in "LOV in Links" page. Create new LINK or TEXT field with this LOV. Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. Create another LINK with 'Link to form(F)'. Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule who prepare...
-
Create and configure newLOV in "LOV in Links" page. Create new LINK or TEXT field with this LOV. Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. Create another LINK with 'Link to form(F)'. Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule who prepare...
-
Create and configure newLOV in "LOV in Links" page. Create new LINK or TEXT field with this LOV. Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. Create another LINK with 'Link to form(F)'. Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule who prepare...
-
Create and configure newLOV in "LOV in Links" page. Create new LINK or TEXT field with this LOV. Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. Create another LINK with 'Link to form(F)'. Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule who prepare...
-
Create and configure newLOV in "LOV in Links" page. Create new LINK or TEXT field with this LOV. Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. Create another LINK with 'Link to form(F)'. Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule who prepare...
-
Create and configure newLOV in "LOV in Links" page. Create new LINK or TEXT field with this LOV. Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. Create another LINK with 'Link to form(F)'. Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule who prepare...
-
Create and configure newLOV in "LOV in Links" page. Create new LINK or TEXT field with this LOV. Now LOV exists but it doesn't do anything. Go to the 'Testing' page and copy HTML link of the LOV you want to use under LOV's section. Create another LINK with 'Link to form(F)'. Paste the copied link from before in 'link' field and replace 'TEST' with '#THIS_FORM#'. Don't forget to change how to open form. Set to new window. Update LOV/link on LINK or TEXT fieldt to new LINK. Thanks to Paule who prepare...
-
Anonymous posted a comment on discussion Hints and Tips using RASD
For better understanding I would add a comment if (cMF()== false) { alert(''Field label is mandatory!"); }
-
Welcome
-
Welcome
-
Welcome
-
Welcome
-
Welcome
1 >