CN111736929A - Method, device and equipment for creating task instance and readable storage medium - Google Patents
Method, device and equipment for creating task instance and readable storage medium Download PDFInfo
- Publication number
- CN111736929A CN111736929A CN202010572232.XA CN202010572232A CN111736929A CN 111736929 A CN111736929 A CN 111736929A CN 202010572232 A CN202010572232 A CN 202010572232A CN 111736929 A CN111736929 A CN 111736929A
- Authority
- CN
- China
- Prior art keywords
- task
- value
- attribute
- target
- template
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000012986 modification Methods 0.000 claims abstract description 16
- 230000004048 modification Effects 0.000 claims abstract description 16
- 230000015654 memory Effects 0.000 claims description 20
- 230000004044 response Effects 0.000 claims description 4
- 238000012545 processing Methods 0.000 abstract description 14
- 238000004891 communication Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000013135 deep learning Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000010924 continuous production Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N20/00—Machine learning
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Artificial Intelligence (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Data Mining & Analysis (AREA)
- Evolutionary Computation (AREA)
- Medical Informatics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a method and a device for creating a task instance, electronic equipment and a computer-readable storage medium, and relates to the technical field of intelligent office, cloud platforms and task processing. One embodiment of the method comprises: determining a target task template required to be used for creating a target task instance; determining the task attribute which is not modified in the target task instance as a target task attribute; and setting the index path of the value of the target task attribute as the index path of the corresponding task attribute value in the target task template. The method sets the index path of the value of the task attribute which is not modified as the index path of the value of the corresponding task attribute in the target task template, so that the value of the task attribute which is not modified actually belongs to a common relation between the task instance and the transaction template, and modification of all task instances created by the task template can be completed at one time by only modifying the task template based on the common relation, and the efficiency is obviously improved.
Description
Technical Field
The embodiment of the application relates to a data processing technology, in particular to the technical field of intelligent office, cloud platforms and task processing, and particularly relates to a method and device for creating a task instance, electronic equipment and a computer-readable storage medium.
Background
In order to enhance the convenience of task instance creation, a two-stage mode of firstly developing a task template and then creating different task instances based on the task template is widely adopted nowadays.
In the prior art, when a task instance is created by a task template, the task instance is created in an "inheritance" manner, that is, the creation action is equivalent to a copy action performed on the task template, and values of some task attributes (basic elements forming a task, such as a title, a priority, a state and the like) in the copied task template are adjusted according to actual requirements of the task instance, so that an independent task instance completely separated from the task template is obtained. Once the task instance is created, the task instance is not associated with the task template, and the modification operation can only be performed on the task instance.
Disclosure of Invention
The embodiment of the application provides a method and a device for creating a task instance, electronic equipment and a computer-readable storage medium.
In a first aspect, an embodiment of the present application provides a method for creating a task instance, including: determining a target task template required to be used for creating a target task instance; determining the task attribute which is not modified in the target task instance as a target task attribute; and setting the index path of the value of the target task attribute as the index path of the corresponding task attribute value in the target task template.
In a second aspect, an embodiment of the present application provides an apparatus for creating a task instance, including: a target task template determination unit configured to determine a target task template to be used for creating a target task instance; a target task attribute determining unit configured to determine an unmodified task attribute in the target task instance as a target task attribute; and the index path setting unit is configured to set the index path of the value of the target task attribute as the index path of the value of the corresponding task attribute in the target task template.
In a third aspect, an embodiment of the present application provides an electronic device, 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 cause the at least one processor to perform the method for creating a task instance as described in any implementation manner of the first aspect when executed.
In a fourth aspect, embodiments of the present application provide a non-transitory computer-readable storage medium storing computer instructions for enabling a computer to implement a method for creating a task instance as described in any implementation manner of the first aspect when executed.
According to the method, the device, the electronic equipment and the computer-readable storage medium for creating the task instance, firstly, a target task template required to be used for creating the target task instance is determined; then, determining the task attribute which is not modified in the target task instance as a target task attribute; and finally, setting the index path of the value of the target task attribute as the index path of the corresponding task attribute value in the target task template.
Compared with the task examples completely separated from the task template obtained through 'inheritance', the index path of the values of the unmodified task attributes is set to be the index path of the values of the corresponding task attributes in the target task template through the technical scheme, so that the values of the unmodified task attributes actually belong to a common relation between the task examples and the transaction template, and the modification of all the task examples created through the task template can be completed at one time through the modification of the task template based on the common relation, and the efficiency is obviously improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture to which the present application may be applied;
FIG. 2 is a flowchart of a method for creating a task instance according to an embodiment of the present application;
FIG. 3 is a flow chart of another method for creating a task instance provided by an embodiment of the present application;
FIG. 4 is a flowchart of a method for creating a task template according to an embodiment of the present application;
FIG. 5 is a block diagram illustrating an apparatus for creating a task template according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an electronic device suitable for implementing a method for creating a task template according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
FIG. 1 illustrates an exemplary system architecture 100 to which embodiments of the method, apparatus, electronic device, and computer-readable storage medium for creating task instances of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to perform information interaction with the server 105 through the network 104, for example, the terminal devices 101, 102, 103 may send a task instance creation request to the server through the network 104, and the server 105 may export the task instance and return the task instance to the terminal devices 101, 102, 103 through the network 104 after completing the task instance creation according to the creation information included in the task instance creation request. Various applications for realizing data exchange between the terminal devices 101, 102, 103 and the server 105 can be installed on the terminal devices 101, 102, 103, and the server 105, for example, a task instance creation application, a task template creation application, an instant messaging application, and the like.
The terminal apparatuses 101, 102, 103 and the server 105 may be hardware or software. When the terminal devices 101, 102, 103 are hardware, they may be various electronic devices with display screens, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like; when the terminal devices 101, 102, and 103 are software, they may be installed in the electronic devices listed above, and they may be implemented as multiple software or software modules, or may be implemented as a single software or software module, and are not limited in this respect. When the server 105 is hardware, it may be implemented as a distributed server cluster composed of multiple servers, or may be implemented as a single server; when the server is software, the server may be implemented as a plurality of software or software modules, or may be implemented as a single software or software module, which is not limited herein.
The terminal devices 101, 102, 103 and the server 105 may provide various services through various built-in applications, for example, a server 105 having a task instance creation application capable of providing the task instance creation service is built in, and when the server 105 runs the task instance creation application, the following effects may be achieved: firstly, receiving task instance creating requests sent from terminal equipment 101, 102 and 103 through a network 104, wherein the task instance creating requests comprise related information of target task instances; then, determining a target task template used for creating a target task instance according to the relevant information; secondly, determining the task attribute which is not modified in the target task instance as a target task attribute according to the related information or the newly created process information transmitted in real time; and finally, setting the index path of the value of the target task attribute as the index path of the corresponding task attribute value in the target task template. I.e., the server 105 will eventually complete the creation of the target task instance with the index path setting for the value of the target task attribute.
It should be noted that the task instance creation request containing the relevant information of the target task instance may be pre-stored locally in the server 105 in various ways, in addition to being received from the terminal devices 101, 102, 103 via the network 104. Thus, when the server 105 detects that such data is already stored locally (e.g., a pending task instance creation request that persists before starting processing), it may choose to retrieve such data directly from locally, in which case the exemplary system architecture 100 may also not include the terminal devices 101, 102, 103 and the network 104.
Since the task template used for creating the task instance is usually stored in the server for security reasons, the method for creating the task instance provided in the subsequent embodiments of the present application is generally executed by the server 105, and accordingly, the device for creating the task instance is also generally disposed in the server 105. However, it should be noted that when the terminal devices 101, 102, and 103 also have the required security or are granted with the corresponding rights, the terminal devices 101, 102, and 103 may also complete the operations executed by the server 105 through the task template stored locally by the task instance creation application installed thereon, and further complete the creation of the task instance without the participation of the server 105. Accordingly, the means for creating task instances may also be provided in the terminal devices 101, 102, 103. In such a case, the exemplary system architecture 100 may also not include the server 105 and the network 104.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continuing reference to fig. 2, fig. 2 is a flowchart of a method for creating a task instance according to an embodiment of the present application, where a flow 200 in the flowchart includes the following steps:
step 201: a target task template to be used for creating a target task instance is determined.
This step is intended to determine, by an executing agent (e.g., server 105 shown in FIG. 1) for creating a task instance, a target task template to be used to create a target task instance. The execution subject may determine the target task template according to the relevant information of the target task instance contained in the task instance creation request initiated by the terminal (e.g., terminal devices 101, 102, 103 shown in fig. 1). The related information may include an application scenario of the target task instance, initiator information, actual requirements, a matching task template number, and the like.
It should be noted that the task instance creation request including the related information of the target task instance may be directly obtained from a local storage device by the execution main body, or may be obtained from a non-local storage device (for example, terminal devices 101, 102, 103 shown in fig. 1). The local storage device may be a data storage module arranged in the execution main body, such as a server hard disk, in which case it can be quickly read locally; the non-local storage device may also be any other electronic device configured to store data, such as some user terminals, in which case, the executing entity may receive a task instance creation request sent by the electronic device through a network, so as to further determine a target task template according to the related information contained therein.
It should be understood that, after the target task template is determined, a subsequent creation operation of the target task instance needs to be completed by using the target task template, in the subsequent creation operation, the task attribute and/or the value of the task attribute are/is adjusted mainly according to the actual needs of the user, which is often a continuous process.
Of course, in addition to the manner of continuously transmitting the adjustment instruction to the execution main body through the long connection, the terminal initiating the task instance creation request may also be required to write all the adjustment instructions into the creation request at one time, so that the execution main body directly completes creation of the target task instance according to all the extracted adjustment instructions. The specific selection of which may be flexibly selected according to all possible special requirements under the actual application scenario is not specifically limited herein.
Step 202: and determining the task attribute which is not modified in the target task instance as the target task attribute.
On the basis of step 201, this step is intended to determine the task attribute that is not modified in the target task instance as the target task attribute by the execution subject, that is, according to whether the task attribute is modified differently from the content embodied in the task template, all task attributes are divided into two categories, that is, the task attribute that is not modified is divided into the target task attribute, and the task attribute that is modified is divided into the non-target task attribute. In other words, the target task attribute still retains the same content of the target task template of the source, since no modification is made to distinguish it from the same part of the target task template.
For ease of understanding, herein by way of illustration: assume that a target task instance a1 is created by a target task template a with 5 different task attributes coexisting on the target task template a, numbered 01, 02, 03, 04, 05, and that the target task instance a1 adjusts only the values of the task attributes numbered 02, 04, so that the values of the 3 task attributes numbered 01, 03, 05 should still match the default values given by the task template a, i.e., the 3 task attributes numbered 01, 03, 05 are target task attributes and the 2 task attributes numbered 02, 04 are non-target task attributes.
Step 203: and setting the index path of the value of the target task attribute as the index path of the corresponding task attribute value in the target task template.
On the basis of step 202, for the target task attribute in the target task instance, this step is intended to set the index path of the value of the target task attribute as the index path of the value of the corresponding task attribute in the target task template by the execution subject. The index path indicates the record/storage location of the value of the target task attribute, and is essentially a pointer-like correspondence, that is, the index path of the value is stored instead of the actual value.
For ease of understanding, the following are exemplified herein: in an Excel table for recording the monthly examination scores of 10 people in the whole shift in the past year, each person in the table has a score box in each month, the actual score in the score box is not directly input, but points to a certain position of the actual score under a certain path, for example, the index path of the actual score in 10 months of Xiaoming is as follows: d/historical achievement/10-month achievement/a 3, namely, column a, row 3 in Excel table file named "10-month achievement" in "historical achievement" folder named "10-month achievement" and showing the actual achievement recorded in xiaoming in 10 months, if xiaoming 10-month achievement is regarded as a task attribute, then the task attribute is indexed: d/historical score/10 month score/a 3 to obtain its actual value.
In the example of accepting 5 task attributes with numbers 01, 02, 03, 04, and 05 as mentioned in step 202, this step is equivalent to making the target task instance and the target task template share an index path of their values for 3 target task attributes with numbers 01, 03, and 05, that is, the target task attributes with numbers 01, 03, and 05 in the target task instance do not directly have their independent actual values, but point to the same actual storage location through the common index path, that is, the target task instance and the target task template have reference sources of the same values on the target task attributes with numbers 01, 03, and 05. Therefore, under the condition that the values of the target task attribute and the target task attribute are determined through the same index path, the same target task attribute on all task instances created through the task template can execute subsequent operations according to the modified values through the same index path only by modifying the value of the target task attribute under the original index path on the task template.
Specifically, the modification of the target task attribute in the target task template can be completed according to the following steps:
and responding to a task attribute adjusting instruction aiming at the target task template, and adjusting the index path of the original task attribute value or adjusting the value stored in the original index path according to the task attribute adjusting instruction. The task attribute adjustment comprises deletion of the original task attribute, value adjustment and addition of the new task attribute.
And no matter whether the target task attribute is modified in the target task template under the original index path or not, when an access instruction for the target task instance is received, the current value is inquired according to the index path of the value of the target task attribute, and a response of corresponding operation is executed according to the current value is made, so that through the two steps of operation, under the condition of sharing the index relation, the modification of all the task instances established based on the template can be completed only by once adjusting the task template.
In order to further improve the efficiency of the task instance executing correct operation according to the actual values of the task attributes, when the value of any task attribute in the target task template is modified, the modified value is actively pushed to the running cache of all task instances created by the target task template, so that the task instance does not need to execute a search action again through an index path and can be quickly obtained from the cache, and the method only aims at the target task attribute which is not modified in the task instance.
For convenience, according to the setting mode of the value provided for the target task attribute in this embodiment, the setting mode given above that shares one index path may be referred to as "shallow copy" for short, and when a task instance is created through a task template, the value of the target task attribute is not copied separately, but only the index path is "copied", so that the task instance and the same part in the task template are associated based on the same index path.
Compared with the task examples completely separated from the task template obtained by the 'inheritance' in the prior art, the embodiment sets the index path of the value of the unmodified task attribute as the index path of the value of the corresponding task attribute in the target task template through the technical scheme, so that the value of the unmodified task attribute actually belongs to a common relationship between the task examples and the transaction template, and the modification of all the task examples created through the task template can be completed at one time by only modifying the task template based on the common relationship, and the efficiency is obviously improved.
With continuing reference to fig. 3, fig. 3 is a flowchart of another method for creating a task instance according to an embodiment of the present application, where a flow 300 in the flowchart includes the following steps:
step 301: a target task template to be used for creating a target task instance is determined.
Step 302: and setting the index paths of the values of all task attributes in the target task instance as the index paths of the values of the corresponding task attributes in the target task template.
On the basis of step 301, this step is intended to set, by the execution subject, the index paths of the values of all task attributes in the initial target task instance just created according to the target task template as the index paths of the values of the corresponding task attributes in the target task template, that is, the setting of the index paths of the values of all task attributes is completed in a "shallow copy" manner. This is because all task attributes are in an unmodified state until a user-entered task attribute adjustment instruction for a task instance has not been received.
Step 303: when the value of any task attribute in the target task instance is modified, deleting the index path of the original value of the modified task attribute, and creating a new index path of the value for the modified task attribute.
On the basis of step 302, this step is intended to delete the index path of the original value of the task attribute whose value is modified and create a new index path of the value for the task attribute whose value is modified when the value of any task attribute in the target task instance is modified by the execution subject.
Step 304: and storing the modified actual value of the task attribute with the modified value to the new index path.
Compared with the processing mode for the unmodified task attribute called "shallow copy", once a user modifies a certain task attribute in a task instance, the task attribute of the task instance should operate according to an actual value set by the user, so that deletion of an original index path and establishment of a new index path are completed through step 303 and step 304, the actual value is stored in the new index path, and an originally existing common relationship is taken out. In distinction to the designation of "shallow copy," the above-described processing approach may be referred to as "deep copy" for modified task processing.
On the basis of having all the beneficial effects of the above embodiments, in the embodiment, in combination with the creation process of the task instance in an actual situation, according to whether the value is modified by the user, the processing manners of "shallow copy" and "deep copy" are respectively given, and it is set that all task instances in the target task instance that have not been adjusted by the user adopt the processing manner of "shallow copy", and each time the user adjusts one of the task attributes, the task attribute is changed to "deep copy", so that the common relationship brought by the processing manner of "shallow copy" is improved to the greatest extent and is used for efficiently and uniformly adjusting the actual value of the task attribute.
On the basis of any of the above embodiments, in order to increase application scenarios of task instances created by task templates as much as possible, meet different requirements of different users, and avoid the problem that an old task template cannot meet the requirements of a new task and needs to be developed secondarily, the present application further provides a flowchart of a task template creation method with high definition characteristics and high extensibility through fig. 4, where the flowchart 400 includes the following steps:
step 401: and setting basic task attributes and custom task attributes.
The basic task attributes refer to essential task attributes which are usually needed by different task requirements, such as starting time, ending time, reminding time, titles, executive staff and the like, and in brief, the basic task attributes are common task attributes existing in different types of tasks; the custom task attribute refers to an individual task attribute in which different types of tasks independently exist according to respective time conditions, for example, the individual task attribute such as iteration times, a next iteration trigger critical value and the like exist in an iteration task scene. Therefore, the embodiment classifies the task attributes into two categories according to the individual requirements and the commonality requirements: a base task attribute and a custom task attribute, wherein the base task attribute provides a conventional fixed or alternative.
Step 402: and writing a limiting rule for limiting the self-defining degree for the self-defining task attribute.
On the basis of step 401, in this step, it is intended that the execution subject writes a restriction rule for restricting the customization degree for the custom task attribute in advance, so as to restrict the custom attribute to meet the preset requirement through the restriction rule, thereby enabling the user to customize the relevant information of the task attribute while meeting the preset requirement. Specifically, the restriction rule can be set by combining the actual situation from various aspects such as the type and the position of the corresponding task attribute. For example, for a custom task attribute as a subheading, the constraint rule may be: the length cannot be 20 characters, the reference relationship cannot occur, and the character type is int.
Furthermore, in order to facilitate the user to clearly define whether the custom task attribute meets the preset requirement or not, when the actual custom content input by the user does not meet the preset requirement, the reminder containing the custom content limiting information corresponding to the limiting rule can be sent through the preset path, so that the custom content input next time can be adjusted according to the reminder.
Step 403: and constructing a task template according to the task attribute forming mode of the basic task attribute and the user-defined task attribute constrained by the limiting rule.
On the basis of the step 402, the step aims to construct a task template by the execution main body according to a task attribute composition mode of a basic task attribute and a custom task attribute constrained by a limiting rule, so that a task instance constructed by the task template can use the high custom property of the task instance.
According to the task template creating method, the task template creating method with high self-definition and high expansibility is provided through the technical scheme, the task examples created based on the task template generated by the method also have the same characteristics, and the problem that the old task template cannot meet the requirements of new tasks and needs to consume great energy for secondary development is solved as far as possible.
In order to deepen understanding, the application also provides a specific implementation scheme by combining a specific application scene:
1) user X adds a task instance B1 for the iterative deep learning network according to the actual needs of the company, so a task instance creation request of the task instance B1 is sent to the solution resolution Y through the network;
2) after receiving the task instance creation request, the server of the solution provider Y establishes long connection with the terminal according to the address information of the terminal used by the user X contained in the task instance creation request;
3) a user X selects a task template B suitable for a model iterative training task from a task template library with high self-definition provided by a scheme solution provider Y through long connection;
4) the solution provider Y creates a brand-New task instance B _ New according to the task template B selected by the user X, sets the index path of the value of all task attributes on the task instance B _ New as the index path of the value of the corresponding task attribute of the task template B in a shallow copy mode, and presents the index path to the user X;
5) a user X issues an instruction for adjusting the values of two task attributes of numbers 01 and 03 from 0 to 1 to a solution provider Y through long connection on the basis of a task instance B _ New according to the actual requirements of the user X;
6) according to the received instruction, the solution provider Y deletes the index paths of the values of the two task attributes of the numbers 01 and 03, and creates a new index path for storing the actual value of '1', so as to obtain a task instance B _ End (namely, deep copy);
7) the solution provider Y returns the created task instance B _ End to the user X through the long connection and releases the long connection for creating the task instance.
After that, the solution provider adjusts the default value of the task attribute (assumed to be numbered 08) of one refresh frequency existing in the task template B from 0.15 to 0.18 through long-term statistical data, so the actual value under the original index path of the value of the task attribute with the number 08 directly adjusted is 0.18, and the task instance B _ End does not modify the task attribute with the number 08 from the task template B, so in the processing mode of "shallow copy", every time the user X performs the operation of the iterative deep learning network through the task instance B _ End, the latest value found by the original index path is refreshed at 0.18.
As can be seen from the above example, the task template B required for creating the user X is located on the cloud platform built by the solution provider Y in the cloud, and the created task instance B _ End is returned to the local of the user X. In addition to the above example, based on the requirement of the user X, the solution provider Y may also return the task template B to the user X, so that the user X may more conveniently generate more task instances according to the requirement of the user X based on the task template B.
With further reference to fig. 5, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of an apparatus for creating a task instance, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be applied to various electronic devices.
As shown in fig. 5, the apparatus 500 for creating a task instance of the present embodiment may include: a target task template determining unit 501, a target task attribute determining unit 502, and an index path setting unit 503. The target task template determining unit 501 is configured to determine a target task template required to be used for creating a target task instance; a target task attribute determining unit 502 configured to determine an unmodified task attribute in the target task instance as a target task attribute; an index path setting unit 503 configured to set an index path of the value of the target task attribute as an index path of the value of the corresponding task attribute in the target task template.
In the present embodiment, in the apparatus 500 for creating a task instance: the specific processing and the technical effects thereof of the target task template determining unit 501, the target task attribute determining unit 502, and the index path setting unit 503 can refer to the related descriptions of step 201 and step 203 in the corresponding embodiment of fig. 2, which are not described herein again.
In some optional implementations of this embodiment, the apparatus 500 for creating a task instance may further include: and the current value query and execution unit is configured to respond to an access instruction aiming at the target task instance, query a current value according to an index path of the value of the target task attribute, and execute a corresponding operation according to the current value.
In some optional implementations of this embodiment, the apparatus 500 for creating a task instance may further include: and the task attribute adjusting unit is configured to respond to a task attribute adjusting instruction aiming at the target task template, and adjust the index path of the original task attribute value or the value stored in the original index path according to the task attribute adjusting instruction.
In some optional implementations of this embodiment, the apparatus 500 for creating a task instance may further include: and the modified value active pushing unit is configured to respond to the modification of the value of any task attribute in the target task template, and actively push the modified value to the running caches of all task instances created through the target task template.
In some optional implementations of this embodiment, the apparatus 500 for creating a task instance may further include: a modified task attribute marking unit configured to mark a target task attribute whose value is modified as a modified task attribute in response to a value of any of the target task attributes being modified;
and the value and index path adjusting unit is configured to delete the index path of the original value of the modified task attribute, create a new index path of the value for the modified task attribute, and store the modified actual value of the modified task attribute to the new index path.
In some optional implementations of this embodiment, the apparatus 500 for creating a task instance may further include: the task template building unit is configured to build a task template according to a task attribute forming mode of the basic task attribute and the user-defined task attribute; and determining whether the actual custom content meets the preset requirement or not by the custom task attribute according to a preset limiting rule.
In some optional implementations of this embodiment, the apparatus 500 for creating a task instance may further include: and the reminding sending unit is configured to respond to the fact that the actual custom content does not accord with the preset requirement, and send a reminding containing custom content limiting information corresponding to the limiting rule through a preset path.
Compared with the prior art that the task instance is completely separated from the task template through 'inheritance', the device for creating the task instance provided by the embodiment sets the index path of the value of the unmodified task attribute as the index path of the value of the corresponding task attribute in the target task template through the technical scheme, so that the value of the unmodified task attribute actually belongs to a common relationship between the task instance and the transaction template, and the modification of all task instances created through the task template can be completed at one time through the modification of only the task template based on the common relationship, and the efficiency is obviously improved.
According to an embodiment of the present application, an electronic device and a computer-readable storage medium are also provided.
FIG. 6 illustrates a block diagram of an electronic device suitable for use in implementing the method for creating task instances of embodiments of the present application. 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 phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 6, the electronic apparatus includes: one or more processors 601, memory 602, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 6, one processor 601 is taken as an example.
The memory 602 is a non-transitory computer readable storage medium as provided herein. Wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method for creating a task instance provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to perform the method for creating a task instance provided herein.
The memory 602, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the method for creating a task instance in the embodiment of the present application (e.g., the target task template determination unit 501, the target task attribute determination unit 502, and the index path setting unit 503 shown in fig. 5). The processor 601 executes various functional applications of the server and data processing by running non-transitory software programs, instructions, and modules stored in the memory 602, that is, implements the method for creating a task instance in the above method embodiments.
The memory 602 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area can store various types of data and the like created by the electronic equipment in the process of executing the method for creating the task instance. Further, the memory 602 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 602 optionally includes memory remotely located from the processor 601, and such remote memory may be connected over a network to an electronic device adapted to perform the method for creating task instances. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device adapted to perform the method for creating a task instance may further comprise: an input device 603 and an output device 604. The processor 601, the memory 602, the input device 603 and the output device 604 may be connected by a bus or other means, and fig. 6 illustrates the connection by a bus as an example.
The input device 603 may receive input numeric or character information and generate key signal inputs related to user settings and function control of an electronic apparatus suitable for performing the method for creating a task instance, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointer, one or more mouse buttons, a track ball, a joystick, or the like. The output devices 604 may include a display device, auxiliary lighting devices (e.g., LEDs), and tactile feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
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 a pointing device (e.g., a mouse or a 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 can 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, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end 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 back-end, 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 clients and servers. A client and server are generally 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.
In this embodiment, the index path of the value of the unmodified task attribute is set as the index path of the value of the corresponding task attribute in the target task template through the above technical solution, so that the value of the unmodified task attribute actually belongs to a common relationship between the task instance and the transaction template, and modification of all task instances created by the task template can be completed at one time by modifying only the task template based on the common relationship, and efficiency is obviously improved.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (16)
1. A method for creating a task instance, comprising:
determining a target task template required to be used for creating a target task instance;
determining the task attribute which is not modified in the target task instance as a target task attribute;
and setting the index path of the value of the target task attribute as the index path of the corresponding task attribute value in the target task template.
2. The method of claim 1, further comprising:
and responding to an access instruction aiming at the target task instance, inquiring a current value according to an index path of the value of the target task attribute, and executing corresponding operation according to the current value.
3. The method of claim 1, further comprising:
and responding to a task attribute adjusting instruction aiming at the target task template, and adjusting an index path of an original task attribute value or adjusting a value stored in the original index path according to the task attribute adjusting instruction.
4. The method of claim 3, further comprising:
and responding to the modification of the value of any task attribute in the target task template, and actively pushing the modified value to the running caches of all task instances created by the target task template.
5. The method of claim 1, further comprising:
in response to the value of any of the target task attributes being modified, marking the modified value of the target task attribute as a modified task attribute;
deleting the index path of the original value of the modified task attribute, creating a new index path of the value for the modified task attribute, and storing the modified actual value of the modified task attribute to the new index path.
6. The method of any of claims 1 to 5, further comprising:
constructing a task template according to a task attribute forming mode of the basic task attribute and the user-defined task attribute; and determining whether the actual custom content meets the preset requirement or not by the custom task attribute according to a preset limiting rule.
7. The method of claim 6, further comprising:
and responding to the fact that the actual custom content does not meet the preset requirement, and sending a prompt containing custom content limiting information corresponding to the limiting rule through a preset path.
8. An apparatus for creating a task instance, comprising:
a target task template determination unit configured to determine a target task template to be used for creating a target task instance;
a target task attribute determining unit configured to determine an unmodified task attribute in the target task instance as a target task attribute;
and the index path setting unit is configured to set the index path of the value of the target task attribute as the index path of the value of the corresponding task attribute in the target task template.
9. The apparatus of claim 8, further comprising:
and the current value query and execution unit is configured to respond to an access instruction aiming at the target task instance, query a current value according to an index path of the value of the target task attribute, and execute a corresponding operation according to the current value.
10. The apparatus of claim 8, further comprising:
and the task attribute adjusting unit is configured to respond to a task attribute adjusting instruction aiming at the target task template, and adjust the index path of the original task attribute value or the value stored in the original index path according to the task attribute adjusting instruction.
11. The apparatus of claim 10, further comprising:
and the modified value active pushing unit is configured to respond to the modification of the value of any task attribute in the target task template, and actively push the modified value to the running caches of all task instances created through the target task template.
12. The apparatus of claim 8, further comprising:
a modified task attribute marking unit configured to mark a target task attribute whose value is modified as a modified task attribute in response to a value of any of the target task attributes being modified;
and the value and index path adjusting unit is configured to delete the index path of the original value of the modified task attribute, create a new index path of the value for the modified task attribute, and store the modified actual value of the modified task attribute to the new index path.
13. The apparatus of any of claims 8 to 12, further comprising:
the task template building unit is configured to build a task template according to a task attribute forming mode of the basic task attribute and the user-defined task attribute; and determining whether the actual custom content meets the preset requirement or not by the custom task attribute according to a preset limiting rule.
14. The apparatus of claim 13, further comprising:
and the reminding sending unit is configured to respond to the fact that the actual custom content does not accord with the preset requirement, and send a reminding containing custom content limiting information corresponding to the limiting rule through a preset path.
15. 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 for creating a task instance of any of claims 1-7.
16. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method for creating a task instance of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010572232.XA CN111736929B (en) | 2020-06-22 | 2020-06-22 | Method, apparatus, device and readable storage medium for creating task instance |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010572232.XA CN111736929B (en) | 2020-06-22 | 2020-06-22 | Method, apparatus, device and readable storage medium for creating task instance |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111736929A true CN111736929A (en) | 2020-10-02 |
| CN111736929B CN111736929B (en) | 2024-04-12 |
Family
ID=72650246
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010572232.XA Active CN111736929B (en) | 2020-06-22 | 2020-06-22 | Method, apparatus, device and readable storage medium for creating task instance |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111736929B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112925855A (en) * | 2021-04-12 | 2021-06-08 | 平安科技（深圳）有限公司 | Theme template synchronization method, device and equipment and storage medium |
| CN113419745A (en) * | 2021-06-24 | 2021-09-21 | 中国建设银行股份有限公司 | Application instance number management method and device, electronic equipment and computer readable medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070074124A1 (en) * | 2005-08-31 | 2007-03-29 | Farn Brian G | System to include multiple instances of data on a web page |
| CN101291344A (en) * | 2008-05-22 | 2008-10-22 | 北京航空航天大学 | Resource status processing method based on aggregation |
| CN104166590A (en) * | 2013-05-20 | 2014-11-26 | 阿里巴巴集团控股有限公司 | Task scheduling method and system |
| CN104965907A (en) * | 2015-06-30 | 2015-10-07 | 小米科技有限责任公司 | Structured object generation method and apparatus |
| CN107038533A (en) * | 2017-04-18 | 2017-08-11 | 北京思特奇信息技术股份有限公司 | A kind of method and system for realizing configurableization workflow examination and approval |
| CN108564281A (en) * | 2018-04-13 | 2018-09-21 | 浙江传媒学院 | The implementation method of outsourcing work task scheduling system based on structuring |
| CN109684053A (en) * | 2018-11-05 | 2019-04-26 | 广东岭南通股份有限公司 | The method for scheduling task and system of big data |
| CN109784716A (en) * | 2019-01-14 | 2019-05-21 | 北京纷扬科技有限责任公司 | The processing method and processing device of task |
| CN111190882A (en) * | 2019-12-03 | 2020-05-22 | 泰康保险集团股份有限公司 | Target template creating method and device, electronic equipment and storage medium |
-
2020
- 2020-06-22 CN CN202010572232.XA patent/CN111736929B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070074124A1 (en) * | 2005-08-31 | 2007-03-29 | Farn Brian G | System to include multiple instances of data on a web page |
| CN101291344A (en) * | 2008-05-22 | 2008-10-22 | 北京航空航天大学 | Resource status processing method based on aggregation |
| CN104166590A (en) * | 2013-05-20 | 2014-11-26 | 阿里巴巴集团控股有限公司 | Task scheduling method and system |
| CN104965907A (en) * | 2015-06-30 | 2015-10-07 | 小米科技有限责任公司 | Structured object generation method and apparatus |
| CN107038533A (en) * | 2017-04-18 | 2017-08-11 | 北京思特奇信息技术股份有限公司 | A kind of method and system for realizing configurableization workflow examination and approval |
| CN108564281A (en) * | 2018-04-13 | 2018-09-21 | 浙江传媒学院 | The implementation method of outsourcing work task scheduling system based on structuring |
| CN109684053A (en) * | 2018-11-05 | 2019-04-26 | 广东岭南通股份有限公司 | The method for scheduling task and system of big data |
| CN109784716A (en) * | 2019-01-14 | 2019-05-21 | 北京纷扬科技有限责任公司 | The processing method and processing device of task |
| CN111190882A (en) * | 2019-12-03 | 2020-05-22 | 泰康保险集团股份有限公司 | Target template creating method and device, electronic equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 施伟斌, 孙未未, 施伯乐: "一种改进的建立XML数据的路径索引的方法", 小型微型计算机系统, no. 04, 21 April 2003 (2003-04-21) * |
| 黄泽谦;彭智勇;李越;彭煜玮;: "一种支持对象代理数据库高效查询处理的索引结构", 计算机学报, no. 08, 15 August 2010 (2010-08-15) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112925855A (en) * | 2021-04-12 | 2021-06-08 | 平安科技（深圳）有限公司 | Theme template synchronization method, device and equipment and storage medium |
| CN113419745A (en) * | 2021-06-24 | 2021-09-21 | 中国建设银行股份有限公司 | Application instance number management method and device, electronic equipment and computer readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111736929B (en) | 2024-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11928432B2 (en) | Multi-modal pre-training model acquisition method, electronic device and storage medium | |
| US20160378734A1 (en) | Visualizing document revisions | |
| US9467533B2 (en) | System and method for developing real-time web-service objects | |
| CN111045985B (en) | File storage processing method, server, electronic device and storage medium | |
| US11080344B2 (en) | Cloud-native documents integrated with legacy tools | |
| CN113268226A (en) | Page data generation method and device, storage medium and equipment | |
| US11080068B2 (en) | Adaptive user-interface assembling and rendering | |
| JP7200277B2 (en) | Method and apparatus, electronic device, storage medium and computer program for identifying word slots | |
| US11514090B2 (en) | Comments-ordering method, apparatus, device and computer storage medium | |
| US20160378735A1 (en) | Metamorphic documents | |
| CN111736929B (en) | Method, apparatus, device and readable storage medium for creating task instance | |
| US20210216212A1 (en) | Method and apparatus for processing data | |
| US10721305B2 (en) | Presenting content using decoupled presentation resources | |
| CN113688612A (en) | Multimodal sharing of content between documents | |
| CN113407284A (en) | Navigation interface generation method and device, storage medium and electronic equipment | |
| CN112528608A (en) | Page editing method and device, electronic equipment and storage medium | |
| CN114706894A (en) | Information processing method, apparatus, device, storage medium, and program product | |
| KR20200114025A (en) | Data conversion server and computer programs | |
| US11308131B2 (en) | Combining visualizations in a business analytic application | |
| WO2024016789A1 (en) | Log data query method and apparatus, and device and medium | |
| US10977428B2 (en) | Content transformations | |
| US20220198301A1 (en) | Method and apparatus for update processing of question answering system | |
| JP7524128B2 (en) | Text prediction method, device, equipment and storage medium | |
| CN114356326A (en) | Management page generation method and device | |
| CN115221451A (en) | Multi-level page switching table data method and device, electronic 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |