Compile Constraints by Configurable Item (tipcf2201m000)

Use this session to compile constraints by generic item for the Object Version of the product configurator, in which an object is generated per item.

Select the directories in LN where the constraint source file and the constraint object file must be stored.
Indicate whether the constraint source file must be deleted from LN after compilation.
Click the Compile option to start the compilation process.

If errors are found when LN compiles constraints, they are logged in a system file with a name similar to that of the constraint source file. However, the name acquires the suffix .e.

Note: Compiling constraints by generic item is only useful if the Product Configurator Version field in the Product Configuration Parameters (tipcf0100m000) session is set to Object Version. In that case, you must run this session each time constraints are updated.

Field Information

From Item

The From and To fields define a range of: configurable items.

Delete Constraint Source

If this check box is selected, the generated constraint source files are deleted from LN after compilation.

If this check box is cleared, the generated constraint source files are not deleted from LN after compilation. It may be useful to be able to consult constraint source files, especially with compilation errors.

Compile in Debug

If this check box is selected, you can debug the evaluation of the constraints, because the constraint objects are compiled in debug mode.

Show Compilation Errors Only

If this check box is selected, LN only prints the compilation errors.

Constraints Directories

Constraint Source Directory

Before constraints can be compiled, this session first generates constraint sources. These constraint sources are stored in the <path.name>/ppcfcons<company.number> directory of your file system.

Enter the path name of the directory in which you want to store the constraint source. You can enter the full path name or use the current directory as your departure point. In the latter situation, the path name must begin with a period [.].

Note: The system adds the name of the constraint source directory to the path name automatically, but you can also add the name yourself. The next time you use this session, the saved directory is presented as the default. In case no directory has been saved, the $BSE/lib/fd<tools.version>.<packet.combination > file is used to determine the default path.

If no directory has been saved, and you are working on a system that has no $BSE/lib/fd<tools version>.<packet.combination> file, you are asked to enter the directory where the sources are to be stored.

Constraint Object Directory

Enter the path name of the directory in which you want to store the constraint objects. You can enter the full path name or use the current directory as your departure point. In the latter situation, the path name must begin with a period and a slash.

Note: The system adds the name of the constraint object directory to the path name automatically, but you can also add the name yourself. If no directory has been saved, the $BSE/lib/fd<tools.version>.<package.combination> file is used to determine the default path.

If no directory has been saved and you are working on a system that has no file called " $BSE/lib/fd<tools version>.<packet.combination>," you are asked to enter the directory where the objects must be stored.