Tutorial(Advance)

The following functions are used when creating a man-hour management application.

Even if the user does not specify a value, the value is automatically assigned according to a set rule. Here, the project ID is set to automatic incrementing in the format of “Pxxx”.

The value is automatically set according to the specified logic. Here, the total value of man-hours (planned) is set.

Specified Logic will be called when the event of creating/updating Entity data has happened. Here, the logic to automatically set a value to the name when creating/updating Entity data is called.

Perform input check of Property. Here, an error is displayed when a value other than 0 to 24 is entered.

If you turn on Audit Log, you can record the operation log of the entity.

Nest tables to display Reference information.

Displays reference information of multiple stages in a drop-down.

You can specify the section name and the number of columns. Here, the section name is “total man-hours” and the number of columns is two.

You can incorporate your original template into the screen.

Entity information with Date type or DateTime type Property can be displayed on the calendar using the calendar function.

The operative privilege for Entity can be changed according to the user. The screen item display also changes for users who can browse, register, update, and delete and users who can only browse.

You can create an email template and send an email from the iPLAss screen via a workflow.

You can display graphs and tables.

To begin with, please register the metadata of the entity. Create an Entity with the following name from AdminConsole.

Add the following Property to each Entity.
When referring to an item whose Type is Reference, the Entity must already be created. After setting the Entity, add a Reference item again.

This completes the preparation work.

Now, let’s register the master data from the GEM edit screen according to the flow of Business Flow. New registration with the following contents in the project master entity.

Even if you want to specify a property name according to a certain logics such as P001, P002, …​, as for the implementation of 'ID', if in the situation of the above example, you will have to enter the value manually in the String type. Manual input is not only cumbersome but can also leads to input errors. In such cases, it is convenient to use the AutoNumber function. The AutoNumber function automatically assigns values ​​according to a certain grammar.

Let’s actually customize and use the AutoNumber function.

For details of AutoNumber, please refer to AutoNumber.

Display the project ID setting screen and change the settings.

Fixed digits can specify how many digits a value is displayed. Since it is 3 digits here, 001, 002, 003, …​ is displayed. You can also specify the format for displaying values. Here, P $ {nextVal()} is specified, so P001, P002, P003,… is assigned. What about other notations? Press the ? button to confirm.

When the change is complete, save the Entity.

Similarly, change the task ID setting as follows.

When the change is complete, save the Entity.

This completes the AutoNumber setting.

Add data to the project master entity for confirmation. Create New from the search screen.

Enter a name and description and register.

You can see that the values ​​are automatically assigned according to the format specified for the project ID.

Next, register the following data in the version master Entity.

When registering the above project name, you manually entered the name of the project master entity that the version master entity references. In this way, if you want to set the value obtained based on other Property values, it is convenient to use the Expression function. With the Expression function, values ​​can be obtained using four arithmetic expressions or EQL (iPLAss version SQL).
See the EQL Reference for more information on EQL.

Let’s actually add customization and use Expression.

For details of Expression function, please refer to Expression.

Change the project name setting as follows.

The value is acquired according to the four arithmetic expressions and EQL described in the expression and set as the Property value. Here, EQL is written to obtain the value of the name of the project master.

When the change is complete, save the Entity.

Similarly, change the project version setting as follows.

[1]:Project version of task master entity

When the change is complete, save the Entity.

Similarly, change the settings for total man-hour (planned) [h] and total man-hour (actual) [h] as follows.

[2]: Get the total value of man-hours (planned) [h] of today’s task Entity

[3]: Get the total value of man-hours (actual) [h] of today’s task Entity

When the change is complete, save the Entity.

Add data to version master entity for confirmation. New registration from the search screen.

Enter a name and description, select a project, and register.

You can see that the project name is set in the project name.

Register the following data in task master entity.

Each project version item consists of the project master name and version master name. Task master entity has version Property, and version Property also has project master entity as a reference.

Here, let’s use the EventListener function to set the project version Property with custom logic that is called when registering or updating an Entity.

Also, set EventListener to automatically set the name Property for today’s schedule entity and today’s task entity. This method can also be used in scenes where you do not want the user to enter the required property name Property directly.

For details of EventListener function, refer to EventListener.

Add EventListener. By default, EventListeners are closed, so click on the tab bar to open EventListeners.

Click the Add button to display the editing dialog. When Script is selected, the edit screen is displayed as shown below. Click the Edit button.

Display the editor for editing and enter the following script.

Click the OK button to close the dialog and save the Entity.

Similarly, add the following script to EventListener.

Get the value of name Property from task master entity and set the value to name property of today’s task entity.

When the change has completed, save the Entity.

Similarly, add the following script to EventListener.

Get the value of name Property and project name Property from version master entity, combine both and set to project version property.

When the change is complete, save the Entity.

Add data to task master entity for confirmation. Register new data from the search screen.

Enter any name and description, select a version, and submit.

You can see that the combined value of the version master name and the project name value is set in the project version.

Use Validator function when you want to check input of data to be registered in Entity was following the rule.

Here, Validator is assigned so that an error is displayed when a value other than 0 to 24 is entered in the man-hour (planned) [h] and man-hour (actual) [h] of today’s task Entity.

First, register a message when an input validation error occurs. Right-click Message in the Data Model, click「Create Message Category」from the context menu that appears, and create the message below.

Add a line and add a message item. Click the ID column to set the ID.

Click the Message column to set the message. ${min} and ${max} will contain the values ​​specified by Validator later.

Click the Save button to save the message.

Next, set Validator to Property.

Perform the following settings from the on the planned Man-hour for today’s task Entity.

An error will occurs if the entered numeric value is not within the specified range.

For Min and Max, specify the range of values ​​that can be entered. The Min and Max values ​​here are entered in ${min} and ${max} of the message created earlier. In Message section, select the message category name of the message you want to use in case of error. For this instance, we will specify tutorial/advanced/common. In Message Id, specify the message ID of the message you want to use in case of error. If you haven’t modify the given names of this tutorial, then it should be M0001. Setting the Code is optional.

Set the same for the man-hour (actual) [h] and save the Entity.

For confirmation, add data to today’s task entity. Please click new registration from the search screen.

Then set a value that will cause an input check error in the man-hour(actual)[h] and register it.

You can observe the error message which is displayed at the top of the screen. A detailed message is also displayed at the location where the input validation error occurred.

If you want to record the update history of Entity, use the AuditLog function. Here, AuditLog is set to record the update history of project master entity.

Enable save audit log in the project master entity. Check this item to record operation logs.

Open DetailLayout of project master entity and click standard load.

Standard settings according to the Entity definition are loaded. Because AuditLog is enabled, AuditLog Section is added. Click the Save button to save the screen definition.

You can also drag the audit log display parts and drop it to the desired location.

Add data to the project master entity for confirmation. New registration from the search screen.

New registration from the search screen.

Edit the created project master data.

Edit and save the contents.

Open the operation log section.

You can confirm that the operation history of entity data (changed property and value before and after change) is recorded in the operation log section.

This completes the Entity settings.

Next, we will try the configurations related to the screen displays.

The following methods can be employed to display the contents of Reference type Property on the detail screen.

Here we will deal with RefCombo and NestTable.

By default, the property information is displayed in a table format with one column on the detail screen, but the number of columns can be increased from Detail_Layout. Set to display part of Property data of today’s schedule Entity in 2 columns.

Open Detail_Layout for today’s schedule Entity. Drag and drop Default Section onto Detail Views.

The Section Setting window will appear. Specify the title and the number of columns.

Drag and drop Total man-hours(planned)[h] to the Total man-hours section. Similarly, drag and drop the total man-hours(actual)[h].

Click the Save button to save the changes. This completes the two-column display setting.

Please open the details screen of today’s schedule Entity for confirmation. You can see that the total Man Hour section is displayed in two columns.

This end the operation checks.

This section explains how to incorporate an original template. The created template can be displayed on the home screen or displayed on the menu. This section describes how to display such template on the menu.

First, create a template.

Create the following template:

Displays the created template. For Layout Action, specify gem/layout/defaultLayout (standard layout). This is because the headers and menus used in the GEM screen such as the Top screen and search list are also used in this template.

Click the Save button to save your changes.
Next, create an action to call the template.

Create the following actions:

Open the created action and add Status Result Actions.

Click the Save button to save your changes.
Next, add a menu to call the action you created. Right-click the ActionMenuItem displayed in Menu Items and select「Create Menu Item」from the context menu that appears.

Drag and drop menu items into the menu tree to add them to the menu. After adding the parts, save the settings.

For confirmation, press the home button to update the menu.  You can see that the menu of Usage has increased. You can also check that the created template is displayed by clicking this menu and opening the usage screen.

In customizing the search/detail view, we explained how to display the created template from the menu, but here we will explain how to incorporate the template into the Top screen.

There are two templates to be created: a template for displaying the Top image and a template displayed on the Top screen.

First, register the image to be used in the Top screen template. Please prepare an image(any image) to be displayed on the template in advance. Create a template according to the following:

Select and save the image file to be used on the Top screen.

Next, create an Action to call the topImg template.

Open the created action and specify the image template in Status Result Actions.

Save the action.

Continue to create a template for the Top screen.

Create the following template:

Specify the path of the action created earlier in the URL of the image in the template and save it.

Now we will add the template to the Top screen. Please open the TopView.

Select the tutorial top template that you just created.

After saving the changes by pressing the Save button, the template has been inserted into the Top screen.

For confirmation, press the Home button to update the Top screen. You can confirm that the created template is displayed.

This concludes the completion of this section.

Now we will explain how to display the calendar on the top screen.

First, create a calendar to display on the top screen.

Open the created calendar. Register the entities you want to display on the calendar. Here, we want to display the contents registered in today’s schedule Entity in the calendar, so drag and drop today’s schedule Entity from Entity Items to Target Items.

Now, we want to put in the created calendar on the Top screen. Open TopView, drag and drop from Items to the MainArea just as you would with a template.

The setting is now complete.

For confirmation, press the Home button to refresh the Top screen. You can see that the calendar is embedded in the top screen.

This concludes the completion of the operation check.

As described in role and granted authority from the tutorial (basic), the role generated during tenant creation does not have authority for the created Entity. Up to this point, there was no particular problem because it was an operation by the administrator user, but from now on, authority control is performed on the data handled by the actual user.

First, let’s customize the master data so that only supervisors can edit it, and employees can only view it.

Create a group for managers and a group for employees. This group is used as a condition for authority control. By creating a group, it is possible to assign the same role to multiple users belonging to that group.

Click the New Registration button on the search screen that appears when you select the Basic Information － Group Information menu and create the following two groups.

Provide users to ensure permissions are controlled.

For how to create an account, please refer to user registration in the tutorial (basic).

Create a role to separate security permissions. Create the following roles:

Please refer to Tutorial (Basic) for how to create a role.

Create Entity permissions to control CRUD permission control for each Entity. Select the Permission Information － Entity Permission menu to display the search screen.

Click the New Registration button and create the following Entity permissions.

Entity privilege for administrators

Entity privileges for employees

Once each input is completed, press the registration button to register each entity privilege.

Create a menu linked to each role. The current menu uses the default menu, so copy it to create the administrator menu and employee menu.

Create the following two Menus.

When input is complete, press the Save button to save. There is no need to customize each menu.

Next, create a layout for the search screen and detail screen so that each Entity screen can be used.
If the layout has not been created, the target menu will not be displayed when performing the operations described below. Open Search_Layout and Detail_layout for the Entity for which the layout has not been set in the steps up to this point, and save the settings created by Standard load.

This completes the security authority settings.

Log out of the administrator user for confirmation.

Log in with your boss account boss@advanced first.

Open the master entity search screen.

It can be confirmed that all four operations of reference, registration, update and deletion can be performed.

Log out again and log back in with the employee account member01@advanced.

Check the master entity search screen.

It can be confirmed that the only possible operation is to view details.

In this way, by performing authority control for each user (for each role), it is possible to limit the disclosure of only the minimum necessary information and prevent unnecessary operations.

Now we will try to implement the feature so that satisfying this real life situation: once the registration of the man-hours of the day is completed, you want to report to your boss. Let’s make settings so that you can report to the supervisor with shortcut to create email from templates at the Entity registration screen.

First, we need create an email template. Create the following template.

Enter the subject and message of the email to be sent.

Next, create a Workflow to use the email function. Create the following Workflow.

Please refer to Tutorial (Workflow) for detailed guide manual of Workflow.
The figure below is an image of the workflow after configuration.

Please set each item as we have been doing, setting is not required for item that are not listed.

Workflow variable. Entity data when starting the workflow is stored.

The task to send email. Set the mail template and its destination.

A task that the user performs some operation. Processing can be branched by the assigned user’s operation.

Set up rules to assign tasks to users. Here, specify the user who will be the supervisor.

Set the task result. The value set here can be performed by the user on the workflow details screen. By setting the Name value to an arrow that extends from the user task, you can control the flow progress.

Next, make settings for starting the workflow from Detail_Layout. Please set DetailScreen from DetailLayout of today’s schedule Entity.

Next, in order for the boss to confirm and approve the report, set the part that displays the task assigned from the workflow on the Top screen. Create the following TopView.

Open the created TopView and drag and drop UserTaskList.

Open the part setting screen and click UserTaskView Setting. Check all the check boxes in the Show Section Properties list and click the OK button.

Please save TopView after completion.

Roles and privileges were created in previous section, privileges are also required when using workflows.

This completes the configuration of the email function using the workflow.

For confirmation, log out and log in as an employee user (menber01@advanced). After creating today’s schedule, please send a report email from the details screen.

The workflow is launched and an email is sent to boss@test.jp.

Log in as the boss user (boss@advanced). You can see that the task is assigned. Click the edit link to display the edit screen.

Perform approval process from the edit screen.

Return to the Top screen, check the “Including after the completion” check box in the task list, and display it again. You can confirm that the process is complete.

This is the end of the workflow part.

The total man-hour schedule and actual changes are displayed in a graph. Set the aggregation according to the following flow.

Create the following aggregation:

Open Aggregation and make the following settings.

Check Display graph and Display graph on summary table.

Set day to the filter item.

Set EQL to search date, total man-hour (planned), total man-hour (actual) from today’s schedule Entity.

Add the following item from the Add button. Settings are not required for items that are not specified.

Make the following settings from the Graph Settings tab. Settings are not required for items that are not specified.

Save the settings when you are done.

Add an action to display the effort graph in the administrator group menu. Right-click the ActionMenuItem displayed in Menu Items and select「Create Menu Item」from the context menu that appears.

Add viewGraph from MenuItems to MenuTree.

Save the menu.

The setting is now complete.

To verify the result, press the Home button to update the Top screen. You can see that the time chart has been added to the menu.

Click the added menu to display the scene.

The item set in the filter item is added to the filter condition. You can also see that the data registered in today’s schedule Entity is displayed as a line graph and a aggregation table.