CN118034647A - Task processing method, device and medium in workflow oriented to low-code platform - Google Patents
Task processing method, device and medium in workflow oriented to low-code platform Download PDFInfo
- Publication number
- CN118034647A CN118034647A CN202311767591.0A CN202311767591A CN118034647A CN 118034647 A CN118034647 A CN 118034647A CN 202311767591 A CN202311767591 A CN 202311767591A CN 118034647 A CN118034647 A CN 118034647A
- Authority
- CN
- China
- Prior art keywords
- node
- task
- label
- workflow
- processor
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 14
- 238000012545 processing Methods 0.000 claims abstract description 94
- 230000000977 initiatory effect Effects 0.000 claims abstract description 21
- 238000000034 method Methods 0.000 claims description 52
- 230000008859 change Effects 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 12
- 238000003860 storage Methods 0.000 claims description 12
- 238000005516 engineering process Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 15
- 238000004891 communication Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Software Systems (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Educational Administration (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- General Business, Economics & Management (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The disclosure provides a task processing method, device and medium in workflow oriented to a low-code platform, and relates to the technical fields of task processing, information management and the like in the low-code platform. The specific implementation scheme comprises the following steps: acquiring a workflow initiated by a user based on a workflow template preconfigured in a platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node can determine the label of the task processor; determining a label of a task processor of a node in the workflow based on configuration information of the node; positioning the identification of the task processor of the node based on the label of the task processor of the node; and initiating a processing task corresponding to the node based on the identification of the task processor of the node. The technology disclosed by the disclosure can effectively ensure the independence of the workflow and the flexibility of use on the premise of ensuring the accurate and effective processing of the tasks of each node.
Description
Technical Field
The disclosure relates to the technical field of computers, in particular to the technical fields of task processing, information management and the like in a low-code platform, and particularly relates to a task processing method, device and medium in a workflow for the low-code platform.
Background
In many platforms, such as low code platforms, personnel are very important management dimensions. In a scenario involving task handling, personnel are all required to participate.
In many platforms of the prior art, personnel management is flattened integrated management. In the scenario configured in the platform, the task is configured directly to the corresponding task handler to be fixedly processed by the task handler.
Disclosure of Invention
The disclosure provides a task processing method, device and medium in workflow oriented to a low-code platform.
According to an aspect of the present disclosure, there is provided a task processing method in a workflow for a low-code platform, including:
Acquiring a workflow initiated by a user based on a workflow template preconfigured in a platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node can determine the label of the task processor;
determining a label of a task handler of a node in the workflow based on configuration information of the node;
Positioning the identification of the task processor of the node based on the label of the task processor of the node;
and initiating a processing task corresponding to the node based on the identification of the task processor of the node.
According to another aspect of the present disclosure, there is provided a task processing device in a workflow for a low-code platform, including:
The acquisition module is used for acquiring a workflow initiated by a user based on a workflow template preconfigured in the platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node can determine the label of the task processor;
The determining module is used for determining labels of task processing persons of the nodes in the workflow based on configuration information of the nodes;
the positioning module is used for positioning the identification of the task processor of the node based on the label of the task processor of the node;
And the initiating module is used for initiating the processing task corresponding to the node based on the identification of the task processor of the node.
According to still another aspect of the present disclosure, there is provided an electronic apparatus including:
At least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the aspects and methods of any one of the possible implementations described above.
According to yet another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method of the aspects and any possible implementation described above.
According to yet another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method of the aspects and any one of the possible implementations described above.
According to the technology disclosed by the invention, on the premise of ensuring that tasks of all nodes are accurately and effectively processed, the independence of the workflow and the flexibility of use can be effectively ensured.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is a schematic diagram according to a first embodiment of the present disclosure;
FIG. 2 is a schematic diagram according to a second embodiment of the present disclosure;
FIG. 3 is a schematic diagram according to a third embodiment of the present disclosure;
FIG. 4 is a schematic diagram according to a fourth embodiment of the present disclosure;
FIG. 5 is a schematic diagram according to a fifth embodiment of the present disclosure;
fig. 6 is a block diagram of an electronic device for implementing the methods of embodiments of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It will be apparent that the described embodiments are some, but not all, of the embodiments of the present disclosure. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments in this disclosure without inventive faculty, are intended to be within the scope of this disclosure.
It should be noted that, the terminal device in the embodiments of the present disclosure may include, but is not limited to, smart devices such as a mobile phone, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a wireless handheld device, and a Tablet Computer (Tablet Computer); the display device may include, but is not limited to, a personal computer, a television, or the like having a display function.
In addition, the term "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
FIG. 1 is a schematic diagram according to a first embodiment of the present disclosure; as shown in fig. 1, the present embodiment provides a task processing method in a workflow facing a low-code platform, which specifically includes the following steps:
s101, acquiring a workflow initiated by a user based on a workflow template preconfigured in a platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node can determine the label of the task processor;
s102, determining labels of task processors of nodes in a workflow based on configuration information of the nodes;
S103, positioning the identification of the task processor of the node based on the label of the task processor of the node;
S104, initiating a processing task corresponding to the node based on the identification of the task processor of the node.
The task processing method of the workflow can be applied to any task processing platform, for example, can be applied to a low-code platform, and is used for processing tasks in the workflow.
In the workflow processing method for the low-code platform, in the task processing process, a user can only determine the label of a task processor based on the configuration information of the nodes configured in the workflow initiated by the workflow template pre-configured in the platform, and does not bind the task processor specifically. When the task is executed, the identification of the task processor of the node is positioned according to the label of the task processor of the node, and then the processing task corresponding to the node is initiated based on the identification of the task processor of the node.
In the task processing method in the workflow facing the low-code platform of the embodiment, due to the plurality of nodes with the circulation sequence relationship in the workflow template and the configuration information of each node; and the configuration information of each node can determine the label of the task processor without binding a specific task processor. Furthermore, in the workflow initiated based on the pre-configured workflow template, only the label of the task processor can be determined, but the specific task processor is not bound, so that the decoupling of the workflow and the specific task processor can be effectively ensured, the independence of the workflow and the flexibility in execution are improved, and the limitation of the bound task processor is avoided. In the task processing process, the labels of the task processing persons of the nodes can be based, the identifications of the task processing persons of the nodes can be positioned, and further, the processing tasks corresponding to the nodes can be initiated based on the identifications of the task processing persons of the nodes, and the tasks of the nodes can be accurately and effectively processed. Therefore, the technical scheme of the embodiment can effectively ensure the independence of the workflow and the flexibility of use on the premise of ensuring the accurate and effective processing of the tasks of each node.
FIG. 2 is a schematic diagram according to a second embodiment of the present disclosure; as shown in fig. 2, the present embodiment further describes the technical solution of the present disclosure in more detail on the basis of the technical solution of the embodiment shown in fig. 1. As shown in fig. 2, the task processing method in the workflow facing the low-code platform in this embodiment may specifically include the following steps:
S201, acquiring a workflow initiated by a user based on a workflow template preconfigured in a platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node can determine the label of the task processor;
Optionally, before this step S201, it may include: the workflow template is configured in a platform, the workflow template comprises a plurality of nodes with a circulation sequence relation, and each node is configured with a label of a task processor. That is, in this embodiment, the configuration information of each node includes a label in which a task processor is disposed for each node. By the configuration mode, the workflow template with very strong flexibility can be efficiently generated, task processing persons are not bound in the workflow template, and only the labels of the task processing persons are configured, so that the task processing persons of all nodes in the workflow template can be decoupled from the workflow template, the flexibility of using the workflow template is effectively improved, the workflow template is not influenced by the variation of any task processing person, and the stability of the workflow template is effectively ensured.
The tag in this embodiment is not an identifier of the task processor, and is attribute information corresponding to the task processor. For example, dimension information and type information in the dimension may be employed to collectively identify the tag of the task processor.
For example, the label of the task handler in this embodiment may include at least one type of identification in at least one dimension; the at least one dimension includes at least one of a role, a job level, and a department. By the method, the attribute information of the task processing person can be accurately and efficiently identified.
Based on the above, it can be known that in the platform of the present embodiment, management of personnel can be managed from multiple dimensions such as roles, job levels, departments, and the like. For example, from an operational level perspective, the roles of all people on a platform may include: various types of executives, manager, operators, leaders, and the like. Or may be classified from the job types of the work mainly responsible in the company corresponding to the platform, and may include: cleaning, maintenance, pre-sale, after-sale, and the like. Or roles may be defined from other angles as well. Regardless of how the roles are partitioned, the role architecture of the platform can be obtained based on the idea of role partitioning. Departments may refer to a framework of division of personnel within a company corresponding to a platform, such as various types of research and development, production, testing, and operation departments, and each department may further divide down into finer-grained departments. The department architecture of the platform can be obtained based on the idea of division of departments. Similarly, a similar manner can be adopted to obtain a job level architecture of the platform, such as various types of L1 level, L2 level and the like, and the higher the level is, the stronger the business capability of corresponding personnel can be. The architecture of each dimension may be identified using a tree structure.
S202, for each node, acquiring a label of a task processor of the node from configuration information of the node in a pre-configured workflow template;
as described in the above steps, in the scenario of the present embodiment, the labels of the task handlers of the respective nodes are directly configured in the workflow template. At this time, for each node, the label of the task handler of the node may be directly obtained from the workflow template.
This step is a specific implementation manner of step S102 in the embodiment shown in fig. 1. By the method, the labels of the task processing persons of the nodes can be accurately and efficiently obtained from the configuration information of the nodes in the workflow template.
S203, detecting whether the label comprises identification of types in at least two dimensions; if yes, go to step S205; otherwise, if not, executing step S204;
S204, detecting whether the label comprises one type of identification in one dimension or at least two types of identification in one dimension; if only one type of identification in one dimension is included, step S206 is performed; otherwise, if at least two types of identifiers in one dimension are included, step S207 is performed;
S205, responding to the label of the task processor to comprise the identification of the type in at least two dimensions, acquiring the identification of the person corresponding to the type in the dimension from the person information table corresponding to each dimension in the at least two dimensions, and taking the dimensions of at least two dimensions intersection of the identifications of the persons of the type, personnel corresponding to the type is provided with an intersection of the identification of (c); step S208 is performed;
Specifically, if the tag includes an identification of a type in at least two dimensions. Since the architectures of different dimensions are all managing the personnel in the platform. And the two-dimensional information itself is also a definition of at least two different dimensions for the same group of people. Therefore, when the label includes an identification of a type in at least two dimensions, it indicates that the task handler of the node satisfies the definition of the corresponding type in at least two dimensions at the same time. Therefore, in this scenario, an intersection of identifications of persons corresponding to types in each of at least two dimensions is taken as an identification of a task processor of the node.
S206, responding to the fact that the label of the task processor comprises a type of identification in one dimension, and acquiring the identification of the person corresponding to the type from the person information table corresponding to the dimension as the identification of the task processor of the node; step S208 is performed;
S207, responding to the fact that the labels of the task processor comprise at least two types of identifications in one dimension, acquiring identifications of people corresponding to each type in the at least two types from a personnel information table corresponding to the dimension, and taking a union of identifications of people corresponding to each type in the at least two types as identifications of task processor of the node; step S208 is performed;
because at least two types in the same dimension are juxtaposed, the labels comprise at least two types of identifications in one dimension, and the obtained is a union of identifications of people corresponding to each type in the at least two types, and the union is used as the identifications of task processing people of the node.
Steps S205-S207 of the present embodiment are processes for implementing a person-finding engine for locating the identity of the task handler of the node based on the label of the task handler of the node. In this embodiment, based on different labels, different people search engine methods may be adopted to implement a process of accurately and efficiently locating the task processor identifier of the node.
Optionally, before steps S205 to S207, it may further include: a personnel information table of each dimension in the platform is created or imported.
For example, the dimensions of the present embodiment may include at least one of a department dimension, a role dimension, and a job-level dimension. In practical applications, other dimensions may also be included. Under each dimension, an architecture for that dimension may be built and stored in the platform. For example, the architecture of department dimension can construct architecture diagram of departments based on the upper and lower relationships among departments on the platform. And can refer to the architecture diagram of the departments to create a personnel information table of the departments. Personnel identifiers included in each department can be stored in the personnel information table of the department, and the personnel identifiers can uniquely identify corresponding personnel in the platform. In this way, a table of personal information for each dimension can be created accurately and efficiently.
Optionally, in an actual application scenario, the personnel information tables of each dimension created in other platforms can also be directly imported into the platform used in the embodiment, such as a low-code platform, so that the creation time in personnel information of each dimension in the platform can be effectively saved, and the creation efficiency is improved.
Further, in this embodiment, the method may further include: the personnel information table of each dimension is updated based on the change of the architecture of each dimension or the change of personnel in each dimension.
That is, if a division combination, a role update, a job change, or the like occurs in the architecture of each dimension, the personnel information table of each dimension may be updated based on the change of the architecture of each dimension.
For another example, if the personnel in each dimension changes, for example, there are reasons such as new personnel entering or old personnel leaving, or a situation such as a certain personnel changing from one department to another, the personnel information table of each dimension may be updated based on the personnel change situation of each dimension, but the architecture of each dimension is not changed at this time.
In this embodiment, by adopting the above manner, personnel in the platform can be managed and maintained according to the architecture with multiple dimensions, so that personnel management efficiency in the platform is effectively improved.
S208, based on the identification of the task processor of the node, acquiring the channel identification of the task processor capable of executing task processing from a personnel basic information table in the platform; step S209 is performed;
s209, initiating processing tasks corresponding to the nodes in the corresponding channels based on channel identifiers of task processing persons.
Optionally, before step S208, the method may further include: a personnel base information table of the platform is created or imported.
That is, in the platform of the present embodiment, the personnel basic information table may be stored in addition to the personnel information table of each dimension and the architecture of each dimension. In the person basic information table, a plurality of pieces of person information may be stored. Each person information includes a person identifier and attribute information of the person. For example, in the platform, a plurality of applications may be included, each application being a channel capable of contacting a person, and attribute information of the person may include a respective channel identifier of the person. For example, each channel identifier of a person may refer to an account number of the person in each application in the platform, so that when the person is required to perform task processing in an application of a certain channel, the channel identifier of the person in the application of the channel can be accurately located. In addition, the attribute information of the person may include various information such as other interests and hobbies of the person, and a reference community.
In the scenario of step S208 of this embodiment, it may be considered that default channel information is set in the pre-configured workflow template, or that the platform includes only one channel application.
Further, the method of the embodiment further includes: based on the change of the person, the person basic information table is updated.
For example, when the personnel change is caused by the reasons of new personnel job entry or old personnel job departure in the platform, the personnel basic information table can be timely and accurately updated based on the personnel change.
For each node in the workflow initiated by the user based on the pre-configured workflow template in the platform, the steps S202-S209 of the embodiment may be adopted to perform task processing on the node, so as to implement execution of the workflow.
According to the task processing method in the workflow oriented to the low-code platform, the labels of the task processing persons of the nodes can be obtained from the workflow initiated based on the pre-configured workflow template, and further the labels of the task processing persons of the nodes can be effectively and accurately determined based on the labels of the task processing persons. For example, the tag may include at least one type of identification within at least one dimension, and in particular, the identification of the task handler of the node may be accurately determined in different ways based on different content included in the tag.
In addition, in the embodiment, when a processing task is initiated, the channel identifier of the task processor capable of executing the task processing can be obtained from the personnel basic information table in the platform based on the identifier of the task processor of the node, so that the processing task corresponding to the node is accurately initiated in the corresponding channel based on the channel identifier of the task processor, and the accuracy of the task processing can be effectively ensured. Furthermore, in the present embodiment, configuration information of each node configured in the workflow template. The method and the system can determine the labels of the task processing persons without binding the task processing persons specifically, so that the workflow templates and the workflows initiated based on the workflow templates are decoupled from the task processing persons of all the nodes, and therefore, when personnel change occurs in the platform, the execution of the workflow templates and the workflows is not affected, the stability of the workflow templates and the workflows is effectively improved, and the flexibility of workflow task processing is improved.
FIG. 3 is a schematic diagram according to a third embodiment of the present disclosure; as shown in fig. 3, the technical solution of the present disclosure is further described in more detail on the basis of the technical solution of the embodiment shown in fig. 1 or fig. 2. As shown in fig. 3, the method for processing a workflow for a low-code platform in this embodiment may specifically include the following steps:
s301, acquiring a workflow initiated by a user based on a workflow template preconfigured in a platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node comprises a positioning strategy of a task processor;
Optionally, before this step S301, the following steps may be included:
The workflow template is configured in a platform, the workflow template comprises a plurality of nodes with a circulation sequence relation, and each node is configured with a positioning strategy of a task processor. In other words, in this embodiment, the configuration information of each node includes the positioning policy of the task processor configured by each node as an example.
S302, for each node, acquiring parameters of a user in a workflow;
S303, acquiring a positioning strategy of a task processor of the node from configuration information of the node in a pre-configured workflow template;
s304, determining a label of the task processor of the node based on the parameter and the positioning strategy of the task processor;
In this embodiment, the parameters of the user in the workflow may specifically refer to parameter information carried when the user initiates the workflow.
For example, if the workflow is a leave ticket, the parameters of the user in the workflow may include the department and job level where the user is located, and the number of leave days. Correspondingly, the task processing person positioning strategy can comprise: if the leave-on days are less than or equal to n days, n is a preset integer threshold, and at this time, the first-level approval personnel can be the personnel with the department and job level higher than those of the user. If the number of leave-on days is greater than n days, the first-level approver can be the department where the user is located and the staff with the job level higher than that of the user by two levels.
For another example, where the workflow is a financial approval worksheet, the parameters of the user in the workflow may include the amount the user has requested approval. Correspondingly, the task processing person positioning strategy can comprise: if the amount of the request approval is less than or equal to m yuan, m is also a preset integer threshold, and at the moment, the first-level approval personnel can be the m 1-level personnel approval in the financial department. If the amount of the request approval is larger than m yuan, the first-level approver can approve the request for the approval for the m 2-level personnel in the financial department.
The above two examples are merely examples, and do not limit the aspects of the present disclosure. By analogy, steps S302-S304 may be applied in various scenarios for determining labels of task handlers of a node.
Steps S302-S304 are another implementation manner of step S102 in the embodiment shown in fig. 1. By the method, the labels of the task handler of the nodes can be accurately and efficiently determined based on the parameters of the user when initiating the workflow and the positioning strategy of the task handler configured in the nodes of the workflow template.
Similarly, in this embodiment, the label of the task handler of each node includes at least one type of identifier in at least one dimension; the at least one dimension includes at least one of a role, a job level, and a department. Details of the embodiment shown in fig. 2 are referred to above, and will not be described herein.
S305, detecting whether the label comprises identification of types in at least two dimensions; if yes, go to step S307; otherwise, if not, executing step S306;
S306, detecting whether the label comprises one type of identification in one dimension or at least two types of identification in one dimension; if only one type of identification in one dimension is included, step S308 is performed; otherwise, if at least two types of identifiers in one dimension are included, step S309 is performed;
S307, responding to the label of the task processor to comprise the identification of the type in at least two dimensions, acquiring the identification of the person corresponding to the type in the dimension from the person information table corresponding to each dimension in the at least two dimensions, and taking the intersection of the identifications of the persons corresponding to the type in each dimension between the at least two dimensions as the identification of the task processor of the node; step S310 is performed;
S308, responding to the label of the task processor to comprise a type of identification in one dimension, and acquiring the identification of the person corresponding to the type from a person information table corresponding to the dimension as the identification of the task processor of the node; step S310 is performed;
S309, responding to the fact that the labels of the task processor comprise at least two types of identifications in one dimension, acquiring identifications of all types of corresponding personnel in the at least two types from a personnel information table corresponding to the dimension, and taking a union of the identifications of all types of corresponding personnel in the at least two types as the identifications of the task processor of the node; step S310 is performed;
S310, acquiring channel information of task processing of the node from a pre-configured workflow template; step S311 is performed;
s311, acquiring a channel identifier of a task processor capable of executing task processing from a personnel basic information table based on the identifier and channel information of the task processor of the node; step S312 is performed;
Steps S310-S311 are one implementation of step S208 of the embodiment shown in fig. 2 described above. In the above step S208, the entire platform may be considered to include only one channel. Or default channel information is set in the pre-configured workflow template, and the workflow template is directly acquired based on the default channel information. In the technical scheme of the embodiment, the channel information of task processing of each node can be configured in the workflow template, and the channel information of task processing of different nodes in the workflow template can be the same or different.
By the mode, the channel information of task processing of each node is configured in the workflow template, so that each node can be more flexible in executing task processing.
S312, acquiring a channel identifier of a task processor capable of executing task processing from a personnel basic information table in a platform based on the identifier of the task processor of the node; step S313 is performed;
S313, initiating processing tasks corresponding to the nodes in the corresponding channels based on channel identifiers of task processing persons.
The specific implementation manner of steps S305 to S313 in this embodiment may refer to the descriptions of steps S203 to S209 in the embodiment shown in fig. 2, and will not be described herein.
Similarly, by adopting the scheme, the task processing method in the workflow facing the low-code platform can also efficiently and accurately determine the identification of the task processor of the node. In addition, in the embodiment, when the processing task is initiated, the accuracy of task processing can be effectively ensured. In this embodiment, the configuration information of each node configured in the workflow template is provided. The method and the system can determine the labels of the task processing persons without binding the task processing persons specifically, so that the workflow templates and the workflows initiated based on the workflow templates are decoupled from the task processing persons of all the nodes, and therefore, when personnel change occurs in the platform, the execution of the workflow templates and the workflows is not affected, the stability of the workflow templates and the workflows is effectively improved, and the flexibility of workflow task processing is improved.
FIG. 4 is a schematic diagram according to a fourth embodiment of the present disclosure; as shown in fig. 4, the present embodiment provides a task processing device 400 in a workflow for a low-code platform, including:
An obtaining module 401, configured to obtain a workflow initiated by a user based on a workflow template preconfigured in a platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node can determine the label of the task processor;
A determining module 402, configured to determine a label of a task handler of a node in the workflow based on configuration information of the node;
a positioning module 403, configured to position an identifier of a task processor of the node based on a tag of the task processor of the node;
and the initiating module 404 is configured to initiate a processing task corresponding to the node based on the identifier of the task processor of the node.
The task processing device 400 in the workflow for the low-code platform according to the embodiment adopts the above modules to implement the implementation principle and the technical effect of task processing in the workflow for the low-code platform, and is the same as the implementation of the related method embodiment, and detailed description of the related method embodiment may be referred to and will not be repeated here.
FIG. 5 is a schematic diagram according to a fifth embodiment of the present disclosure; as shown in fig. 5, the present embodiment provides a task processing device 500 in a workflow for a low-code platform, including: the same name and function module as shown in the above figure 4: an acquisition module 501, a determination module 502, a positioning module 503, and an initiation module 504.
In this embodiment, the determining module 502 is configured to:
And acquiring the label of the task processor of the node from the configuration information of the node in the pre-configured workflow template.
Or further alternatively, in one embodiment of the present disclosure, the determining module 502 is configured to:
Acquiring parameters of the user in the workflow;
Acquiring a positioning strategy of a task processor of a node from configuration information of the node in the pre-configured workflow template;
and determining the label of the task processor of the node based on the parameters and the positioning strategy of the task processor.
Further optionally, in an embodiment of the present disclosure, the tag includes at least one type of identification within at least one dimension; the at least one dimension includes at least one of a role, a job level, and a department.
Further optionally, in an embodiment of the present disclosure, the positioning module 503 is configured to:
And responding to the label of the task processor to comprise a type of identification in one dimension, and acquiring the identification of the person corresponding to the type from a person information table corresponding to the dimension as the identification of the task processor of the node.
Further optionally, in an embodiment of the present disclosure, the positioning module 503 is configured to:
And responding to the label of the task processor, wherein the label comprises at least two types of identifiers in a dimension, acquiring the identifiers of the persons corresponding to each type in the at least two types from a person information table corresponding to the dimension, and taking the union of the identifiers of the persons corresponding to each type in the at least two types as the identifier of the task processor of the node.
Further optionally, in an embodiment of the present disclosure, the positioning module is configured to:
And responding to the label of the task processor, wherein the label comprises identifiers of types in at least two dimensions, acquiring identifiers of persons corresponding to the types in the dimensions from a person information table corresponding to each dimension in the at least two dimensions, and taking an intersection of identifiers of the persons corresponding to the types in each dimension in the at least two dimensions as the identifier of the task processor of the node.
Further alternatively, as shown in fig. 5, in one embodiment of the present disclosure, the task processing device 500 in the workflow for the low code platform further includes:
the personnel information table generating module 505 is configured to create or import personnel information tables of each dimension in the platform;
An updating module 506, configured to update the personnel information table of each dimension based on a change of the architecture of each dimension or a change of personnel in each dimension.
Further optionally, in an embodiment of the present disclosure, the initiating module 504 is configured to:
based on the identification of the task processor of the node, acquiring a channel identification of the task processor capable of executing task processing from a personnel basic information table in a platform;
And initiating the processing task corresponding to the node in the corresponding channel based on the channel identification of the task processor.
Further optionally, in an embodiment of the present disclosure, the initiating module 504 is configured to:
Obtaining channel information of task processing of the node from the preconfigured workflow template;
and acquiring the channel identification of the task processor capable of executing task processing from a personnel basic information table based on the identification of the task processor of the node and the channel information.
Further optionally, in one embodiment of the present disclosure:
The personnel information table generating module 505 is further configured to create, or import, a personnel basic information table of the platform;
The update module 506 is further configured to:
and updating the personnel basic information table based on the personnel change.
Further optionally, in an embodiment of the present disclosure, the task processing device 500 in the workflow for the low code platform further includes:
A configuration module 507, configured to configure the workflow template in a platform, where the workflow template includes a plurality of nodes with a circulation order relationship, and each node is configured with configuration information; the configuration information of each node can determine the label of the task processor.
The task processing device 500 in the workflow for the low-code platform according to the embodiment adopts the above modules to implement the implementation principle and the technical effect of task processing in the workflow for the low-code platform, and is the same as the implementation of the related method embodiment, and detailed description of the related method embodiment may be referred to and will not be repeated here.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the related user personal information all conform to the regulations of related laws and regulations, and the public sequence is not violated.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
Fig. 6 illustrates a schematic block diagram of an example electronic device 600 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 6, the apparatus 600 includes a computing unit 601 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 may also be stored. The computing unit 601, ROM 602, and RAM 603 are connected to each other by a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Various components in the device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, mouse, etc.; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 601 performs the various methods and processes described above, such as the methods described above of the present disclosure. For example, in some embodiments, the above-described methods of the present disclosure may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into RAM 603 and executed by computing unit 601, one or more steps of the above-described methods of the present disclosure described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the above-described methods of the present disclosure in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server incorporating a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (27)
1. A task processing method in a workflow facing a low-code platform comprises the following steps:
Acquiring a workflow initiated by a user based on a workflow template preconfigured in a platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node can determine the label of the task processor;
determining a label of a task handler of a node in the workflow based on configuration information of the node;
Positioning the identification of the task processor of the node based on the label of the task processor of the node;
and initiating a processing task corresponding to the node based on the identification of the task processor of the node.
2. The method of claim 1, wherein determining the label of the task handler of the node in the workflow based on the configuration information of the node comprises:
And acquiring the label of the task processor of the node from the configuration information of the node in the pre-configured workflow template.
3. The method of claim 1, wherein determining the label of the task handler of the node in the workflow based on the configuration information of the node comprises:
Acquiring parameters of the user in the workflow;
Acquiring a positioning strategy of a task processor of a node from configuration information of the node in the pre-configured workflow template;
and determining the label of the task processor of the node based on the parameters and the positioning strategy of the task processor.
4. A method according to claim 2 or 3, wherein the tag comprises at least one type of identity in at least one dimension; the at least one dimension includes at least one of a role, a job level, and a department.
5. The method of claim 4, wherein locating the identity of the task handler of the node based on the label of the task handler of the node comprises:
And responding to the label of the task processor to comprise a type of identification in one dimension, and acquiring the identification of the person corresponding to the type from a person information table corresponding to the dimension as the identification of the task processor of the node.
6. The method of claim 4, wherein locating the identity of the task handler of the node based on the label of the task handler of the node comprises:
And responding to the label of the task processor, wherein the label comprises at least two types of identifiers in a dimension, acquiring the identifiers of the persons corresponding to each type in the at least two types from a person information table corresponding to the dimension, and taking the union of the identifiers of the persons corresponding to each type in the at least two types as the identifier of the task processor of the node.
7. The method of claim 4, wherein locating the identity of the task handler of the node based on the label of the task handler of the node comprises:
And responding to the label of the task processor, wherein the label comprises identifiers of types in at least two dimensions, acquiring identifiers of persons corresponding to the types in the dimensions from a person information table corresponding to each dimension in the at least two dimensions, and taking an intersection of identifiers of the persons corresponding to the types in each dimension in the at least two dimensions as the identifier of the task processor of the node.
8. A method according to any of claims 5-7, wherein, based on the label of the task handler of the node, prior to locating the identity of the task handler of the node, the method further comprises:
creating or importing a personnel information table of each dimension in the platform;
Further, after creating, or importing, the personnel information table of each dimension in the platform, the method further includes:
the personnel information table of each dimension is updated based on the change of the architecture of each dimension or the change of personnel in each dimension.
9. The method of claim 1, wherein initiating the processing task corresponding to the node based on the identification of the task handler of the node comprises:
based on the identification of the task processor of the node, acquiring a channel identification of the task processor capable of executing task processing from a personnel basic information table in a platform;
And initiating the processing task corresponding to the node in the corresponding channel based on the channel identification of the task processor.
10. The method of claim 9, wherein based on the identification of the task processor of the node, obtaining, from a person base information table, an account identification of a task processor capable of performing task processing, includes:
Obtaining channel information of task processing of the node from the preconfigured workflow template;
and acquiring the channel identification of the task processor capable of executing task processing from a personnel basic information table based on the identification of the task processor of the node and the channel information.
11. A method according to claim 9 or 10, wherein, based on the identity of the task processor of the node, before obtaining from a person base information table a channel identity from which the task processor can perform task processing, the method further comprises:
Creating or importing a personnel basic information table of the platform;
further, after creating, or importing, the personnel base information table of the platform, the method further includes:
and updating the personnel basic information table based on the personnel change.
12. The method of claim 1, wherein prior to retrieving a workflow initiated by a user based on a pre-configured workflow template in a platform, the method further comprises: configuring the workflow template in a platform, wherein the workflow template comprises a plurality of nodes with a circulation sequence relation, and each node is configured with configuration information; the configuration information of each node can determine the label of the task processor.
13. A task processing device in a workflow for a low code platform, comprising:
The acquisition module is used for acquiring a workflow initiated by a user based on a workflow template preconfigured in the platform; the workflow template comprises a plurality of nodes with a circulation sequence relation and configuration information of each node; the configuration information of each node can determine the label of the task processor;
The determining module is used for determining labels of task processing persons of the nodes in the workflow based on configuration information of the nodes;
the positioning module is used for positioning the identification of the task processor of the node based on the label of the task processor of the node;
And the initiating module is used for initiating the processing task corresponding to the node based on the identification of the task processor of the node.
14. The apparatus of claim 13, wherein the means for determining is configured to:
And acquiring the label of the task processor of the node from the configuration information of the node in the pre-configured workflow template.
15. The apparatus of claim 13, wherein the means for determining is configured to:
Acquiring parameters of the user in the workflow;
Acquiring a positioning strategy of a task processor of a node from configuration information of the node in the pre-configured workflow template;
and determining the label of the task processor of the node based on the parameters and the positioning strategy of the task processor.
16. The apparatus of claim 14 or 15, wherein the tag comprises at least one type of identification in at least one dimension; the at least one dimension includes at least one of a role, a job level, and a department.
17. The apparatus of claim 16, wherein the positioning module is configured to:
And responding to the label of the task processor to comprise a type of identification in one dimension, and acquiring the identification of the person corresponding to the type from a person information table corresponding to the dimension as the identification of the task processor of the node.
18. The apparatus of claim 16, wherein the positioning module is configured to:
And responding to the label of the task processor, wherein the label comprises at least two types of identifiers in a dimension, acquiring the identifiers of the persons corresponding to each type in the at least two types from a person information table corresponding to the dimension, and taking the union of the identifiers of the persons corresponding to each type in the at least two types as the identifier of the task processor of the node.
19. The apparatus of claim 16, wherein the positioning module is configured to:
And responding to the label of the task processor, wherein the label comprises identifiers of types in at least two dimensions, acquiring identifiers of persons corresponding to the types in the dimensions from a person information table corresponding to each dimension in the at least two dimensions, and taking an intersection of identifiers of the persons corresponding to the types in each dimension in the at least two dimensions as the identifier of the task processor of the node.
20. The apparatus of any of claims 17-19, wherein the apparatus further comprises:
The personnel information table generation module is used for creating or importing personnel information tables of all dimensions in the platform;
The apparatus further comprises:
And the updating module is used for updating the personnel information table of each dimension based on the change of the architecture of each dimension or the change of personnel in each dimension.
21. The apparatus of claim 20, wherein the means for initiating is configured to:
based on the identification of the task processor of the node, acquiring a channel identification of the task processor capable of executing task processing from a personnel basic information table in a platform;
And initiating the processing task corresponding to the node in the corresponding channel based on the channel identification of the task processor.
22. The apparatus of claim 21, wherein the means for initiating is configured to:
Obtaining channel information of task processing of the node from the preconfigured workflow template;
and acquiring the channel identification of the task processor capable of executing task processing from a personnel basic information table based on the identification of the task processor of the node and the channel information.
23. The apparatus of claim 21 or 22, wherein:
The personnel information table generation module is also used for creating or importing a personnel basic information table of the platform;
The updating module is further configured to:
and updating the personnel basic information table based on the personnel change.
24. The apparatus of claim 13, wherein the apparatus further comprises:
The configuration module is used for configuring the workflow template in the platform, wherein the workflow template comprises a plurality of nodes with a circulation sequence relation, and each node is configured with configuration information; the configuration information of each node can determine the label of the task processor.
25. An electronic device, comprising:
At least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-12.
26. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-12.
27. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311767591.0A CN118034647A (en) | 2023-12-20 | 2023-12-20 | Task processing method, device and medium in workflow oriented to low-code platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311767591.0A CN118034647A (en) | 2023-12-20 | 2023-12-20 | Task processing method, device and medium in workflow oriented to low-code platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118034647A true CN118034647A (en) | 2024-05-14 |
Family
ID=90992236
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311767591.0A Pending CN118034647A (en) | 2023-12-20 | 2023-12-20 | Task processing method, device and medium in workflow oriented to low-code platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118034647A (en) |
-
2023
- 2023-12-20 CN CN202311767591.0A patent/CN118034647A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112559631B (en) | Data processing method and device of distributed graph database and electronic equipment | |
| CN112866391A (en) | Message pushing method and device, electronic equipment and storage medium | |
| CN114202027A (en) | Execution configuration information generation method, model training method and device | |
| CN114021156A (en) | Method, device and equipment for organizing vulnerability automatic aggregation and storage medium | |
| CN116562249A (en) | Form generation method, form generation device, electronic equipment and medium | |
| CN113037489B (en) | Data processing method, device, equipment and storage medium | |
| CN113407745A (en) | Data annotation method and device, electronic equipment and computer readable storage medium | |
| CN116302218B (en) | Function information adding method, device, equipment and storage medium | |
| CN113704256B (en) | Data identification method, device, electronic equipment and storage medium | |
| CN112783943B (en) | Stroke relationship extraction method, device, equipment, storage medium and program product | |
| CN118034647A (en) | Task processing method, device and medium in workflow oriented to low-code platform | |
| CN116069497A (en) | Method, apparatus, device and storage medium for executing distributed task | |
| CN112632293B (en) | Industry map construction method and device, electronic equipment and storage medium | |
| CN114118937A (en) | Information recommendation method and device based on task, electronic equipment and storage medium | |
| CN114327392A (en) | Data processing method and device and electronic equipment | |
| CN113592293A (en) | Risk identification processing method, electronic device and computer-readable storage medium | |
| CN113360672A (en) | Methods, apparatus, devices, media and products for generating a knowledge graph | |
| CN114036250A (en) | High-precision map task processing method and device, electronic equipment and medium | |
| CN114036249A (en) | Map data processing method, map data processing device, electronic equipment and medium | |
| CN104881491A (en) | Software development system based on big data platform | |
| CN116432169B (en) | Automatic task permission control method, system and equipment based on sharing strategy | |
| CN116910250B (en) | Knowledge processing method, knowledge processing device, electronic equipment and storage medium | |
| CN113051470B (en) | Position accuracy evaluation method and device, electronic equipment and computer readable medium | |
| CN116414999A (en) | Knowledge graph-based management method and device, electronic equipment and storage medium | |
| CN117611093A (en) | Service processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |