JP7469854B2 - Screen creation device - Google Patents

Description

The present invention relates to a screen creation device.

Since the screens of programmable displays tend to be more detailed and complex, the scale of projects that combine multiple related screens is becoming larger and larger. As a result, it is no longer possible for one person to create the entire project, and it is becoming more common for multiple editors to work on a single project. Therefore, screen editing software that edits the screens that belong to a project is required to manage the division of labor involved in the production of a single project.

For example, the programming device disclosed in Patent Document 1 restricts the types of access operations by function that a user can perform when accessing a programmable logic controller based on the level of access authority that corresponds to the password entered by the user.

JP 2007-280348 A

However, the programming device disclosed in Patent Document 1 selects and restricts the types of access operations by function performed by the user, which means that it is not possible to flexibly and precisely set the types of access operations by function performed by the user for each account. One aspect of the present invention aims to flexibly and precisely set definition information that defines the editing range that can be edited on screen for each account.

To solve the above problem, a screen creation device according to one aspect of the present invention includes a reference unit that references definition information that defines in association a plurality of accounts for authenticating a user who performs screen editing, and an editable screen range as information that is the subject of screen editing and that specifies an editing subject that constitutes part of the screen, and a determination unit that determines whether or not to restrict editing for each account according to the editing range, based on the definition information referenced by the reference unit.

According to the above configuration, a user can edit the screen while an editing object that constitutes part of the screen is specified. Therefore, it is possible to assign roles to each user in creating the editing object.

The screen creation device according to one aspect of the present invention includes a reference unit that references definition information that defines multiple accounts for authenticating a user who performs screen editing in association with the editing range that can be edited on the screen, a determination unit that determines whether or not to restrict editing for each account according to the editing range based on the definition information referenced by the reference unit, and a management unit that manages the definition information so that an administrator who manages the multiple accounts can write the definition information for the determination by the determination unit using a script.

According to the above configuration, the administrator can write definition information using a script, so that the definition information can be set flexibly and in detail for each account. This allows the administrator to easily set even complex editing ranges. In addition, the administrator can easily change the definition information for each account.

The management unit may manage the definition information so that the administrator can write the definition information using the script including regular expressions.

According to the above configuration, the administrator can write the definition information using a script that includes regular expressions. This can reduce the amount of definition information that needs to be written. In addition, the administrator writes the definition information using regular expressions that have rules for writing. This can prevent the administrator from writing the definition information incorrectly.

The reference unit may refer to the definition information included in at least one of the program and the data, or the definition information provided outside the program and the data, at least one of when a program for performing screen editing is started and when a file of data for which screen editing is to be performed is opened.

According to the above configuration, whether or not to restrict editing for each account is determined at least when a user launches a program or opens a data file, so editing can be automatically restricted for each account.

The definition information may include information on a plurality of rule settings that indicate whether an editing object that is the subject of screen editing and that constitutes a part of the screen can be edited, and information that applies at least one of the plurality of rule settings to each of a plurality of editor types that are set for each account and indicate the type of editor who will perform the screen editing.

According to the above configuration, at least one of the multiple rule settings is applied to each editor type set for each account. Therefore, by selecting an editor type for each account, the administrator can easily set the editing range that can be edited on the screen for each account.

The definition information may include information in which a hierarchical relationship is set for the multiple editing targets, and the determination unit may determine, based on the hierarchical relationship, that if a predetermined rule setting is applied to the editor type, the editor type is also permitted to edit editing targets that are lower in rank than the editing targets permitted to be edited by the predetermined rule setting.

According to the above configuration, the administrator can easily create rule settings, and can easily restrict editing for each account. In addition, since the editor type is permitted to edit an editing target that is lower in rank than the editing target permitted to be edited in a specific rule setting, the work required for the administrator to create rule settings can be reduced.

The determination unit may determine that, if a predetermined rule setting is applied to the editor type, the editor type is permitted to edit all editing targets other than the editing target for which editing is restricted by the predetermined rule setting.

According to the above configuration, the administrator can easily create rule settings, and can easily restrict editing for each account. In addition, since the editor type is permitted to edit all editing targets other than those restricted by a specific rule setting, the work involved in creating rule settings by the administrator can be reduced.

