Support > Repository > Screen function > Screen transition (5) Screen transition parameters Summary
ja | en

It summarizes the parameters at the time of screen transition.

Application screen event name command Description
Registration screen New BeginInsert Open the new registration screen.
Registration screen Send DoInsert Perform registration processing.(Form data will be sent and data will be registered.)
Update screen Update BeginUpdate Open the update screen.
Update screen Send DoUpdate Perform update processing.(The form data will be sent and the data will be updated.)
Registration/update screen Add AddItem Add repeating item or repeating container item.
Registration/update screen Remove RemoveItem Delete repeating item or repeating container item.
Registration/update screen MoveUp MoveUpItem Move the position of the target repetition item or repeat container item one position upward.
Registration/update screen MoveDown MoveDownItem Move the target repetition item or repeat container item down one position.
Registration/update screen Sort DoSort Rearrange the target repeating item or repeating container item.
Registration/update screen Zipcode Zipcode We will obtain an address from the zip code.
Registration/update screen FileUpload FileUpload Send the file.
Registration/update screen Cancel Cancel Cancel registration/update processing.
Registration/update screen Confirm Confirm Move to confirmation screen.
Registration/update screen Clear / AllClear AsIs After deleting the value, redraw the screen.
Registration/update screen GetXml GetXml We exchange data with Ajax.
Search screen Reset Search Resets the current search condition and performs search processing using external parameters.It is effective when passing parameters from outside.
Search screen Search Search Use the search condition that was set first.For this reason, the second and subsequent external parameters are not set.This is a screen transition that goes back and forth between the search screen and the list display screen and is an event to hold search conditions.
Search screen Search_Condition Search It is the same as Search, but if there is no parameter, it is treated as an empty search condition was specified.
List display screen Show Forward Transit to detail screen.
List display screen Update Forward Transit to update screen.
List display screen Copy Forward Transit to copy registration screen.
List display screen SizePerChange ChangeSizePerPage Change the number of displayed items.
List display screen Sort DoSort Sort the list display data.
List display screen Next Next The following N of the list display data is displayed.
List display screen Prev Prev Displays the previous N items of the list display data.
List display screen First First The first N items of the list display data are displayed.
List display screen Last Last Displays the last N items of the list display data.
List display screen Jump Jump Perform pagination processing with list display data.
List display screen DeleteAll DoDeleteAll Performs batch deletion processing of the data selected in the list display.
List display screen UpdateAll DoUpdateAll Performs batch update processing of data selected in list display.
Detail screen Show DoShow Open the details screen.[Notes on returning to your own screen ...]
Delete screen Send DoDelete Delete the data.
Register/Update/Detailed screen Print DoPrint We will process the form processing.
List display screen PrintAll DoPrintAll Performs form report processing of list display data.
List update screen ULInsert UpdateListInsert Create new data.It is reflected only in the editing screen.
List update screen ULCopy UpdateListCopy Copy data is registered.It is reflected only in the editing screen.
List update screen ULExecute UpdateListExecute Update the data on the edit screen.
List update screen ULCancel UpdateListCancel Discard data on the edit screen.
Download screen Reset InputCondition Open the download screen (search screen).R7.10.2
Upload update screen Status ShowStatus Open the upload update operation status screen.R7.11
(all) (Event name decided by developer) UserDefined Send when original button is pressed.
Event names are case sensitive.Please input correctly.

Customized developer information

For Java and (server side) JavaSciprt, the event name can be obtained by p.action.Internal command information can be obtained with p.cmd.

Basic rules

If the item to be listed on the right side of the parameter (item specified by $ {...}) is a model reference, the value is passed in the next rule.

  • In case of model reference, pass the ID part.
  • In case of reference linkage, pass the content part.

To change this rule, please specify #id or #content after the item name. For example, if you want to pass an ID value for the reference linkage item companyname, write $ {companyname # id}.

When the destination model is a compound key

