When the items included in the expression of the button display control internally use the FLOWSTATUS function, it becomes a run-time error.It occurs from R 7.4.2.
After installing Wagby, if you make difference build by changing model ID and item ID, an error occurs.It occurs from R 7.4.
In the referential container's reference linkage, if the reference linkage items are all non-DB-saved and contain unique input items, a malfunction (not linked with reference)
On the search list screen, when the original button is placed on the list display screen (line by line) and the event name is set to Reset, the reset button of the search screen is ignored.
When setting options to narrow down based on the relationship between reference models, typing errors may occur in the p2p method of the generated helper class.
When setting options to narrow down based on the relationship between the reference models, the item as the narrowing candidate may be erroneously determined.If the model including the narrowing source item includes another narrowing setting and the primary key of the reference destination model is the same name, it is erroneously judged.
Referencing items that refer to a compound key model When linked, an error occurs at automatic generation.
Printing title is not copied in batch output of detailed form (1 data 1 Excel sheet format).
When IE is used, another button can not be pressed after the download button on the search screen is pressed.
"Retain value" does not work with input control by value of other items when using IE.
Using an automatic calculation formula to specify the output control style sometimes results in a build error.
If the environment variable ANT_HOME is not set,CreateWagbyappZip commandFail to execute.(Make it work even when ANT_HOME is not set)
When it is judged in the list box of the list updating screen that the screen redrawing is necessary when the value is changed, an error occurs in the form reference in the onChange event and other buttons on the screen can not be pressed.
When the date/time type item is searched for, the input search condition becomes empty after the screen redrawn.
In referential linkage to recurring containers, `-1 'is displayed if the reference destination is a numeric type item and no value is set.
If you perform an operation outside the authority, a general error screen is displayed instead of a security error screen.
When browsing authority is set for items in the repeating container, the header row is not output at the time of downloading, the data rows are outputted, and the columns may shift.
In the tab display control, the reference interlock in the hidden tab does not work.
You can not select if single quotes are included in the data selected in the sub window search.
In the collective form output, the formula using the value of the child model is not reflected.
If you use JasperReport (detailed form) together with the output of collective form, build error.
The screen scroll position is not maintained after pressing the up/down movement button of the repeating container.
The screen scroll position is not maintained after pressing the sort button of the repeating container.
When using JasperReport, a runtime error occurs in a detailed form containing multiple child models.
When using the maintenance mode, a black screen is displayed when a general user logs on.
When an original button is prepared on the master model detail screen and the display control is performed in relation to the foreign key parent-child model relationship, the expression of the button display control is also applied to the child model list.
When the screen of the search condition part is redrawn with setting to display the search screen and the list display at the same time, even when the list display result has not been output so far, it is always displayed at the timing of redrawing.
In the compound key model, part of the primary key refers to the model, and the model of the reference destination is also a compound key, and the deletion or update function of the list update does not work.
In the compound key model, a part of the primary key refers to the model, and the model of the reference destination is also a compound key, and the batch processing of the list display screen does not work.
In the compound key model, a part of the primary key is model referenced, and the referenced model is also configured as a compound key, and sorting of repeated containers is a run-time error.
The value of the item of the reference interlocking (self model saving) linked with another model reference item (list box) which enabled "display only the top of the option" may not be appropriately solved.
On the list update screen, when the primary key is a list box, radio, numeric value, it is an interface that can change the value (actually an update error occurs).
When updating parent data without child data in parent-child model simultaneous update, a run-time error occurs.
Build error when including time type item in one of compound key.
If data contains a control code that can not be used in XML, a run-time error occurs on the detail display screen.Check out these characters and remove them.
When opening the search screen, a run-time error (Null Pointer Exception) may occur during CSS processing of the search item.
With the mail reception function, change some of the logs output by DEBUG so far to WARN.
When adding breadcrumbs IndexOutOfBoundsException may occur.
If the file type item is set as a full text search target, the width of the "full text search keyword" input field on the search screen becomes narrower.
Self model saving of reference linked items is not subject to full-text search.
An empty log is output even when the update button is pressed without changing any value with the change history function.
Opening the same update screen on another tab of the browser while updating on the update screen will display the screen with the input field empty.The input value disappears when updating is done here.As a countermeasure against this, if there is no input, it is made to transition to the error screen.
In the foreign key parent-child model, if you set "Do not allow update processing" setting when updating list of child models, reference linked items are not resolved.
In IE, even if the label width of the list display screen is fixed, it is not reflected.In IE 9/10/11, if even one label width fixation is specified in the list display item, add table-layout: fixed designation.(IE only)
The "Do not fold value" setting in IE 9 does not work.
The setting of "Do not fold" labels/values does not work when Chrome performs settings that do not wrap around the width at the same time.
In the list display screen, if it is a text area designation in a repeating item or a repeating container item, and it is label display, it is surrounded by a span tag rather than a pre tag.
[Specification change] When setting the variable length designation of the repeated container in the detailed form, the cell join is shifted on the line in the form output of data in which no repeating containers are registered.Because of this correspondence, even if there are 0 containers, one empty data line will be displayed in the container.This causes cell coupling to operate.
Immediately after installing Wagby, if you make difference build by changing model ID or item ID, an error may occur.(Fully building will resolve it.)
Even if you change the item name/item ID of the model, the item item choice of item setting of the view is not updated.
In real-time check of design information, selecting "Model reference (narrowing down)> Display only at the beginning of choices" results in an error even though it is not stored in the database.
If "*" is included in the default selection tab ID, the specified tab does not become selected state when displaying the screen.
Changing the display character size of the browser makes it impossible to press the backup button in the operation tab.
In the case of the submodel, setting of the physical table can not be entered.
In the "Screen> Script" column, what was last displayed may remain on the screen.
> Show text area as label "has been supported.After migration from the old repository, this setting is "○" as standard.