The reference unit may refer to link information that associates an editing screen with at least one piece of editing information for an editing screen and editing information related to the editing screen that has been edited within the editing range associated with the multiple accounts, and the screen creation device may further include a creation unit that creates data in which screen editing has been performed by combining the editing screen associated in the link information referenced by the reference unit with at least one piece of editing information.

According to the above configuration, when re-editing an editing screen or editing information related to the editing screen, the editing screen and editing information are re-edited for each account. This not only makes it possible to efficiently re-edit the editing screen and editing information, but also eliminates the need to make the same corrections to multiple pieces of data that have been edited on the screen, making it less likely that human error will occur.

In addition, data that has undergone screen editing is created by combining the editing screen and editing information associated in the link information. Therefore, when multiple pieces of data that have undergone screen editing are created, changes to the editing screen or changes to the editing information can be reflected in multiple pieces of data that have undergone screen editing all at once. This allows the user to reduce the time it takes to create a screen.

According to one aspect of the present invention, it is possible to flexibly and precisely set definition information that defines the range of screen editing that can be performed for each account.

1 is a block diagram showing configurations of a PC and a programmable display device according to a first embodiment of the present invention; 1A is a diagram showing an account setting screen that can only be opened by an administrator, FIG. 1B is a diagram showing an editor type setting screen that can only be opened by an administrator, and FIG. 1C is a diagram showing a rule setting screen that can only be opened by an administrator. 2A is a diagram showing an example of definition information set on a setting screen such as that shown in FIG. 2C, and FIG. 2B is a diagram showing how editing is restricted by the definition information shown in FIG. FIG. 13 is a diagram showing screen data as data on which screen editing has been performed; FIG. 5 is a schematic diagram showing how data for the screen shown in FIG. 4 is created. FIG. 11 is a diagram showing an example of a storage location of definition information in a PC according to a second embodiment of the present invention.

[Embodiment 1]
The configurations of a personal computer (hereinafter, simply referred to as "PC") 1 and a programmable display device 2 will be described with reference to Fig. 1. Fig. 1 is a block diagram showing the configurations of a PC 1 and a programmable display device 2 according to a first embodiment of the present invention.

(Configuration of PC1)
1, the PC 1 includes a control unit 10, a recording unit 20, an interface unit 30, a display unit 40, and an operation unit 50. The PC 1 is connected to a programmable display device 2. The PC 1 functions as a screen creation device that creates a screen to be displayed by the programmable display device 2 by executing a program for performing screen editing.

The control unit 10 includes a reference unit 11, a determination unit 12, a management unit 13, a creation unit 14, a display control unit 15, and a communication control unit 16. The control unit 10 controls each unit of the PC 1. The reference unit 11 references the definition information recorded in the recording unit 20.

The definition information defines in association a plurality of accounts for authenticating a user who performs screen editing, and a screen editable editing range as information that is the subject of screen editing and that specifies an editing object that constitutes part of the screen. According to the above configuration, a user can perform screen editing with an editing object that constitutes part of the screen specified. Therefore, it is possible to assign roles for creating the editing object to each user.

Examples of the editing target include multiple layers included in a screen, areas within a screen, and objects included in a screen. The objects include, for example, parts and figures. Examples of the editing target include, for parts, some of the part attributes such as position, size, character, address, and variable name, and for figures, some of the figure attributes such as position, size, line type, line thickness, and color. An address is an address in the memory of the PLC 3 or the internal memory of the programmable display device 2. A variable name is information presented to the user instead of an address so that the user can easily recognize the address.

Here, the definition information is described as being recorded in the recording unit 20, but the definition information may be recorded, for example, in a recording medium connected to the PC1. In this case, the reference unit 11 refers to the definition information recorded in the recording medium when the recording medium is connected to the PC1. In other words, one aspect of the present invention is not limited to the case where the definition information is recorded in the recording unit 20, and the definition information may be recorded in something external to the PC1.

