1. Improvements to the Field Mapping window (maintenance contract required for part of it) We have made major improvements to the Field Mapping window used to define mappings between text files, database columns and Asprova properties.

1.	When a column is added, changed, or deleted in a database connected to OLE DB, the mapping was shifted in the previous version, but is no longer shifted in this new version.	Example: The column OrderUser_aaa (right column) of the external database is mapped. If the column OrderUser_aaa is deleted in the external database, the mapping will shift one column in versions earlier than 16.2, and you will have to fix it manually. In the latest version, the deleted column will be detected and the mapping will be automatically modified, so there is no need for manual modifications.
2.	When deleting a user property in Asprova, the mapping was shifted in previous versions, but is no longer shifted in this new version.	Example: The user property aaa on Asprova is mapped. If the user property aaa is deleted, the mapping will shift in versions earlier than 16.2, and you will have to correct it manually. From this version, the mapping is automatically modified when it detects that a user property has been deleted, so there is no need for manual changes.
3.	The data types are now displayed. (Maintenance contract required.) Also, the display columns can now be customized from the right-click menu just like other tables. This will allow you to view the properties you want to see in the left and right windows. However, this cannot be saved to a style.
4.	Rows with the same data type are now easier to identify when mapping. (Maintenance contract required) If you want to forcibly map for some reason even if the data types are different, you can uncheck the “Enforce data type check” in the right-click menu of the center.	If the data type cannot be mapped, an X mark will be displayed.
5.	When the field mapping window is opened, the data type of the existing mapping is now checked. If the data type does not match, the connection line will be shown in red. (Maintenance contract required)
6.	A red warning message is now displayed when the primary key is not mapped. (Maintenance contract required)
7.	The left column can now be sorted by mapping order. Press the F3 key to sort. This will make it easier to understand the mapping. (Maintenance contract required)
8.	It is now easier to export each table in the order of its style to a text file. (Maintenance contract required)	Suppose you want to output a text file in the sequence of the “standard” style of the Order table. In the Field Mapping window, select Style from the right-click pop-up menu. Sort by style display order. After that, select a row and choose the right-click menu item “Link by selected rows”. Mapping by display order of styles can be created.
9	Auto-mapping: Improved the function of auto-mapping with “Connect by Name” in the right-click menu.	For each property definition on the left, searches the field definitions on the right using the following rules. 1. Long name that matches 2. Alias or display name that matches 3. Short name that matches Followed by: 4. Contains a long name 5. Contains an alias or display name
10	It is now possible to see on the window frame or tab if the changes are unapplied. You are less likely to forget to apply the field mapping after editing it. (Maintenance contract required)
11	When importing, exporting, and synchronizing, the system now checks for DBOIOs that have not been pressed the Apply menu. (Maintenance contract required)
12	Field definitions can now be constructed from the header information of the first line of a text file. (Maintenance contract required)	Set DBIO’s “First row is field info” to “Yes (code)” or “Yes (code and field info)” or “Yes (alias/display name and field info)”. Create the text file accordingly. Select “First row is field info” from the right-click menu. The first line is read and mapped. If “First row is field info” is set to “Yes (alias/display name)”, it will not be read.
13	In the table on the left, you can now select cells and copy strings to the clipboard. You can select multiple cells by holding down the Shift key.
14	Strings can be searched in the Find dialog. (Maintenance contract required)
15	The properties window can now be opened from the right-click menu.
16	Enhanced Undo/Redo function.

   2. DBIO export acceleration (maintenance contract required)

Export to Microsoft SQL Server (Microsoft SQL Server 2008 or later) and Oracle Database (Oracle Database 9i or later) has been accelerated.

For DBIO settings, the “SQL command type” property must be set to “Full text”. However, with this improvement, if the database meets the above requirements, “Full text” will be much faster.

The following are the test results within the same LAN network. INSERT and UPDATE processes in the database are grouped together to speed up the process. (The time difference for Microsoft SQL Server is probably due to the processing characteristics of each cMicrosoft SQL Server. )

The following are the test results when exporting from Japan to a database located in Brazil. In Ver. 16.2, the number of SQL statements sent has been reduced to 1/100. Therefore, the reduction in network traffic is likely to contribute to the higher speed.

