WO2019011255A1 - 通过第三方字段对表单字段的字段值进行授权的方法 - Google Patents
通过第三方字段对表单字段的字段值进行授权的方法 Download PDFInfo
- Publication number
- WO2019011255A1 WO2019011255A1 PCT/CN2018/095204 CN2018095204W WO2019011255A1 WO 2019011255 A1 WO2019011255 A1 WO 2019011255A1 CN 2018095204 W CN2018095204 W CN 2018095204W WO 2019011255 A1 WO2019011255 A1 WO 2019011255A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- field
- authorized
- time
- party
- role
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/105—Human resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2137—Time limited access, e.g. to a computer or data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2145—Inheriting rights or properties, e.g., propagation of permissions or restrictions within a hierarchy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2149—Restricted operating environment
Definitions
- the present invention relates to a form authorization method for a management software system such as an ERP, and more particularly to a method for authorizing a field value of a form field by a third party field.
- the fields in the form include contract signing time, contract signator, customer name, customer industry, etc.
- the user can separately authorize the content of the fields that the user can view, and allow the user A to view the contract signing time and the contract signing party in the form, and not allow the user A to view the customer name and the customer industry, thereby realizing the confidentiality of the company information and preventing the confidential information.
- these ERP management software can only authorize each user separately, and cannot realize the batch authorization of the user. The authorization operation is inefficient, and it will bring a huge workload to a system containing a large number of users.
- the fields in the form cannot be further limited, so that the user can view a large amount of data after obtaining the viewing permission of the field value of a certain field, which is likely to cause information leakage for the business responsibility subdivision enterprise.
- User C is authorized to be able to view the contract signing time, contract signer and customer name of the contract form, but the actual job responsibilities of User C are only responsible for the contract information statistics of the financial industry, but the existing permission setting method will lead to the user. C can view contract information of other industries outside the financial industry, which is not conducive to the company's information security.
- the traditional form field value authorization cannot control the field value of the authorized field of the form by the third-party field.
- Zhang San can view the order of the software industry.
- Price, traditional software can not achieve the differentiated authorization of the field values of such refined fields, the demand for high-demand management can not be achieved.
- Role-based access control is one of the most researched and matured database rights management mechanisms in recent years. It is considered to be an ideal candidate to replace traditional mandatory access control (MAC) and autonomous access control (DAC).
- the basic idea of role-based access control (RBAC) is to divide different roles according to different functional positions in the enterprise organization view, encapsulate the access rights of database resources in roles, and indirectly access database resources by being assigned different roles.
- the role-based permission control mechanism can manage the access rights of the system simply and efficiently, which greatly reduces the burden and cost of the system rights management, and makes the system rights management more in line with the business management specifications of the application system.
- the traditional role-based user rights management method adopts the "role-to-user one-to-many" association mechanism, and its "role” is group/class nature, that is, one role can simultaneously correspond to/associate multiple users, and the role is similar to the post.
- the authorization of user rights under this association mechanism is basically divided into the following three forms: 1, as shown in Figure 1, directly authorized to the user, the disadvantage is that the workload is large, the operation is frequent and troublesome; As shown in Figure 2, the role (class/group/post/work type) is authorized (a role can be associated with multiple users), and the user obtains the permission through the role; 3. As shown in Figure 3, the above two methods are combined. .
- both 2 and 3 need to authorize the role of the class/group nature, and the way of authorization through the role of class/group/post/work type has the following disadvantages: 1.
- the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
- the object of the present invention is to overcome the deficiencies of the prior art, and provide a method for authorizing a field value of a form field by a third party field, and controlling a field value of an authorized field of the form by a third party field to implement a refined field. The difference in the field value is authorized.
- a method for authorizing field values of a form field by a third party field including:
- the third party field is a field in the selected form, and the options of the third party field include one or more;
- Steps (2), (3), (4) are performed sequentially, and step (1) may be performed before step (2) or between step (2) and step (3) or in step (3) and step ( 4) Execute between or after step (4).
- the authorized object includes one or more of a person, a user, a group, a class, and a role
- the role is an independent individual, not a group/class, and a role can only associate with a unique user in the same time period.
- a user associates one or more roles.
- the role belongs to a department, and the role is unique under the department, and the role is authorized according to the work content of the role, and the user obtains the permission by associating the role.
- the user when the user moves across the department, the user is first associated with the role in the original department, and then the user is associated with the role in the new department.
- said third party field comprises a time property field and a non-time property field, said option of said time property field being determined by an authorized operator; said field value of said non-time property field being determined by selection or automatically determined, Select all of the alternatives when determining or auto-determining as an option for non-time nature fields.
- the option of the time property field includes one or more of the following: a time period from a current time back to a fixed time length to a current time period, a time period from a start time to a current time, and a time period. a time period from the start time to the system initial time, a time period from the start time to the cutoff time, a time period in which the time field value is a null value, and a time period from the system initial time to the current time, the slave system initial time to the current time
- the time period of time includes a time period in which the time field value is a null value.
- the viewing authority of the field value of the authorized field of the form of the authorized object is displayed as the last time the field value of the authorized field of the form of the authorized object is authorized. View permission saved when the authorized object is two or more, the view permission of the field value of the authorized field of the form of the authorized object is not displayed.
- the display manner includes: (1) displaying the field corresponding to the field value, but hiding the field value with the concealer; (2) the field value and the field corresponding to the field value are both Do not show.
- a method for authorizing a field value of a form field by a third-party field including: selecting one or more authorized objects; selecting a form to be authorized, showing that the field value of the form needs to be controlled by a third-party field
- Authorized field for authorization authority select template: select an existing authorized object or created template as an authorization template, and update the view permission of the field value of the authorized field of the authorized object to the authorization template.
- a method for authorizing field values of a form field through a third-party field including:
- the third party field is a field in the selected form, and the options of the third party field include one or more;
- Steps (2), (3), (4) are performed sequentially, and step (1) may be performed before step (2) or between step (2) and step (3) or in step (3) and step ( 4) Execute between or after step (4).
- the beneficial effects of the present invention are as follows: (1) In the present invention, by setting a third-party field to define an authorized field in the form that needs to perform the viewing permission/modification authority authorization of the field value, the viewing permission/modification permission of the authorized object can be determined. It is set to be consistent with its job responsibilities, thus preventing authorized objects from viewing/modifying form information (field content information of the form) unrelated to their work, reducing the possibility of corporate information disclosure.
- the viewing authority of the field value of the authorized field of the form of the authorized object is displayed as the last authorized time of the field value of the authorized field of the form of the authorized object.
- the saved viewing permission is convenient for the authorized operator to modify on the basis of this, and the authorization efficiency of the form is improved; the authorized objects of two or more authorized objects can be simultaneously authorized, and the batch with the same authority or most of the same authority is authorized to be authorized. The authorization efficiency of the object.
- the viewing permission of the field value of the authorized field of the authorized object's form is updated to the viewing right of the field value of the corresponding field in the authorization template, which can improve the authorization efficiency of the form, especially to improve the bulk authorization rights or the permissions. Most of the same forms are authorized for efficiency.
- the traditional authority management mechanism defines the role as a group, a job type, a class, etc.
- the role is a one-to-many relationship with the user. In the actual system use process, it is often necessary to perform the user's authority in the operation process. Adjustments, for example, when the employee permissions are changed, the permissions of an employee associated with the role change. We cannot change the permissions of the entire role because of the change of the individual employee permissions, because the role is also associated with other permissions. Staff. So in response to this situation, either create a new role to satisfy the employee whose permissions have changed, or directly authorize (disengage the role) from the employee based on the permission requirements.
- the above two processing methods not only require a long time for the role authorization in the case of a large number of role permissions, but also are easy to make mistakes, the user is cumbersome and troublesome to operate, and is also prone to errors resulting in loss to the system user.
- the role since the role is an independent individual, the role permission can be changed to achieve the goal.
- the method of the present application seems to increase the workload when the system is initialized, it can be made by copying and the like to make the role or authorization more efficient than the traditional group-based role, because the role of the group is not considered.
- the application scheme will make the permission setting clear and clear; especially after the system is used for a period of time (the user/role authority changes dynamically), the application scheme can greatly improve the system usage for the system user.
- the efficiency of the rights management makes the dynamic authorization simpler, more convenient, clearer and clearer, and improves the efficiency and reliability of the permission setting.
- the traditional group-based role authorization method is error-prone, and the method of the present application greatly reduces the probability of authorization errors, because the method of the present application only needs to consider the role as an independent individual, without considering the traditional method to associate the role of the group. What are the commonalities of multiple users? Even if the authorization error occurs, it only affects the user associated with the role, while the traditional group-based role affects all users associated with the role. Even if a permission authorization error occurs, the correction method of the present application is simple and short, and the traditional group-type role needs to consider the commonality of all users associated with the role when correcting the error, and not only the modification when there are many function points. Troublesome, complicated, very error-prone, and in many cases only new roles can be created.
- the method of the present application is as follows: the transferred user associates several roles.
- the user When adjusting the post, the user is first unlinked from the role in the original department (the canceled roles can be re-associated to other users), and then Associate users with roles in the new department. The operation is simple and will not go wrong.
- Reason 1 Because the role of this application is equivalent to a station number/post number, different station number/post number The work content/permissions are different. For example, the salesperson 1 role under the sales department and the developer 1 role of the technical department are completely different two station numbers/post numbers, and their permissions are different; Reason 2: If the department (sales department) of the salesperson 1 role is replaced with the technical department, and the role of the salesperson 1 is unchanged, there is a role in the technical department that has the authority of the sales department, which may lead to management confusion and security loopholes.
- FIG. 1 is a schematic diagram of a manner in which a system directly authorizes a user in the background art
- FIG. 2 is a schematic diagram of a manner in which a system authorizes a group/class role in the background art
- FIG. 3 is a schematic diagram of a manner in which a system directly authorizes a user and authorizes a group/class role role in the background art
- Figure 4 is a flow chart of an embodiment of the present invention.
- FIG. 5 is a schematic diagram of a manner in which a system authorizes a user through an independent individual role
- Figure 6 is a schematic view of a form in the present invention.
- Figure 7 is a schematic view of the selection of the contract signing time in Figure 6;
- FIG. 8 is a schematic diagram of FIG. 6 after selecting an industry to which the customer belongs;
- Figure 9 is a schematic diagram of a contract form
- Figure 10 is a flow chart of still another embodiment of the present invention.
- Figure 11 is a schematic diagram of a form after selecting an authorization template
- Figure 12 is a flow chart of still another embodiment of the present invention.
- a method for authorizing a field value of a form field by a third party field includes: selecting one or more authorized objects.
- the authorized object includes one or more of a person, a user, a group, a class, and a role, the role is an independent individual, not a group/class, and a role can only associate with a unique user in the same period, and one A user associates one or more roles.
- the role belongs to the department, and the role is authorized according to the work content of the role, and the name of the role is unique under the department, and the number of the role is unique in the system.
- the user determines (acquires) rights through its association with the role, one employee corresponds to one user, and one user corresponds to one employee.
- Role definition The role does not have the nature of group/class/category/post/job/work, but a non-collection nature, the role is unique, the role is an independent independent entity; in the enterprise application is equivalent Job number (The job number here is not a post, one post may have multiple employees at the same time, and one job number can only correspond to one employee at the same time).
- a company system can create the following roles: general manager, deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
- general manager deputy general manager 1, deputy general manager 2, Beijing sales manager, Beijing sales manager, Shanghai sales engineer 1, Shanghai sales Engineer 2, Shanghai Sales Engineer 3, Shanghai Sales Engineer 4, Shanghai Sales Engineer 5...
- Zhang San serves as the company's deputy general manager 2, and also serves as a sales manager in Beijing, then Zhang The three roles to be associated are Deputy General Manager 2 and Beijing Sales Manager. Zhang San has the rights to these two roles.
- roles are group/class/post/position/work type, and one role can correspond to multiple users.
- the concept of "role" in this application is equivalent to the post number/station number, and is similar to the role in the film and television drama: a character can only be played by one actor at the same time (childhood, juvenile, middle-aged). And an actor may be decorated with multiple angles.
- the user When the user moves across departments, the user is associated with the role in the original department, and the user is associated with the role in the new department. After the role is created, you can associate the role in the process of creating the user, or you can associate it at any time after the user is created. After the user associates the role, the relationship with the role can be released at any time, and the relationship with other roles can be established at any time.
- Selecting a form to be authorized displays the authorized fields in the form that require authorization to view the field values through third-party fields, where it refers to the authorized field.
- the contract form includes the customer name, the number of items, and the unit price of the item.
- the viewing authority of the field value of the authorized field of the form of the authorized object is displayed as the last authorized time of the field value of the authorized field of the form of the authorized object.
- View authority when the authorized object is two or more, the view permission of the field value of the authorized field of the form of the authorized object is not displayed.
- the authorized object is one
- the authorized permission of the field of the authorized field of the authorized object of the authorized object is displayed, and the authorization time is authorized for the authorized object.
- the privilege of the privilege is checked, and the field value of the authorized field of the form of the authorized object needs to be authorized.
- the viewing authority of the field value of the authorized field of the contract form of the Chinese member 1 is the last authorized authorized operator Zhang 2, and the authorized time is May 6, 2017, 15:00.
- an operator needs to perform authorization operations on 100 roles, but on the same day, the operator only completes the authorization operation of 70 roles.
- the operator can be filtered by the authorized operator or The view right of the field value of the last authorized field of the form is authorized to find the role that needs authorization. For another example, by viewing the last time the viewing permission of the field value of the authorized field of the form of a certain role is authorized, it can be known that the viewing right of the field value of the authorized field of the form has not been changed, which is helpful for judging. Whether you need to authorize the view permission of the field value of the authorized field of the form again.
- One or more third party fields are selected for each authorized field, the third party field being a field in the selected form, and the options of the third party field include one or more.
- the third-party field selected for the authorized field "customer name” is "contract signing time”; and the third-party field selected for the authorized field “item unit price” is "customer-owned industry”.
- the third party field includes a time property field and an untime property field, the option of the time property field being determined by an authorized operator; the field value of the non-temporal property field is determined by the selection (such as a field of the industry field to which the customer form belongs) Values are available in manufacturing, finance, aviation, etc., such fields are customer level, department, etc., not manually filled in) or automatically determined (such as form creator, record holder, billing role, system maker, etc.
- the field value of its field is automatically determined/save according to the relevant rules, such as the creator (field) alternative is a system-wide person, but the creator is the current person automatically obtained according to the rules when creating the form) All alternatives (all alternatives to the field value of this field) when determining or automatically determined are selected as options for the non-time property field (this non-time property field).
- the options of the time property field include one or more of the following: a time period from a current time back to a fixed time length to a current time period, a time period from a start time to a current time, and a deadline time to The time period of the system initial time, the time period from the start time to the cutoff time, the time period in which the time field value is null, and the time period from the system initial time to the current time, the time from the system initial time to the current time
- the segment includes a time period in which the time field value is a null value.
- the time period from the current time back to a fixed time length to the current time, the time period from the start time to the current time, the time period from the cutoff time to the system initial time, and the start time to the cutoff time The time period of time is determined by the authorized operator; the time period in which the time field value is null and the time period from the initial time of the system to the current time are determined by the authorized operator. As shown in FIG. 7, among the four options of the contract signing time displayed after the third party field is selected as the "contract signing time", the time period from the start time to the current time is filled in by the authorized operator, that is, "from From January 1st, 2016 to present, the time period when the time field value is null is selected by the authorized operator.
- the following examples illustrate the above six time periods: the time point obtained by reversing a fixed time length from the current time to the current time period. For example, on June 20, 2017, employee A is authorized to view the signing time (contract signing time) from the time point of 6 days from June 20, 2017 to the time of June 20, 2017.
- the time period from the start time to the current time is dynamic.
- employee A is authorized to view the signing time (contract signing time) is the customer name of the contract form (contract) from February 1, 2015 to the current (current), then A can view the signing Time (contract signing time) is the customer name of all contract forms (contracts) from February 1, 2015 to May 1, 2015; on May 2, 2015, employee A can view the contract signing time as 2015
- the customer name of all contracts from February 1st to May 2nd, 2015 (further, the start time can be expressed as not including the start time, and when the start time is not included, the employee A cannot view the contract signing time.
- the customer name of the contract dated February 1, 2015 only the customer name of all contracts signed after February 1, 2015 can be viewed.
- the time period from the deadline to the initial time of the system For example, for employee A to authorize the contract name (contract signing time) is the customer name of the contract form (contract) from February 1, 2015 to the system initial time, then A can check the signing time (contract signing time) is 2015.
- employee A can view the contract name of the customer name of all contracts before the deadline and deadline. , or employee A can view the customer name of all contracts before the deadline for contract signing).
- the time period from the start time to the deadline For example, if employee A is authorized to view the customer name of the contract form (contract) for the signing time (contract signing time) from February 1, 2015 to June 1, 2015, then A can check the signing time (contract signing time). The customer name for all contract forms (contracts) from February 1, 2015 to June 1, 2015.
- the time period in which the time field value is null For example, the delivery time within the contract is not required, and the delivery time in some contract forms (contracts) is not filled out, and employee A is authorized to view the contract form for the time field value of the delivery time value that is null. Customer name, then A can view the customer name of all contract forms (contracts) that have not filled in the delivery time.
- the time period from the system initial time to the current time is dynamic. For example, on June 1, 2017, employee A is authorized to view the customer name of the contract form (the contract signing time) from the initial time of the system to the current time. On June 1, 2017, A can view the signing.
- the time (contract signing time) is the customer name of all contract forms (contracts) from the system initial time to June 1, 2017. On June 2, 2017, A can check the signing time (contract signing time) for the initial system. The customer name for all contract forms (contracts) until June 2, 2017, and so on.
- the time period from the initial time of the system to the current time includes a time period in which the time field value is a null value; (further, the specific system initial time and the current time time value may not be set, as long as the system is set to the employee A This setting of the initial time to the current time period, the employee A can view the contract signing time in the system is the customer name of all contracts including the time null value at any time).
- the viewing rights of the field values of the authorized fields of the form data corresponding to each option of each third-party field are respectively authorized.
- “empty” and “electrical” are selected in the form data corresponding to the industry to which the customer belongs after the third-party field is selected as “customer-owned industry”, where “empty” refers to the industry's null value; That is, the clerk 1 can check the price of the item price of the contract in the electrical industry (the industry to which the customer belongs is an electric appliance) and the industry in which the industry is null (the customer's industry is null, or the customer's industry field has no field value/content). Assuming that "unrestricted” is selected in FIG. 8, the clerk 1 can view the price of the item price of the contract of all industries (including subsequently added industries) such as electric appliances, machinery, and the like, and the field value of the customer's industry is "empty”.
- the display mode includes: (1) displaying the field corresponding to the field value, but hiding the field value with the concealer; (2) the field value and the field corresponding to the field value are not displayed.
- the contact information and the contact information displayed by the user when viewing the contract form are displayed as “*”.
- a method for authorizing a field value of a form field by a third party field includes: selecting one or more authorized objects.
- the authorized object includes one or more of a person, a user, a group, a class, and a role, the role is an independent individual, not a group/class, and a role can only associate with a unique user in the same period, and one A user associates one or more roles.
- the role belongs to the department, and the role is unique under the department.
- the role is authorized according to the work content of the role, and the user obtains the permission by associating the role. When a user moves across departments, the user is first associated with the role in the original department, and then the user is associated with the role in the new department.
- Selecting a form to be authorized displays the authorized fields in the form that require authorization to view the field values through third-party fields, where it refers to the authorized field.
- the viewing authority of the field value of the authorized field of the form of the authorized object is displayed as the last authorized time of the field value of the authorized field of the form of the authorized object.
- View authority when the authorized object is two or more, the view permission of the field value of the authorized field of the form of the authorized object is not displayed.
- the authorized object is one
- the authorized permission of the field of the authorized field of the authorized object of the authorized object is displayed, and the authorization time is authorized for the authorized object.
- the privilege of the privilege is checked, and the field value of the authorized field of the form of the authorized object needs to be authorized.
- Selecting a template selecting an existing authorized object or a created template as an authorization template, and updating the viewing permission of the field value of the authorized field of the authorized object to the field value of the corresponding field in the authorization template. Permissions. As shown in Figure 11, you have selected Template 1 as an authorization template.
- Determining whether to continue modifying after selecting the template if yes, determining, for each authorized field, a third-party field for each authorized field (the determination here means increasing, decreasing or not increasing or not decreasing), the third-party field is a field in the selected form
- the third-party field option includes one or more; respectively, authorizing the view permission of the field value of the authorized field of the form data corresponding to each option of each third-party field, and then saving; if not, saving .
- the third party field includes a time property field and an untime property field, the option of the time property field being determined by an authorized operator; the field value of the non-temporal property field is determined by the selection (such as a field of the industry field to which the customer form belongs) Values are available in manufacturing, finance, aviation, etc., such fields are customer level, department, etc., not manually filled in) or automatically determined (such as form creator, record holder, billing role, system maker, etc.
- the field value of its field is automatically determined/save according to the relevant rules, such as the creator (field) alternative is a system-wide person, but the creator is the current person automatically obtained according to the rules when creating the form) All alternatives (all alternatives to the field value of this field) when determining or automatically determined are selected as options for the non-time property field (this non-time property field).
- the options of the time property field include one or more of the following: a time period from a current time back to a fixed time length to a current time period, a time period from a start time to a current time, and a deadline time to The time period of the system initial time, the time period from the start time to the cutoff time, the time period in which the time field value is null, and the time period from the system initial time to the current time, the time from the system initial time to the current time
- the segment includes a time period in which the time field value is a null value.
- the display mode includes: (1) displaying the field corresponding to the field value, but hiding the field value with the concealer; (2) the field value and the field corresponding to the field value are not displayed.
- a method for authorizing a field value of a form field by a third party field includes: selecting one or more authorized objects.
- the authorized object includes one or more of a person, a user, a group, a class, and a role, the role is an independent individual, not a group/class, and a role can only associate with a unique user in the same period, and one A user associates one or more roles.
- the role belongs to the department, and the role is unique under the department.
- the role is authorized according to the work content of the role, and the user obtains the permission by associating the role. When a user moves across departments, the user is first associated with the role in the original department, and then the user is associated with the role in the new department.
- the modification authority of the field value of the authorized field of the form of the authorized object is displayed as the last authorized time of the field value of the authorized field of the form of the authorized object is saved. Modify permission; when the authorized object is two or more, the modification permission of the field value of the authorized field of the form of the authorized object is not displayed.
- the authorized object is one
- the authorized authority of the field value of the authorized field of the form of the authorized object is displayed, and the authorized operator and authorized time are authorized for the authorized object.
- the privilege of the privilege is checked, and the field value of the authorized field of the form of the authorized object needs to be authorized.
- One or more third party fields are selected for each authorized field, the third party field being a field in the selected form, and the options of the third party field include one or more.
- the third party field selected for the authorized field "customer name” is "contract signing time, contract signer”; the third party field selected for the authorized field “item quantity” is "contract” level”.
- the third party field includes a time property field and an untime property field, the option of the time property field being determined by an authorized operator; the field value of the non-temporal property field is determined by the selection (such as a field of the industry field to which the customer form belongs) Values are available in manufacturing, finance, aviation, etc., such fields are customer level, department, etc., not manually filled in) or automatically determined (such as form creator, record holder, billing role, system maker, etc.
- the field value of its field is automatically determined/save according to the relevant rules, such as the creator (field) alternative is a system-wide person, but the creator is the current person automatically obtained according to the rules when creating the form) All alternatives (all alternatives to the field value of this field) when determining or automatically determined are selected as options for the non-time property field (this non-time property field).
- the options of the time property field include one or more of the following: a time period from a current time back to a fixed time length to a current time period, a time period from a start time to a current time, and a deadline time to The time period of the system initial time, the time period from the start time to the cutoff time, the time period in which the time field value is null, and the time period from the system initial time to the current time, the time from the system initial time to the current time
- the segment includes a time period in which the time field value is a null value.
- the modification authority of the field value of the authorized field of the form data corresponding to each option of each third-party field is separately authorized.
- the difference between the field and the field value with the modification permission is displayed. If the field with the modification permission and the field value are displayed in black, the field and field value without modification permission, or the field with no modification permission are displayed. The value is displayed in gray.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Business, Economics & Management (AREA)
- Data Mining & Analysis (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computing Systems (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Storage Device Security (AREA)
- Document Processing Apparatus (AREA)
- Time Recorders, Dirve Recorders, Access Control (AREA)
Abstract
Description
Claims (10)
- 通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,包括:选择一个或多个被授权对象;选择一个要进行授权的表单,显示出该表单中需要通过第三方字段控制其字段值的查看权限授权的被授权字段;分别为每个被授权字段选择一个或多个第三方字段,所述第三方字段为所选表单中的字段,所述第三方字段的选项包括一个或多个;分别对每个第三方字段的每个选项对应的表单数据的被授权字段的字段值的查看权限进行授权。
- 根据权利要求1所述的通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,所述被授权对象包括人、用户、组、类、角色中的一种或多种,所述角色是独立的个体,而非组/类,同一时段一个角色只能关联唯一的用户,而一个用户关联一个或多个角色。
- 根据权利要求2所述的通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,所述角色归属于部门,该角色在该部门下唯一,根据角色的工作内容对角色进行授权,用户通过关联角色获得权限。
- 根据权利要求3所述的通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,用户跨部门调岗时,先取消用户与原部门内的角色的关联,再将用户与新部门内的角色进行关联。
- 根据权利要求1所述的通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,所述第三方字段包括时间性质字段和非时间性质字段,所述时间性质字段的选项由授权操作者确定;所述非时间性质字段的字段值是由选择确定或自动确定的,将选择确定或自动确定时的所有备选项作为非时间性质字段的选项。
- 根据权利要求5所述的通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,所述时间性质字段的选项包括以下的一个或多个:从当前时间倒推一个固定时间长度得到的时间点到当前时间的时间段、从起始时间到当前时间的时间段、从截止时间到系统初始时间的时间段、从起始时间至截止时间的时间段、时间字段值为空值的时间段和从系统初始时间到当前时间的时间段,所述从系统初始时间到当前时间的时间段包括时间字段值为空值的时间段。
- 根据权利要求1所述的通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,当被授权对象为一个时,将所被授权对象的该表单的被授权字段的字段值的查看权限显示为该被授权对象的该表单的被授权字段的字段值的最近一次被授权时保存的查看权限;当被授权对象为两个或以上时,不显示所述被授权对象的该表单的被授权字段的字段值的查看权限。
- 根据权利要求1所述的通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,对于不具备查看权限的字段值,其显示方式包括:(1)显示该字段值对应的字段,但以隐藏符隐藏字段值;(2)该字段值及该字段值对应的字段均不显示。
- 通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,包括:选择一个或多个被授权对象;选择一个要进行授权的表单,显示出该表单中需要通过第三方字段控制其字段值的查看权限授权的被授权字段;选择模板:选择一个现有的被授权对象或已创建模板作为授权模板,将所述被授权对象的该表单的被授权字段的字段值的查看权限更新为授权模板中相应字段的字段值的查看权限;判断选择模板后是否继续修改:若是,则分别为每个被授权字段确定第三方字段,所述第三方字段为所选表单中的字段,所述第三方字段的选项包括一个或多个;分别对每个第三方字段的每个选项对应的表单数据的被授权字段的字段值的查看权限进行授权,然后保存;若否,则保存。
- 通过第三方字段对表单字段的字段值进行授权的方法,其特征在于,包括:选择一个或多个被授权对象;选择一个要进行授权的表单,显示出该表单中需要通过第三方字段控制其字段值的修改权限授权的被授权字段;分别为每个被授权字段选择一个或多个第三方字段,所述第三方字段为所选表单中的字段,所述第三方字段的选项包括一个或多个;分别对每个第三方字段的每个选项对应的表单数据的被授权字段的字段值的修改权限进行授权。
Priority Applications (12)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA3069597A CA3069597A1 (en) | 2017-07-11 | 2018-07-10 | Method for authorizing field value of form field by means of third party field |
PE2020000011A PE20200344A1 (es) | 2017-07-11 | 2018-07-10 | Procedimiento para autorizar un valor de campo de un campo de formulario por medio de un campo de terceros |
MX2020000256A MX2020000256A (es) | 2017-07-11 | 2018-07-10 | Procedimiento para autorizar un valor de campo de un campo de formulario por medio de un campo de terceros. |
EP18831297.9A EP3654193A4 (en) | 2017-07-11 | 2018-07-10 | METHOD FOR AUTHORIZING A FIELD VALUE OF A FORM FIELD USING A THIRD FIELD |
BR112020000593-2A BR112020000593A2 (pt) | 2017-07-11 | 2018-07-10 | método para autorizar o valor de campo de formulário por meio de campo de terceiros |
US16/630,412 US11775687B2 (en) | 2017-07-11 | 2018-07-10 | Method for authorizing field value of form field by means of third party field |
EA202090233A EA202090233A1 (ru) | 2017-07-11 | 2018-07-10 | Способ предоставления прав в отношении значений полей формы посредством полей третьего лица |
JP2020500610A JP7329218B2 (ja) | 2017-07-11 | 2018-07-10 | 第三者フィールドを介してフォームフィールドのフィールド値を承認する方法 |
KR1020207001597A KR20200017514A (ko) | 2017-07-11 | 2018-07-10 | 제3자 필드를 통하여 폼 필드의 필드값에 대하여 권한을 부여하는 방법 |
AU2018301083A AU2018301083A1 (en) | 2017-07-11 | 2018-07-10 | Method for authorizing field value of form field by means of third party field |
PH12020500008A PH12020500008A1 (en) | 2017-07-11 | 2020-01-02 | Method for authorizing field value of form field by means of third party field |
CONC2020/0000181A CO2020000181A2 (es) | 2017-07-11 | 2020-01-09 | Procedimiento para autorizar un valor de campo de un campo de formulario por medio de un campo de terceros |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710562793.XA CN107358093A (zh) | 2017-07-11 | 2017-07-11 | 通过第三方字段对表单字段的字段值进行授权的方法 |
CN201710562793.X | 2017-07-11 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019011255A1 true WO2019011255A1 (zh) | 2019-01-17 |
Family
ID=60292941
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/095204 WO2019011255A1 (zh) | 2017-07-11 | 2018-07-10 | 通过第三方字段对表单字段的字段值进行授权的方法 |
Country Status (14)
Country | Link |
---|---|
US (1) | US11775687B2 (zh) |
EP (1) | EP3654193A4 (zh) |
JP (1) | JP7329218B2 (zh) |
KR (1) | KR20200017514A (zh) |
CN (2) | CN107358093A (zh) |
AU (1) | AU2018301083A1 (zh) |
BR (1) | BR112020000593A2 (zh) |
CA (1) | CA3069597A1 (zh) |
CO (1) | CO2020000181A2 (zh) |
EA (1) | EA202090233A1 (zh) |
MX (1) | MX2020000256A (zh) |
PE (1) | PE20200344A1 (zh) |
PH (1) | PH12020500008A1 (zh) |
WO (1) | WO2019011255A1 (zh) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107358093A (zh) * | 2017-07-11 | 2017-11-17 | 成都牵牛草信息技术有限公司 | 通过第三方字段对表单字段的字段值进行授权的方法 |
CN107330307A (zh) * | 2017-07-16 | 2017-11-07 | 成都牵牛草信息技术有限公司 | 一种表单数据操作权限授权方法 |
CN109977697A (zh) * | 2019-04-03 | 2019-07-05 | 陕西医链区块链集团有限公司 | 一种区块链的数据授权方法 |
CN112883418B (zh) * | 2021-02-03 | 2024-02-09 | 中国工商银行股份有限公司 | 数据库的表字段值保护方法及装置 |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101226573A (zh) * | 2007-01-16 | 2008-07-23 | 北京书生国际信息技术有限公司 | 一种控制电子文档的访问权限的方法 |
US20090019516A1 (en) * | 2006-01-31 | 2009-01-15 | Koninklijke Philips Electronics N.V. | Role-based access control |
CN102236659A (zh) * | 2010-04-27 | 2011-11-09 | 中国银联股份有限公司 | 使用复杂条件从数据源进行数据过滤的方法和系统 |
CN104408339A (zh) * | 2014-12-18 | 2015-03-11 | 山东钢铁股份有限公司 | 一种信息系统中权限管理方法 |
CN104881506A (zh) * | 2015-06-29 | 2015-09-02 | 山东钢铁股份有限公司 | 一种基于数据库可配置的管理信息系统权限控制方法 |
CN106570406A (zh) * | 2016-10-27 | 2017-04-19 | 深圳前海微众银行股份有限公司 | 数据级权限配置方法及装置 |
CN107358093A (zh) * | 2017-07-11 | 2017-11-17 | 成都牵牛草信息技术有限公司 | 通过第三方字段对表单字段的字段值进行授权的方法 |
Family Cites Families (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1994018620A1 (en) * | 1993-02-08 | 1994-08-18 | Action Technologies, Inc. | Method and apparatus for managing business processes |
AU7735600A (en) * | 1999-10-01 | 2001-05-10 | Infraworks Corporation | Port blocking method and system |
US7251666B2 (en) * | 2000-02-01 | 2007-07-31 | Internet Business Information Group | Signature loop authorizing method and apparatus |
US20050210263A1 (en) * | 2001-04-25 | 2005-09-22 | Levas Robert G | Electronic form routing and data capture system and method |
US7237119B2 (en) * | 2003-06-30 | 2007-06-26 | At&T Intellectual Property, Inc. | Method, system and computer program for managing user authorization levels |
US20060218394A1 (en) * | 2005-03-28 | 2006-09-28 | Yang Dung C | Organizational role-based controlled access management system |
JP2007249912A (ja) | 2006-03-20 | 2007-09-27 | Fujitsu Ltd | 共用資源管理システム、共用資源管理方法、およびコンピュータプログラム |
JP2007280181A (ja) | 2006-04-10 | 2007-10-25 | Fuji Xerox Co Ltd | 電子文書の処理プログラム及び電子文書の処理装置 |
US8527539B2 (en) * | 2007-01-24 | 2013-09-03 | Oracle International Corporation | System and method for a central index for RFID data with data privilege indicia |
US20160217488A1 (en) * | 2007-05-07 | 2016-07-28 | Miles Ward | Systems and methods for consumer-generated media reputation management |
CN100498792C (zh) * | 2007-06-08 | 2009-06-10 | 北京神舟航天软件技术有限公司 | 数据库表行级数据的自主访问控制方法 |
CN101699478A (zh) | 2009-10-28 | 2010-04-28 | 金蝶软件(中国)有限公司 | 权限管理方法、装置和一种管理系统 |
JP2011237927A (ja) | 2010-05-07 | 2011-11-24 | Canon Software Inc | ワークフロー制御装置、ワークフロー制御システム、ワークフロー制御方法、ワークフロー制御プログラムおよび記録媒体。 |
US9129238B2 (en) * | 2010-05-12 | 2015-09-08 | Winshuttle, Llc | Dynamic web services work flow system and method |
US9141442B1 (en) * | 2010-09-08 | 2015-09-22 | Dell Software Inc. | Automated connector creation for provisioning systems |
JP5683939B2 (ja) | 2010-12-22 | 2015-03-11 | 株式会社野村総合研究所 | 文書管理装置 |
JP5814639B2 (ja) * | 2011-06-09 | 2015-11-17 | キヤノン株式会社 | クラウドシステム、クラウドサービスのライセンス管理方法、およびプログラム |
CN102316216A (zh) * | 2011-09-07 | 2012-01-11 | 宇龙计算机通信科技(深圳)有限公司 | 一种终端自适应角色的方法及终端 |
US20130246995A1 (en) * | 2012-03-13 | 2013-09-19 | Outsystems - Software Em Rede S.A. | Systems, methods, and apparatus for model-based security control |
US20140025425A1 (en) * | 2012-07-17 | 2014-01-23 | Winshuttle, Llc | Bulk business workflow systems and methods |
US20140040153A1 (en) * | 2012-08-06 | 2014-02-06 | CareDirector USA LLC | System and Method for Providing a Configurable Web Portal Builder Interfacing with a Customer Relationship Management System |
US9178886B2 (en) * | 2012-08-29 | 2015-11-03 | Red Hat Israel, Ltd. | Flattening permission trees in a virtualization environment |
US10146850B2 (en) * | 2012-10-30 | 2018-12-04 | FHOOSH, Inc. | Systems and methods for collecting, classifying, organizing and populating information on electronic forms |
US9032545B1 (en) * | 2012-12-19 | 2015-05-12 | Emc Corporation | Securing visual information on images for document capture |
US10320903B2 (en) * | 2013-09-16 | 2019-06-11 | Vii Network, Inc. | Web and mobile-based platform that unites workflow management and asynchronous video collaboration for healthcare |
CN104463005A (zh) | 2013-09-25 | 2015-03-25 | 天津书生投资有限公司 | 一种控制电子文档的访问权限的方法 |
US9461972B1 (en) * | 2014-03-19 | 2016-10-04 | NetSuite Inc. | Intelligently designed user interface based on user behavior |
CN104660599B (zh) | 2015-02-14 | 2016-02-10 | 张晓� | 一种基于角色的访问控制方法 |
US20160371062A1 (en) * | 2015-06-17 | 2016-12-22 | J. Wood Software Services LLC | Method For The Automatic Presentation And Interaction Of A Data-Form User-Interface From Object-Model Metadata Under Media And Security Constraints |
US9842221B2 (en) * | 2015-06-26 | 2017-12-12 | Sap Se | Role analyzer and optimizer in database systems |
US20180246705A1 (en) * | 2015-08-18 | 2018-08-30 | Entit Software Llc | User interface behavior based rules generation |
CN105303084A (zh) * | 2015-09-24 | 2016-02-03 | 北京奇虎科技有限公司 | 权限管理系统及方法 |
US10032045B2 (en) * | 2015-10-30 | 2018-07-24 | Raytheon Company | Dynamic runtime field-level access control using a hierarchical permission context structure |
US20210182870A1 (en) * | 2015-11-17 | 2021-06-17 | Schneider Enterprise Resources, LLC | Geolocation compliance for a mobile workforce |
CN105653977B (zh) * | 2015-12-28 | 2019-07-05 | 上海瀚银信息技术有限公司 | 一种菜单权限配置方法及系统 |
CN107180334A (zh) * | 2017-04-29 | 2017-09-19 | 成都牵牛草信息技术有限公司 | 基于角色对用户一对一的工作流控制方法和系统 |
CN107203870A (zh) * | 2017-05-23 | 2017-09-26 | 成都牵牛草信息技术有限公司 | 工作流审批节点按部门设置审批角色的方法 |
CN107292588A (zh) * | 2017-07-01 | 2017-10-24 | 成都牵牛草信息技术有限公司 | 根据表单字段值对表单操作权限进行分别授权的方法 |
CN107330344A (zh) * | 2017-07-01 | 2017-11-07 | 成都牵牛草信息技术有限公司 | 一种表单的关联信息授权方法 |
CN107301336A (zh) * | 2017-07-04 | 2017-10-27 | 成都牵牛草信息技术有限公司 | 基于表单时间性质字段的表单授权方法 |
CN107315931A (zh) * | 2017-07-05 | 2017-11-03 | 成都牵牛草信息技术有限公司 | 表单字段值操作权限授权方法 |
CN107340951A (zh) * | 2017-07-13 | 2017-11-10 | 成都牵牛草信息技术有限公司 | 基于角色获取的表单数据的授权方法 |
CN107330307A (zh) * | 2017-07-16 | 2017-11-07 | 成都牵牛草信息技术有限公司 | 一种表单数据操作权限授权方法 |
CN107508798A (zh) * | 2017-07-28 | 2017-12-22 | 成都牵牛草信息技术有限公司 | 系统中邮箱账号和即时通讯账号内容操作权限的授权方法 |
CN107360083A (zh) * | 2017-07-29 | 2017-11-17 | 成都牵牛草信息技术有限公司 | 根据角色间的通讯关系预设即时通讯账号联系人及预设通讯录的方法 |
CN107480544A (zh) * | 2017-08-07 | 2017-12-15 | 成都牵牛草信息技术有限公司 | 统计列表操作权限授权方法 |
CN107395611A (zh) * | 2017-08-07 | 2017-11-24 | 成都牵牛草信息技术有限公司 | 系统中对授权操作者进行授权的方法 |
CN107480556A (zh) * | 2017-08-07 | 2017-12-15 | 成都牵牛草信息技术有限公司 | 基于列值对统计列表操作权限进行分别授权的方法 |
CN107480557A (zh) * | 2017-08-07 | 2017-12-15 | 成都牵牛草信息技术有限公司 | 显示所有系统使用者当前权限状态的授权方法 |
US20190050587A1 (en) * | 2017-08-08 | 2019-02-14 | Adobe Systems Incorporated | Generating electronic agreements with multiple contributors |
CN107370748A (zh) * | 2017-08-14 | 2017-11-21 | 成都牵牛草信息技术有限公司 | 基于时间段的操作记录查看权限的设置方法 |
US10681095B1 (en) * | 2018-01-17 | 2020-06-09 | Sure Market, LLC | Distributed messaging communication system integrated with a cross-entity collaboration platform |
US11475456B2 (en) * | 2018-07-24 | 2022-10-18 | Accenture Global Solutios Limited | Digital content and transaction management using an artificial intelligence (AI) based communication system |
US11381563B1 (en) * | 2020-09-29 | 2022-07-05 | Parallels International Gmbh | Automated methods and systems for granting complex permissions |
-
2017
- 2017-07-11 CN CN201710562793.XA patent/CN107358093A/zh active Pending
-
2018
- 2018-07-10 CA CA3069597A patent/CA3069597A1/en not_active Abandoned
- 2018-07-10 JP JP2020500610A patent/JP7329218B2/ja active Active
- 2018-07-10 AU AU2018301083A patent/AU2018301083A1/en not_active Abandoned
- 2018-07-10 US US16/630,412 patent/US11775687B2/en active Active
- 2018-07-10 PE PE2020000011A patent/PE20200344A1/es unknown
- 2018-07-10 MX MX2020000256A patent/MX2020000256A/es unknown
- 2018-07-10 EA EA202090233A patent/EA202090233A1/ru unknown
- 2018-07-10 WO PCT/CN2018/095204 patent/WO2019011255A1/zh unknown
- 2018-07-10 KR KR1020207001597A patent/KR20200017514A/ko not_active Application Discontinuation
- 2018-07-10 BR BR112020000593-2A patent/BR112020000593A2/pt not_active IP Right Cessation
- 2018-07-10 EP EP18831297.9A patent/EP3654193A4/en active Pending
- 2018-07-10 CN CN201810753143.8A patent/CN108920940B/zh active Active
-
2020
- 2020-01-02 PH PH12020500008A patent/PH12020500008A1/en unknown
- 2020-01-09 CO CONC2020/0000181A patent/CO2020000181A2/es unknown
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090019516A1 (en) * | 2006-01-31 | 2009-01-15 | Koninklijke Philips Electronics N.V. | Role-based access control |
CN101226573A (zh) * | 2007-01-16 | 2008-07-23 | 北京书生国际信息技术有限公司 | 一种控制电子文档的访问权限的方法 |
CN102236659A (zh) * | 2010-04-27 | 2011-11-09 | 中国银联股份有限公司 | 使用复杂条件从数据源进行数据过滤的方法和系统 |
CN104408339A (zh) * | 2014-12-18 | 2015-03-11 | 山东钢铁股份有限公司 | 一种信息系统中权限管理方法 |
CN104881506A (zh) * | 2015-06-29 | 2015-09-02 | 山东钢铁股份有限公司 | 一种基于数据库可配置的管理信息系统权限控制方法 |
CN106570406A (zh) * | 2016-10-27 | 2017-04-19 | 深圳前海微众银行股份有限公司 | 数据级权限配置方法及装置 |
CN107358093A (zh) * | 2017-07-11 | 2017-11-17 | 成都牵牛草信息技术有限公司 | 通过第三方字段对表单字段的字段值进行授权的方法 |
Also Published As
Publication number | Publication date |
---|---|
JP7329218B2 (ja) | 2023-08-18 |
CA3069597A1 (en) | 2019-01-17 |
PE20200344A1 (es) | 2020-02-17 |
EP3654193A4 (en) | 2021-07-28 |
BR112020000593A2 (pt) | 2020-07-14 |
US20200143068A1 (en) | 2020-05-07 |
PH12020500008A1 (en) | 2020-12-07 |
JP2020528600A (ja) | 2020-09-24 |
CN108920940A (zh) | 2018-11-30 |
EA202090233A1 (ru) | 2020-08-27 |
AU2018301083A1 (en) | 2020-02-06 |
CO2020000181A2 (es) | 2020-04-24 |
MX2020000256A (es) | 2021-03-02 |
CN107358093A (zh) | 2017-11-17 |
CN108920940B (zh) | 2021-10-29 |
KR20200017514A (ko) | 2020-02-18 |
EP3654193A1 (en) | 2020-05-20 |
US11775687B2 (en) | 2023-10-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019007260A1 (zh) | 表单字段值操作权限授权方法 | |
WO2018210245A1 (zh) | 工作流及其审批节点的表单字段操作权限的设定方法 | |
EP3633567A1 (en) | Method for setting up approval role according to department by approval node in workflow | |
WO2018210248A1 (zh) | 基于表单字段的工作流审批节点设置审批角色的方法 | |
WO2019011255A1 (zh) | 通过第三方字段对表单字段的字段值进行授权的方法 | |
US11507679B2 (en) | Authorization method for form related information | |
WO2019007292A1 (zh) | 基于角色的表单操作权限授权方法 | |
US11599656B2 (en) | Method for authorizing form data operation authority | |
WO2019029499A1 (zh) | 显示所有系统使用者当前权限状态的授权方法 | |
WO2019011304A1 (zh) | 基于角色获取的表单数据的授权方法 | |
JP7318894B2 (ja) | 統計列表の操作権限の承認方法 | |
WO2018205942A1 (zh) | 工作流审批节点按部门级别设置审批角色的方法 | |
WO2018192557A1 (zh) | 基于角色对用户的一对一的权限授权方法和系统 | |
WO2019019981A1 (zh) | 系统中用户在信息交流单元的权限的设置方法 | |
AU2018318803A1 (en) | Method for setting operating record viewing right based on time period | |
US11750616B2 (en) | Method for authorizing approval processes and approval nodes thereof for user | |
WO2018224023A1 (zh) | 系统中员工登录其账户后的权限显示方法 | |
WO2018205940A1 (zh) | 基于角色对用户的一对一的组织结构图生成及应用方法 | |
WO2019011162A1 (zh) | 快捷功能设置方法 | |
WO2019007338A1 (zh) | 基于表单时间性质字段的表单授权方法 | |
WO2019001322A1 (zh) | 基于角色的菜单授权方法 | |
WO2019029502A1 (zh) | 系统中对授权操作者进行授权的方法 | |
WO2019007261A1 (zh) | 表单中的角色性质字段的字段值获取方法 | |
JPWO2019011255A5 (zh) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18831297 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2020500610 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 3069597 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20207001597 Country of ref document: KR Kind code of ref document: A |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112020000593 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 2018301083 Country of ref document: AU Date of ref document: 20180710 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2018831297 Country of ref document: EP Effective date: 20200211 |
|
ENP | Entry into the national phase |
Ref document number: 112020000593 Country of ref document: BR Kind code of ref document: A2 Effective date: 20200110 |