The determination unit 12 determines whether or not to restrict editing for each account according to the editing range, based on the definition information referenced by the reference unit 11. The management unit 13 manages the definition information recorded in the recording unit 20. Details of the processes of the determination unit 12, management unit 13, and creation unit 14 will be described later. The display control unit 15 controls the display of the display unit 40. The communication control unit 16 controls the communication between the PC 1 and the programmable display device 2 via the interface unit 30.

The interface unit 30 is a communication unit that enables the PC 1 to communicate with the programmable display device 2. The display unit 40 is a monitor that displays the processing contents of the PC 1. The operation unit 50 is, for example, a keyboard that allows the user to input data and a mouse that allows the user to perform operations.

(Configuration of programmable display unit 2)
1, the programmable display device 2 includes a control unit 21, a display panel 22, a touch panel 23, a user memory 24, and interface units 25 and 26. The programmable display device 2 is connected to a PLC (programmable logic controller) 3 as an external device.

The programmable display 2 is connected to the PLC 3 via a communication cable, and communicates with the PLC 3. The programmable display 2 is a dedicated computer that realizes the operation and display functions unique to the programmable display by displaying a screen for operation and display, and is used as an HMI (Human Machine Interface) device.

The control unit 21 specifies the operation of displaying the state of the device 4 connected to the PLC 3 and the operation of controlling the state of the device 4 in response to operations on the touch panel 23. The display panel 22 displays screens created by the user and the state of the device 4. The user memory 24 records the screens created by the user as a collection of multiple related screens (screen groups) in a file format called a project. The project is created by the creation unit 14 of the PC 1 and downloaded from the PC 1. The interface unit 25 is a communication unit that allows the programmable display device 2 to communicate with the PC 1. The interface unit 26 is a communication unit that allows the programmable display device 2 to communicate with the PLC 3.

PLC3 is a control device that reads the status of device 4 and issues control instructions to device 4 at each predetermined scan time according to a sequence program created by the user.

(Processing of management unit 13)
The management unit 13 manages definition information as shown in (a) to (c) of Fig. 2. (a) of Fig. 2 is a diagram showing an account setting screen that can only be opened by the administrator. (b) of Fig. 2 is a diagram showing an editor type setting screen that can only be opened by the administrator. (c) of Fig. 2 is a diagram showing a rule setting setting screen that can only be opened by the administrator. The screens shown in (a) to (c) of Fig. 2 are opened by a program for screen editing and are displayed on the display unit 40 of the PC 1. Here, the administrator is a person who manages each account.

For each item shown in FIG. 2(a), "User Name" indicates the name of the user associated with the account for logging in, and "Password" indicates the password for the account for logging in. The login function is provided in at least one of the program for performing screen editing and the data for which screen editing is performed.

"Operator Type" indicates the type of editor performing the screen editing. When the administrator clicks on arrow A1 using the operation unit 50, multiple editor type candidates indicating the type of editor performing the screen editing are displayed. When the administrator clicks on one of the editor type candidates using the operation unit 50, the editor type for the account is determined.

In this way, the administrator can select the editor type for each account. In addition, on the screen shown in FIG. 2(a), the administrator can add an account to at least one of the program for performing screen editing and the data for which screen editing is to be performed. At this time, the management unit 13 changes the definition information recorded in the recording unit 20 based on the operation information from the operation unit 50. The editor type is set on the screen shown in FIG. 2(b).

For each item shown in FIG. 2(b), "Operator Type" indicates the same editor type as "Operator Type" shown in FIG. 2(a). "Rule Name(s)" indicates the names of multiple rule settings that are the subject of screen editing and indicate whether editing is possible for the editing subject that constitutes part of the screen. When the administrator clicks button B1, multiple rule setting candidates are displayed.

When the administrator clicks on a candidate rule setting using the operation unit 50, the rule setting to be applied to the editor type is determined. In this way, the administrator can select at least one rule setting. At this time, the management unit 13 changes the definition information recorded in the recording unit 20 based on the operation information from the operation unit 50.

The definition information therefore includes information on multiple rule settings and information in which at least one of the multiple rule settings is applied to each of multiple editor types set for each account. According to the above configuration, the administrator can easily set the editing range that can be edited on the screen for each account by selecting the editor type for each account.