In this test, we exported two tables at the same time, the order table and the work table, but the results show the same trend even if we do it with a single table.
 

   3. Remove message boxes related to importing, exporting, downloading and uploading DS.

A message box used to be displayed when the file to be imported could not be found when executing import, or when no objects were exported when exporting. From this version, these messages are no longer displayed. This avoids the phenomenon of a message box appearing and stopping the reschedule when the import or export command is embedded in the scheduling parameter. The same goes for the message boxes regarding DS downloads and uploads.

   4. Welcome screen (maintenance contract required)

Added a welcome screen to be displayed after starting Asprova. This makes it easier to access recently used files and our various web services, including access to installed sample files and data from the “Kokoshiri” series.

Enter a keyword to search for the corresponding sample file among the installed sample files and the data you need to know here. You can search by feature name, production method, mold or worker, or any other word.
 

   5. Online search (maintenance contract required)

You can cross-search over various educational materials such as online help, Knowledge Center, “Here’s what you need to know series”, and e-learning.

   6. Jump to online help (maintenance contract required)

It is now possible to jump to a specific page for online help for each Asprova property and command. In the following situations, press “Online Help” from the right-click pop-up menu to jump to the corresponding page.
(1) Property definition object, each property line of the property window, and the header line of the table window
(2) Class definition object
(3) Command object
(4) Internal function on the expression edit dialog.

In addition, from the help file of Ver. 16.2, help files have been created for each property, each class definition, each internal function, and each command.

   7. Improvements to the assigning methods of assigned operations (maintenance contract required)

Asprova has a status called “released” in the work object “status” property that indicates that instructions have been given to the work site, but instead of assigning this released operation forward from the last assigned time like fixed time work, it can be assigned forward from the scheduling basis time (※1). This will allow you to pack and allocate the operation in front of you according to the result of the previous operation.

(*1) If the “Result Entry Flag” of the resource is “Not mandatory”, the released operation that has been assigned in the past will be assigned and forwarded from the time of the last assignment.

For example, in previous versions, even if an operation was completed earlier than scheduled, started with a different resource than scheduled, or cancelled, the ordered operation would not move from the time it was ordered in the past. This sometimes caused operations to be assigned between previous operations and the released operations.

In the case of imposing raw material constraints, once the released operation was assigned to the end time of the assignment, it was necessary to cancel the released status once in order to assign it close to the scheduling basis time again.

From this version, you will be able to assign the operation to be done at the scheduling basis time so that no other work will be interrupted before the operation with an assigned status. For more information, see the help file for the “Released operations assignment method” property.
 

   8. Detailed output of tentative assignment evaluation values (maintenance contract required)

The temporary assignment evaluation values displayed when the “Assignment message level” in the project settings is set to “Detailed” can now be broken down by resource evaluation weight. The resource evaluation object used to calculate the temporary assignment evaluation value is also displayed. This makes it easier to adjust the weights and investigate why the operation was assigned to a resource.

   9. Improved date/time display in Gantt chart

The date/time scale in the header line of the Gantt chart is now displayed down to the minute. Also, when the display period is less than a day, the date and time are displayed in the corner box to make it easier to see the date currently displayed.
Also, 10 minutes and 30 minutes have been added to the unit term and display period.

   10. Grant permission to use the trial version by the distributor version protector.

Starting with Ver.16.0, the demo version requires a login and an offline key is required to use the Asprova trial version on an offline PC that is not connected to the Internet. But if you have a distributor version protector, you will be able to allow a PC to use the trial version for 7 days. In the User Information dialog, click the “Activate trial period for this computer” button. What is a distributor version? It is a protection key held by our sales partners who have passed the APT certification exam (certification exam on Asprova skills).

   11. Improved help files

From this version, help pages are provided for each property, class, internal function, and command. Also, the chapter on “Data Input/Output ” has been substantially rewritten.
 

   12. You will be unable to log in with your serial number.

We have made it so that the Asprova ID given with the purchased license cannot be used to log in when using the trial version. Please use the Asprova ID of your e-mail address for the Asprova ID you will use when using the trial version.
 

   13. Signed executable

Our installer, Asprova.exe, AsprovaNLS.exe, and various dll files distributed by our company has now been signed. This will prevent warnings from appearing during installation and software startup in Windows 10 and other operating systems.