Widget Initialization Support 

Framework supports initializing the required tables, named queries when the widget is added. Widget developer must make sure he will add the required information to the setup_library.sql and setup_library_mysql.sql.

Here is an example:

Example for UserEditableWidget in setup_library.sql, after inserting to LibWidgetImport.

insert into LibWidgetInit VALUES (@INSERTED_ID, 'AppliWidget.UserEditableText.Init1', 'create table AppliWidget_UserEditableText(content text);', 'INITQUERY');
insert into LibWidgetInit VALUES (@INSERTED_ID, 'AppliWidget.UserEditableText.Init2', 'drop table AppliWidget_SomeTable; create table 
 AppliWidget_UserEditableText2(content text);', 'INITQUERY');
insert into LibWidgetInit VALUES (@INSERTED_ID, 'AppliWidget.UserEditableText.NQ1', 'select * from AppliWidget_UserEditableText;', 'SQLQUERY');
insert into LibWidgetInit VALUES (@INSERTED_ID, 'AppliWidget.UserEditableText.NQ2', 'select * from AppliWidget_UserEditableText;', 'JYTHONQUERY');
insert into LibWidgetInit VALUES (@INSERTED_ID, 'AppliWidget.UserEditableText.DS1', 'select * from AppliWidget_UserEditableText;', 'DATASOURCE_SQLQUERY');

When UserEditableWidget is added,

• AppliWidget.UserEditableText.Init1 is executed as sql script (and will be added as a part of application initialization script).
• AppliWidget.UserEditableText.Init2 is executed as sql script (and will be added as a part of application initialization script) but drop statement is not executed since AppliWidget_SomeTable was not created in same script.
• AppliWidget.UserEditableText.NQ1 is created as SQL Named Query and is added to the application.
• AppliWidget.UserEditableText.NQ2 is created as Jython Named Query and is added to the application.
• AppliWidget.UserEditableText.DS datasource will be created with underlying AppliWidget.UserEditableText.DS named query as well.

VALID QUERY TYPES

• INITQUERY: Initialization query should be specified with this type.
• SQLQUERY: To create SQL type named query.
• JYTHONQUERY: To create Jython type named query.
• JAVASCRIPTQUERY: To create Javascript type named query.
• DATASOURCE_SQLQUERY: To create SQL type datasource.
• DATASOURCE_JYTHONQUERY: To create Jython type datasource.
• DATASOURCE_JAVASCRIPTQUERY: To create Javascript type datasource.

Specifying ScriptValue

You can directly specify the script value in the insert statement or give reference to the sql file.

Use file:widgetinit/<script_filename> if you are specifying script value as a reference to the sql file.

Here <script_filename> will be looked in the widgetinit directory within framework sql directory during widget initialization.

insert into LibWidgetInit VALUES (@INSERTED_ID, 'AppliWidget.UserEditableText.Init3', 'file:widgetinit/usereditable.init3.sql', 'INITQUERY');
insert into LibWidgetInit VALUES (@INSERTED_ID, 'AppliWidget.UserEditableText.DS2', 'file:widgetinit/usereditable.ds2.sql', 'DATASOURCE_SQLQUERY');

NOTE: All table created for widget will be present under the application schema of developer database.

SUGGESTION:

• Make sure you use Proper names for the entries like, AppliWidget.<WidgetName>.<ScriptPurpose>
• Each widget should make sure creates table whose name are unique across widgets like, AppliWidget_<WidgetName><TableName>
• If you create files in widgetinit directory please name the file like, <WidgetName>.<ScriptPurpose>.sql or create the files in widgetinit/<WigdetName> subdirectory. This is to make sure to easily identify widget script files in widgetinit directory.