For each item shown in Figure 2(c), "Rule Name" indicates the name of each rule setting displayed in "Rule Name(s)" shown in Figure 2(b). "Component" indicates the function of the program for screen editing. "Type" indicates the type of rule setting, and "Rule" indicates the specific rule setting content for each rule setting.

When the administrator clicks on the arrow A2 using the operation unit 50, candidate functions of the program are displayed. When the administrator clicks on one of the candidate functions of the program using the operation unit 50, the function of the program to be applied to the rule setting is determined. At this time, the management unit 13 changes the definition information recorded in the recording unit 20 based on the operation information from the operation unit 50.

When the administrator clicks on arrow A3 using the operation unit 50, candidate types of rule settings are displayed. In this way, the administrator can select the type of rule setting for each rule. At this time, the management unit 13 changes the definition information recorded in the recording unit 20 based on the operation information from the operation unit 50.

Furthermore, in "Rule," the administrator can write specific rule settings using scripts that include regular expressions. For example, by adding the regular expression "[0-9]" to the "Name" of a "Screen," the administrator can restrict the use of only numbers in the "Screen" name.

The "Rule" item shown in Figure 2(c) allows the administrator to create rules for variable names, object names, and various other error checks for each user. Examples of rules set in the "Rule" item shown in Figure 2(c) include naming rules for objects and variables, stipulations on the range of values for the properties of each object, an upper limit on the number of objects and variables that can be created, and restrictions on the types of objects that can be created.

Note that the administrator may be able to write specific rule settings in "Rule" using a script that does not include regular expressions. In the screen shown in FIG. 2(c), the administrator can easily set each rule by selecting "Component" and "Type."

As described above, the management unit 13 enables an account to be set for each user in a program for performing screen editing, such as screen editing software for editing the screen of the programmable display device 2. The management unit 13 also manages definition information so that an administrator who manages multiple accounts can use a script to write definition information for judgment by the judgment unit 12 on the screens shown in (a) to (c) of FIG. 2.

According to the above configuration, the administrator can write definition information using a script, so that the definition information can be set flexibly and in detail for each account. This allows the administrator to easily set even complex editing ranges. In addition, the administrator can easily change the definition information for each account.

In addition, the editing scope for each account is not predetermined, such as the data unit or screen unit for which screen editing is performed, but can be freely defined, making it easy to set complex scopes of responsibility for each user.In addition, since the definition information is set using a descriptive method, the definition information can be created freely, and the program for screen editing can be freely selected.

Figures 2(a) to (c) show an example of definition information that combines table-format selection and script notation, but all of the definition information may be written in script notation as shown below.

Rule_1 = ScreenDesign.All.Editable
Rule_2 = ScreenDesign.Object.Screen1, Screen2, @Screen, Screen1.Grid1
Rule_3 = Alarm.Property.@ALARMGROUP.Name
Rule_4 = Alarm.Value.@ALARMGROUP.Name = ^A+[0-9a-zA-Z]+[0-9]$
…
In this way, by using a descriptive format for all definition information, it becomes easy to edit a large number of rules, accounts, editor types, etc., by copying and appending, and to reuse the information when creating other definition information. In addition, if it becomes possible to export (write out) definition information entered in table format to the above-mentioned descriptive format and to import (import) definition information written in the descriptive format, editing can be made even easier.

The management unit 13 may also manage the definition information so that the administrator can write the definition information using a script including regular expressions. According to the above configuration, the administrator can write the definition information using a script including regular expressions. This makes it possible to reduce the amount of definition information to be written. The administrator writes the definition information using regular expressions for which descriptive rules are set. This makes it possible to prevent the administrator from writing the definition information incorrectly.

(Processing of Determination Unit 12)
The determination unit 12 determines whether or not to restrict editing depending on the editing range that can be edited on the screen for each account, based on the definition information referred to from the recording unit 20 by the reference unit 11. A specific description will be given below based on (a) and (b) of Fig. 3. (a) of Fig. 3 is a diagram showing an example of definition information set on a setting screen such as that shown in (c) of Fig. 2. (b) of Fig. 3 is a diagram showing how editing is restricted by the definition information shown in (a) of Fig. 3.

