I will explain how to register and delete models using WagbyDesigner.
Select "Model" from the WagbyDesigner menu.There are two tabs "user" and "system", but the model to be newly developed is stored in the "user" tab.
As shown in Figure 1, select "New model" from the gear icon.As shown in Figure 2, the definition screen for the new model opens.
"Model name" is the name displayed on the screen (and menu).
"Model ID" is used as the database table name and the identifier in the generated source code.
You can not use Japanese (hiragana, katakana, Chinese numerals) for model ID.Please use alphanumeric characters.
Changes to the model name and model ID are immediately reflected in the repository.At the timing of the build, the source code is regenerated using the changed name.
Display the model list from the "Model" menu.Check the model you want to delete.
Select "Delete" from the gear icon.
A confirmation dialog will be displayed. Click the "OK" button.
The model has been deleted.
You can specify build target models individually.Please specify a checkbox in the Build column.All models are targeted for build in the standard.
A table (for relational database) corresponding to the model is generated.
More precisely, DDL (create table, drop table) for the database is automatically generated for the model definition.You can use this DDL to create and delete tables on the database.[More ...]
If there are other models referring to this model, a warning dialog will be displayed before the change.When OK is pressed, the model ID after substitution is substituted for all referenced models.(The items in the formula are also the same.)
If there are other models referring to this model, a warning dialog will be displayed before deleting.If you refer to this model in the calculation formula (item in), it is included in the warning target.
If you press OK, the model will be deleted, but for other models indicated as affected, developers should manually correct them appropriately.
The model included in the "System" tab is used by Wagby's management function.This is called "system model".On the other hand, the one created by the developer is called "user model".
|Model name||Model ID||Use|
|Result of batch job execution||jfcbatchjob_execution||It is effective when Spring Batch is used.The execution result of the job is stored.The registration process is done by the Spring Batch framework.It is not assumed (by Spring Batch) to update or delete it.It becomes exclusive for viewing during operation.|
|Batch job execution details||jfcbatchjob_execution_context|
|Batch job execution parameters||jfcbatchjob_execution_params|
|Batch job instance||jfcbatchjob_instance|
|Batch step execution||jfcbatchjob_execution|
|Batch step execution details||jfcbatchjob_execution_context|
|Common Settings Preferences||jfccspreferenceitem||List display grid Used when common setting is used by multiple users.Data is registered at the timing when common settings are created.It becomes exclusive for viewing during operation.When updating or deleting, please operate the database directly.|
|Flow pattern||jfcflow_setting||It is used when using workflow.Stores the flow pattern.You can also add your own flow patterns during operation.|
|Graph settings||jfcgraphsetting||You can save the settings of the graph display and use it in common by other users.Data is registered at the timing when common settings are created.It becomes exclusive for viewing during operation.When updating or deleting, please operate the database directly.|
|Job master||jfcjob||Apart from Spring Batch, Wagby prepares a job by time designation.It stores the job list.Its contents are prepared beforehand when installing Wagby.|
|Job sched||jfcjobschedule||The schedule for executing the job prepared by jfcjob is stored.The operator can add and edit the job schedule.|
|License file||jfclicenseholder||Information on the production operation license file is stored.Usually, it holds one record.|
|mail template||jfcmailtemplate||The mail transmission settings are saved.Records are added as much as you set.|
|Definition model||jfcmodel||It holds the name of the predefined system model and user model and the amount of data.It is used as browsing only, not as a model operated by developers and operators.|
|Flow Participant Setting||jfcparticipant_setting||It is used when using workflow.Stores information about users or groups participating in the flow.It can be arbitrarily added during operation.|
|Flow participant container||jfcparticipant_setting_node|
|Portal||jfcportal||It is used when using the portal.We keep only one record of whether to use portal or not.|
|Portlet||jfcportlet||It holds part information that can be displayed on the portal.Developers can extend and add their own portlets as well.|
|Portlet (graph color)||jfcportletGraphColor_m||It is used in graph portlet.It is fixed at installation and can not be expanded.|
|Portlet (graph type)||jfcportletGraphType_m|
|Preferences||jfcpreferenceitem||It is prepared for each user (logon account juser).Information that should hold values is stored even when logging off, such as sorting information of list display and column listing information of list display grid.Once re-logged on, it is prepared to restore the previous information.Number of registered accounts x Records are added by the number of information (key-value pair) to keep.Add, edit, and delete records are automatically done inside the system.|
|Delegate setting||jfcproxy_setting||It is used when using workflow.A record is added when proxy approval setting is done.|
|Form template||jfcreporttemplate||It is used when using Excel/PDF form.Records are added as many as you set.|
|Start flow state||jfcstartworkstate||It is used when using workflow.It is management information to know who is currently waiting for approval for the workflow that I applied.Records are prepared by the system.Even if the workflow ends, this record is kept in the database as a record, so the data volume will increase with operation.It is possible for the administrator to delete the old data manually.(Deleted data will be excluded from search.)|
|Pending flow status||jfcsuspendworkstate||It is used when using workflow.It is management information to investigate the workflow that you should approve.Records are prepared by the system.Even if the workflow ends, this record is kept in the database as a record, so the data volume will increase with operation.It is possible for the administrator to delete the old data manually.(Deleted data will be excluded from search.)|
|Workflow setting||jfcworkflow_setting||It is used when using workflow.We link the workflow definition model with the workflow definition model.Records are created as many times as you set up.|
|Flow Event||jfcworkstate||It is used when using workflow.Record events for workflow (approval, remand, decision, etc.).Records are prepared by the system.Even if the workflow ends, this record is kept in the database as a record, so the data volume will increase with operation.It is possible for the administrator to delete the old data manually.(Deleted data will be excluded from search.)|
|group||jgroup||Group information to be used inside the system.A record is added as many as the number of registered groups.|
|holiday||jholiday||It is holiday information used inside the system.Initial value is Japan holiday information "JapanHolidays.ics" is registered.Optional holidays can be additionally registered.|
|Notice||jnews||You can display announcements to users on the portal screen.Records will be added when using Notification portlet.|
|Principal||jprincipal||It is prepared for each user (logon account juser).Wagby's authorization function is realized.It is managed automatically within the system according to account registration and editing.|
|account||juser||It is a user (logon account).A record is prepared for the number of registered accounts.|
|order||seq||Holds the order (primary key) for each model.It is not prepared when the database provides sequence (ordering) service, such as Oracle or PostgreSQL.It is prepared only when you use a database that does not provide sequence such as MySQL.The system will manage it automatically.|
The system model has the following restrictions.
The following models can expand model items.
|Model name||Model ID||Use|
|group||jgroup||Used for group authority management.It is linked with account (juser).|
|Notice||jnews||A model that can notify users.|
Models other than those described here can not be changed.Please use it at the time of installation. In Wagby's version upgrade, the latest model is applied when applying the migration tool (models belonging to "system" other than the model above).
There is no theoretical limit.
By increasing the memory used by WagbyDesigner, you can build applications that contain many models.
Moreover, by increasing the memory used by the application built by Wagby, it is possible to operate a large-scale application.