The transition source is model 1 and the transition destination is model 2.Model2 is a compound key, and it is pkey1 and pkey2 respectively.

In this case, two items (model1, item2) held by model1 are passed to pkey1 and pkey2 respectively.Please match the type of item you pass on to the side you receive.

When the model reference item of the transition destination model is a compound key

The transition source is model 1 and the transition destination is model 2.Item item 3 in model 2 is a model reference item and reference destination model is model 3.Model3 is a compound key, and it is pkey1, pkey2 respectively.

Figure 1 Configuration of sample

Parameters to be described by buttons prepared for model 1

If the primary key of the referenced model is a compound key, describe the additional parameters as follows.

Item name = $ {primary key 1} $ SEP $$ {primary key 2}

We write the primary key item name with $ {...}, but we add $ SEP $ between the key concatenation character string.

item3=${item1}$SEP$${item2}
Figure 2 Parameters to pass to model 2

Script for model 2

In model 2, which is the receiving side, it analyzes and sets the value by script instead of initial value expression.The timing is "registration (initial data creation)".

var item3 = p.request.getParameter("item3");
if (item3 != null) {
    var ss = item3.split("$SEP$");
    /*
    for (var i in ss) {
        stdout.println(i+"="+ss[i]);
    }
    */
    model2.item3Pkey1 = ss[0];
    model2.item3Pkey2 = ss[1];
}
Figure 3 Script to be prepared for model 2

P.request is the request object managed by the Java application server.Using the getParameter method you can receive the parameters specified in Figure 2.

Calling split function with $ SEP $ as delimiter prepares an array.Set individual values ​​to the elements of model 2.

Here, item 2 is provided with item "item 3", but internally it is managed as follows.

Item name _ Primary key of the referenced model (first) Item name _ Primary key of the referenced model (second)

That is, in model 2, two items "item 3 _ pkey 1" and "item 3 _ pkey 2" are internally held.In server side JavaScript, it is written as "item 3 Pkey 1", "item 3 Pkey 2", respectively, by the Camel rule.(Pkey 'P' is in uppercase letters.)

When the model reference item of the transition source model is a compound key R7.10.2

The transition source is model 1 and the transition destination is model 2.The item item 1 in model 1 is the model reference item, and the reference destination model is model 3.Model3 is a compound key, and it is pkey1, pkey2 respectively.

If the primary key of the referenced model is a compound key, describe the additional parameters as follows.

Item name = $ {item name # id} $ SEP $$ {item name # id 2}

We describe the item name with $ {...}, but add the suffix # id, # id 2, ... to the back of the item name.The primary keys pkey 1 and pkey 2 of model 3 are passed in correspondence with the suffix digits, respectively.

When passing to the item field of the transition destination model model 2, it becomes as follows.

item=${item1#id}$SEP$${item1#id2}

In model 2 which is the receiving side please divide delimiter $ SEP $ using script.(Since it is explained in "When model reference item of transition destination model is compound key", it is omitted.)

In case of check box R7.10.2

For check box type items, the value (ID part of the referenced model) is passed by comma break.In the transition destination model, please use scripts to store values ​​after dividing them.Here is an example of a script that stores the value in the item field of the transition destination model model 2 (this also assumes check box type).

var item = p.request.getParameter("checkbox");
if (item !== null) {
  var array = item.split(",");
  var i;
  for (i=0; i<array.length; i++) {
    /*stdout.println("i="+i+","+array[i]);*/
    if (array[i] !== '') {
      model2.addItem(parseInt(array[i]));/*model2のitemはチェックボックス型*/
    }
  }
}

Change delimiter

If you want to use a character other than a comma as a delimiter, write the parameter as follows.

item=${checkbox;|}

Specify a delimiter after the semicolon.Please remodel the receiving JavaScript accordingly.

Restriction: The following characters can not be used for this delimiter specification function.

";" "(" ")" "" ""] "&" "=" ">" "" "" $ "