The recording unit 20 records definition information such as that shown in FIG. 3A. As shown in FIG. 3A, in a rule setting in which "Rule Name" is "Rule_1", "Component" is set to "ScreenDesign", "Type" is set to "Object", and "Rule" is set to "Screen1.Grid.Ellipse1".

A user who uses an account to which only "Rule_1" is applied can only edit Ellipse 1 on the Grid in Screen 1 of multiple screens, as an object in ScreenDesign. In other words, as shown in Figure 3(b), a user who uses an account to which only "Rule_1" is applied cannot add or edit any objects other than Ellipse 1 on the Grid in Screen 1.

In this case, the determination unit 12 determines that there will be no restriction on editing ellipse 1 by a user using an account to which only "Rule_1" is applied, and determines that there will be restrictions on editing other objects other than ellipse 1 by that user.

The definition information also includes information in which a hierarchical relationship is set for multiple editing targets. The information in which the hierarchical relationship is set, which is included in the definition information, is recorded in advance in the recording unit 20. If a predetermined rule setting is applied to the editor type shown in FIG. 2(b) based on the hierarchical relationship, the determination unit 12 determines that the editor type is also permitted to edit editing targets that are lower in rank than the editing targets permitted to be edited by the predetermined rule setting.

According to the above configuration, the administrator can easily create rule settings, and can easily restrict editing for each account. In addition, since the editor type is permitted to edit an editing target that is lower in rank than the editing target permitted to be edited in a specific rule setting, the work required for the administrator to create rule settings can be reduced.

Specifically, for example, consider the case of the definition information shown in FIG. 3(a). In this case, editing of ellipse 1 in FIG. 3(b) is permitted, so the determination unit 12 determines that editing of all of the editing objects lower than the editing object ellipse 1, that is, the properties of ellipse 1, such as the color, line type, line color, line thickness, position, and size, etc. of ellipse 1, is permitted.

As another example, if "Rule" is set to "Screen1.Canvas.Rectangle1.Fill=[Red,Yellow]", the color of Rectangle1 is limited to red or yellow. On the other hand, if "Rule" is set to "Screen1.Canvas.Rectangle1.Fill", the user can freely set the color of Rectangle1.

Furthermore, the determination unit 12 determines that, based on the hierarchical relationship, if a predetermined rule setting is applied to the editor type shown in FIG. 2(b), the editor type is not permitted to edit an editing target that is at the same level as or higher than an editing target permitted to be edited by the predetermined rule setting. Since editing targets higher than an editing target permitted to be edited by the predetermined rule setting are not permitted, it is necessary to specify a screen or object as a lower-level editing target in the predetermined rule setting.

The determination unit 12 may determine that, if a predetermined rule setting is applied to an editor type, the editor type is permitted to edit all editing targets other than those restricted by the predetermined rule setting. According to the above configuration, the administrator can easily create rule settings, and therefore can easily restrict editing for each account. In addition, since the editor type is permitted to edit all editing targets other than those restricted by the predetermined rule setting, the administrator's work involved in creating rule settings can be reduced.

Specifically, consider a case where editing is restricted using the definition information shown in FIG. 3A. "Rule_1" is a definition that indicates permission, and one example of its use to restrict it to a certain editor type is "Operator_100 = !Rule_1". In this case, when the editor type of a certain account is "Operator_100", the determination unit 12 determines that editing is permitted for all editing targets other than the editing target of "Rule_1" in FIG. 3A. The editing targets for which editing is restricted in FIG. 3B are screen 1, grid, and ellipse 1. In this case, the determination unit 12 determines that editing is permitted for all editing targets other than screen 1, grid, and ellipse 1, which are editing targets for which editing is restricted.

In other words, the determination unit 12 determines that all editing other than ellipse 1 on the grid in screen 1 is permitted. In this case, the editing targets for which editing is restricted are all of the editing of ellipse 1, so editing cannot be performed on any of the properties of ellipse 1. Conversely, if the editing targets are other than ellipse 1, editing can be performed on all of the editing targets.

As another example, consider the case where editing is restricted using the definition information where "Rule_1" is set to "Screen1.Canvas.Fill." One example of using "Rule_1" to restrict editing to a certain editor type is "Operator_100 = !Rule_1 = !Screen1.Canvas.Fill." In this case, the user can change everything except the fill of all objects in the Canvas of screen 1.

(Processing of Creation Unit 14)
The creation unit 14 performs an editing process in response to a user operation via the operation unit 50, and creates data for one screen, for example, as data for which screen editing has been performed, as shown in Fig. 4. A specific description will be given below with reference to Figs. 4 and 5. Fig. 4 is a diagram showing data for a screen as data for which screen editing has been performed. Fig. 5 is a schematic diagram showing how data for the screen shown in Fig. 4 is created.

Here, the data for one screen shown in FIG. 4 is assumed to be created by three users, users A, B, and C. Also, user A is in charge of the basic layout, user B is in charge of address settings, and user C is in charge of color settings. As shown in FIG. 4, user A places objects to be edited, such as a title T1, a graph G1, a numeric display R1, switches SW1 to SW6, and an input key I1, on the editing screen P1.

This sets the basic layout of the screen data, and the basic layout of the screen data is recorded as edit screen P1 in the area of the management database recorded in the recording unit 20 that is responsible for user A, as shown in FIG. 5. Here, for the account used by user A, user A performs editing within the editing range associated with that account.

User B also sets the addresses of the graph G1, numeric display R1, and switches SW1 to SW6, which require address setting. This sets the address of each edit target of the screen data, and the address of each edit target of the screen data is recorded as Address Setting 1, which is editing information, in the area of the management database for user B, as shown in FIG. 5. Here, for the account used by user B, user B performs editing within the editing range associated with that account.

Furthermore, user C sets the colors of title T1, graph G1, numeric display R1, switches SW1 to SW6, and input key I1. This sets the color of each edit target of the data on the screen, and the color of each edit target of the data on the screen is recorded as color setting 1, which is editing information, in the area of the management database for user C, as shown in FIG. 5. Here, for the account used by user C, user C performs editing within the editing range associated with that account.

The reference unit 11 refers to link information that associates the editing screen P1, address setting 1, and color setting 1. The editing screen P1 is an editing screen edited within an editing range associated with an account used by user A. The address setting 1 is editing information edited within an editing range associated with an account used by user B. The color setting 1 is editing information edited within an editing range associated with an account used by user C.

As shown in FIG. 5, the creation unit 14 creates a project for Company X as screen edited data by combining the edit screen P1, address setting 1, and color setting 1 associated in the link information referenced by the reference unit 11. In this way, one screen can be created by multiple users.

The reference unit 11 may also refer to link information that associates the editing screen P1, an address setting 2 different from the address setting 1, and a color setting 2 different from the color setting 1. In this case, the creation unit 14 creates a project for Company Y as data for which screen editing has been performed by combining the editing screen P1, the address setting 2, and the color setting 2 associated in the link information referenced by the reference unit 11. A project for Company Z is also created in a similar manner by the creation unit 14.

As described above, the reference unit 11 references link information that associates an editing screen with at least one piece of editing information for editing screens and editing information related to the editing screens that have been edited within an editing range associated with multiple accounts. The creation unit 14 also creates data on which screen editing has been performed by combining the editing screen associated in the link information referenced by the reference unit 11 with at least one piece of editing information.

According to the above configuration, when re-editing an editing screen or editing information related to the editing screen, the editing screen and editing information are re-edited for each account. This not only makes it possible to efficiently re-edit the editing screen and editing information, but also eliminates the need to make the same corrections to multiple pieces of data that have been edited on the screen, making it less likely that human error will occur.

In addition, data that has undergone screen editing is created by combining the editing screen and editing information associated in the link information. Therefore, when multiple pieces of data that have undergone screen editing are created, changes to the editing screen or changes to the editing information can be reflected in multiple pieces of data that have undergone screen editing all at once. This allows the user to reduce the time it takes to create a screen.

[Embodiment 2]
Another embodiment of the present invention will be described below. For convenience of explanation, the same reference numerals are given to components having the same functions as those described in the first embodiment, and the description thereof will not be repeated. Fig. 6 is a diagram showing an example of a storage location of definition information in a PC according to a second embodiment of the present invention.

As shown in FIG. 6, users A and B edit project PRJ1, which is a project for company X and serves as a data file for screen editing. Users C and D edit project PRJ2, which is a project for company X and serves as a data file for screen editing. Users A to D use a common program PRG for screen editing.

The accounts used by users A to D are associated with common definition information RX, which is information common to the definition information associated with each account and is used for screen editing for projects for company X. The common definition information RX is information included in the program PRG, and is applied to each user who uses the program PRG before the dedicated definition information described below is applied to each user.

Projects PRJ1, PRJ2 and program PRG may be recorded in the recording unit 20, or may be recorded on something external to PC1, such as a recording medium connected to PC1. Also, one of projects PRJ1, PRJ2 and program PRG may be recorded in the recording unit 20, and the other of projects PRJ1, PRJ2 and program PRG may be recorded on something external to PC1, such as a recording medium connected to PC1.

Furthermore, the account used by user A is associated with dedicated definition information RA, which is information dedicated to the definition information associated with that account. The dedicated definition information RA is information included in project PRJ1, and is part of the definition information associated with the account used by user A.

In other words, the definition information associated with the account used by user A is composed of dedicated definition information RA and common definition information RX. Similarly, the definition information associated with the accounts used by users B to D is composed of dedicated definition information RB to RD and common definition information RX, respectively. If dedicated definition information is recorded for each project, unauthorized users cannot edit the project even if they open it.

As shown in FIG. 6, users E and F edit project PRJ3, which is a project for company Y and serves as a data file for screen editing. Users G and H edit project PRJ4, which is a project for company Y and serves as a data file for screen editing. Users E to H use a common program PRG for screen editing.

Similarly, for projects PRJ3 and PRJ4, which are projects for Company Y, the definition information associated with the accounts used by users E to H is composed of dedicated definition information RE to RH and common definition information RY, respectively. The common definition information RY is information for performing screen editing for projects for Company Y, but may be the same information as the common definition information RX.

Here, for example, consider a case where the reference unit 11 references definition information associated with an account used by user A. In this case, the reference unit 11 references the common definition information RX included in the program PRG and the dedicated definition information RA included in the project PRJ1 at least when the program PRG is started or when the project PRJ1 is opened.

In addition, both the dedicated definition information RA and the common definition information RX may be included in either the program PRG or the project PRJ1. In this case, the reference unit 11 refers to both the dedicated definition information RA and the common definition information RX included in either the program PRG or the project PRJ1.

In addition, both the dedicated definition information RA and the common definition information RX may be provided in a file outside the program PRG and the project PRJ1. In this case, the reference unit 11 refers to both the dedicated definition information RA and the common definition information RX provided in a file outside the program PRG and the project PRJ1. Furthermore, there may be no dedicated definition information RA, and only common definition information RX may exist. In this case, the reference unit 11 refers only to the common definition information RX.

The contents explained regarding the definition information associated with the account used by user A also apply to the case where the reference unit 11 refers to the definition information associated with the accounts used by users B to H. Here, after the reference unit 11 refers to the definition information, the determination unit 12 makes a determination in the same manner as described above.

As a result, when a program for performing screen editing is started or when a file of data for which screen editing is to be performed is opened, the reference unit 11 refers to the definition information contained in at least one of the program and the data, or the definition information provided outside the program and the data.

According to the above configuration, whether or not to restrict editing for each account is determined at least when a user launches a program or opens a data file, so editing can be automatically restricted for each account.

In addition, when the program for performing screen editing is started or when the file of the data for screen editing is opened, the definition information associated with the account is automatically applied to the error check performed by the program for performing screen editing. Since the error check performed by the program for performing screen editing is managed using a script, the application of the definition information to the error check can be performed without compiling.

Therefore, when an administrator wants to change the definition information, the administrator can edit the definition information simply by opening the data for which screen editing will be performed, changing the definition information, and saving it. The flow for screen editing by multiple users is described below. The administrator first creates the data for which screen editing will be performed, creates definition information for each account, and embeds the definition information in the data for which screen editing will be performed.

The administrator then copies the created data for screen editing and distributes it to each user. Users can log in with their own accounts and perform screen editing, checking for errors with their own settings. Since the definition information is embedded in the data for screen editing, when different users perform screen editing on the same data, they can log in with their own accounts and perform screen editing with their own definition information.

This allows the administrator to manage variable names etc. by checking for errors, eliminating collisions and making merging easier. Specifically, the administrator can set definition information for each user, preventing collisions when merging two projects. One example of a collision when merging two projects is when the names of created objects, screen numbers or screen names overlap.

To prevent these collisions from occurring, it is preferable for the administrator to set the definition information so that the object names and screen names created by user A will start with A and the screen numbers will be in the 1000s. It is also preferable for the administrator to set the definition information so that the object names and screen names created by user B will start with B and the screen numbers will be in the 2000s.

In this way, the administrator can set definition information for each user, preventing conflicts when each user uses the program's error checking function, making it easy to implement an automatic merge function in the program.

[Software implementation example]
The control block of the PC 1 (particularly the control unit 10) may be realized by a logic circuit (hardware) formed on an integrated circuit (IC chip) or the like, or may be realized by software.

In the latter case, the PC1 is equipped with a computer that executes the instructions of a program, which is software that realizes each function. This computer is equipped with, for example, one or more processors, and a computer-readable recording medium that stores the program. The object of the present invention is achieved by the processor reading the program from the recording medium and executing it in the computer. The processor can be, for example, a CPU (Central Processing Unit). The recording medium can be a "non-transient tangible medium", such as a ROM (Read Only Memory), as well as a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, etc. The computer may also be equipped with a RAM (Random Access Memory) that expands the program. The program may be supplied to the computer via any transmission medium (such as a communication network or a broadcast wave) that can transmit the program. Note that one aspect of the present invention can also be realized in the form of a data signal embedded in a carrier wave, in which the program is embodied by electronic transmission.

The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. The technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments.

1 PC (screen creation device)
11 Reference section 12 Determination section 13 Management section 14 Creation section P1 Editing screen PRJ1, PRJ2, PRJ3, PRJ4 Project (data for which screen editing is performed)
PRG Program (program for editing screens)

Claims (6)

A screen creation device that creates a screen to be displayed by a programmable display device,
a reference unit that references definition information that defines, in association with each other, a plurality of accounts for authenticating each of a plurality of editors who share the screen editing of the screen including a plurality of editing objects that are the subject of screen editing, and an editing range that can be edited on the screen as information specifying the editing objects for each of the plurality of accounts;
a determination unit that determines whether or not to restrict editing of a screen in creating a screen to be displayed on the programmable display device according to the editing range for each account based on the definition information referenced by the reference unit;
A screen creation device comprising: a management unit that manages the definition information so that an administrator who manages the multiple accounts can write the definition information for judgment by the judgment unit using a script including regular expressions . The screen creation device according to claim 1, characterized in that the reference unit references the definition information contained in at least one of the program and the data, or the definition information provided outside the program and the data, at least one of when a program for screen editing is launched and when a file of data for which screen editing is to be performed is opened. The screen creation device according to claim 1 or 2, characterized in that the definition information includes information on a plurality of rule settings indicating whether or not editing is possible for the editing object that is the subject of screen editing and constitutes part of the screen, and information in which at least one of the plurality of rule settings is applied to each of a plurality of editor types that are set for each account and indicate the type of editor who will perform the screen editing. the definition information includes information in which a hierarchical relationship is set for the plurality of editing objects,
The screen creation device according to claim 3, characterized in that the determination unit determines that, if a predetermined rule setting is applied to the editor type based on the hierarchical relationship, the editor type is also permitted to edit editing objects that are lower in rank than the editing object permitted to be edited by the predetermined rule setting. The screen creation device according to claim 3, characterized in that the determination unit determines that, when a predetermined rule setting is applied to the editor type, the editor type is permitted to edit all editing objects other than the editing object for which editing is restricted by the predetermined rule setting. the reference unit refers to link information that associates the editing screen with at least one piece of editing information for an editing screen edited within the editing range associated with the multiple accounts and editing information related to the editing screen;
A screen creation device as described in any one of claims 1 to 5, further comprising a creation unit that creates data for which screen editing has been performed by combining the editing screen associated in the link information referenced by the reference unit with at least one of the editing information.

Images