JP4890223B2 - Electronic device, report creation method and report creation program - Google Patents

Description

  The present invention relates to an electronic device, a report creation method, and a report creation program.

  2. Description of the Related Art Conventionally, devices having a function of outputting the operation state and the like as a report (hereinafter referred to as “report function”) have been provided (for example, Patent Document 1, Patent Document 2, and Patent Document 3). In particular, it is well known that a transmission history, a non-delivery report, and the like are output from a facsimile machine.

On the other hand, some recent image forming apparatuses are equipped with a CPU as in a general-purpose computer, and each function is realized by application control. In addition, applications can be added (installed) or deleted (uninstalled) after shipment, and can be customized by implementing an application suitable for the user's usage environment (for example, Patent Documents). 4).
JP-A-10-322535 Japanese Patent Laid-Open No. 10-173698 JP-A-11-298662 JP 2005-269619 A

  However, in the conventional report function, information to be reported is fixed, and the output format of the report is also fixedly mounted. Therefore, when an application is added and it is desired to realize a report function for the application, there is a problem that a report function corresponding to the application must be implemented for each application.

  SUMMARY An advantage of some aspects of the invention is that it provides an electronic apparatus, a report creation method, and a report creation program capable of realizing a versatile report output function.

Accordingly, in order to solve the above-described problem, the present invention provides an electronic device that can execute a plurality of programs, and among the plurality of programs, a program that uses a service that outputs a report is an output target of the report. that information to create a specification information specification is defined in the report according to accept the registration of the created specification information, it acquires the specification management unit that manages the information that is the output target, the specification According to the information, there is provided a report creation means for creating the report related to the information, and a report output means for outputting the report created by the report creation means.

  In such an electronic device, a versatile report output function can be realized.

  According to the present invention, it is possible to provide an electronic device, a report creation method, and a report creation program capable of realizing a versatile report output function.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating an example of a hardware configuration of a multifunction machine according to an embodiment of the present invention. Here, the multifunction peripheral refers to an image forming apparatus that realizes a plurality of functions such as a printer, a copy, a scanner, or a FAX in a single casing. As hardware of the multifunction machine 1, there are a controller 201, an operation panel 202, a facsimile control unit (FCU) 203, an imaging unit 121, and a printing unit 122.

  The controller 201 includes a CPU 211, ASIC 212, NB221, SB222, MEM-P231, MEM-C232, HDD (hard disk drive) 233, memory card slot 234, NIC (network interface controller) 241, USB device 242, IEEE 1394 device 243, and Centronics device. 244.

  The CPU 211 is an IC for various information processing. The ASIC 212 is an IC for various image processing. The NB 221 is a north bridge of the controller 201. The SB 222 is a south bridge of the controller 201. The MEM-P 231 is a system memory of the multifunction machine 1. The MEM-C 232 is a local memory of the multifunction machine 1. The HDD 233 is a storage of the multifunction device 1. The memory card slot 234 is a slot for setting the memory card 235. The NIC 241 is a controller for network communication using a MAC address. The USB device 242 is a device for providing a USB standard connection terminal. The IEEE 1394 device 243 is a device for providing a connection terminal of the IEEE 1394 standard. The Centronics device 244 is a device for providing a Centronics specification connection terminal. The operation panel 202 is hardware (operation unit) for an operator to input to the multifunction device 1 and hardware (display unit) for an operator to obtain an output from the multifunction device 1.

  FIG. 2 is a diagram illustrating a software configuration example of the multifunction peripheral according to the embodiment of the present invention. The software shown in FIG. 2 is stored in the MEM-C 232, for example, and is processed by the CPU 211 to cause the MFP to execute its function.

  As shown in FIG. 2, the software in the multifunction device 1 includes a user interface layer 10, a control layer 20, an application logic layer 30, a device service layer 40, a device control layer 50, and the like. In addition, the vertical relationship of each layer in the drawing is based on the calling relationship between layers. That is, basically, the upper layer in the figure calls the lower layer.

  The user interface layer 10 is a part in which functions for receiving execution requests of various services (for example, copy, print, scan, FAX transmission) are implemented. For example, the communication server unit 11 and the local UI unit 12 A program is included. For example, the communication server unit 11 receives a request from a client PC (Personal Computer) (not shown) via a network. For example, the local UI unit 12 receives a request input via the operation panel 202. The request accepted by the user interface layer 10 is transmitted to the control layer 20.

  The control layer 20 is a part in which a function for controlling processing for realizing a requested service is implemented. For example, a program such as a request management unit 21, an in-flight monitoring unit 22, and a plug-in management unit 23 Is included. The request management unit 21 controls, for example, processing for realizing a service requested to be executed via the operation panel 202. The in-machine monitoring unit 22 monitors an event (change in state or the like) that occurs in the multifunction device 1 and controls processing for realizing a service in response to detection of the event. The plug-in management unit 23 manages various software (programs) in the application logic layer 30. The management includes installation or uninstallation of the various software.

  The application logic layer 30 is a part on which an application that realizes a service provided by the multifunction device 1 or a group of components that realize a part of the function of the application is mounted.

  Software corresponding to an application that implements a service in the multifunction device 1 is called an “activity”. In the figure, a copy activity 331, a printer activity 332, a report activity 333, and the like are shown as examples of activities. Each activity is constituted by a combination (connection) of one or more parts in the application logic layer 30. In the present embodiment, each component is referred to as a “filter”. This is because the software architecture of the multifunction device 1 is based on a concept called “pipe & filter”.

  FIG. 3 is a diagram for explaining the concept of the pipe and filter. In FIG. 3, “F” indicates a filter, and “P” indicates a pipe. As shown in the figure, each filter is connected by a pipe. The filter converts the input data and outputs the result. The pipe transmits the data output from the filter to the next filter.

  That is, in the MFP 1 according to the present embodiment, each service is regarded as a series of “conversions” for documents (image data). Each service of the multi-function peripheral can be generalized as being composed of document input, processing, and output. Therefore, “input”, “processing”, and “output” are regarded as “conversion”, and a software component that realizes one “conversion” is configured as a filter. A filter that realizes input is particularly called an “input filter”. A filter that realizes processing is particularly referred to as a “processing filter”. Further, a filter that realizes output is particularly referred to as an “output filter”. Each filter is independent, and basically there is no dependency relationship (call relationship) between the filters. Therefore, addition (installation) or deletion (uninstallation) is possible in units of filters. For the pipe, for example, a storage area such as a memory or a hard disk is used.

  In FIG. 2, a reading filter 301, a stored document reading filter 302, a mail receiving filter 303, a FAX receiving filter 304, a PC document receiving filter 305, a report filter 306, and the like are included as input filters.

  The reading filter 301 controls reading of image data by the scanner and outputs the read image data. The stored document read filter 302 reads document data (image data) stored in the HDD 233 of the multifunction machine 1 and outputs the read data. The mail reception filter 303 receives an e-mail and outputs data included in the e-mail. The FAX reception filter 304 controls FAX reception and outputs received data. The PC document reception filter 305 receives image data from a client PC (not shown) and outputs the received image data. The report filter 306 outputs various setting information and management information of the multifunction device 1 and history information output from each software component as a report formatted in a predetermined format.

  The processing filters include a document processing filter 311 and a marking generation filter 312. The document processing filter 311 performs predetermined image conversion processing (aggregation, enlargement, reduction, etc.) on the input data and outputs it. The marking generation filter 312 generates marking data such as a barcode to be combined with the image data.

  The output filters include a print filter 321, a stored document registration filter 322, a mail transmission filter 323, a FAX transmission filter 324, a PC document transmission filter 325, a preview filter 326, a marking analysis filter 327, and the like.

  The print filter 321 causes the plotter to output (print) the input data. The stored document registration filter 322 stores the input data in the HDD 233 of the multifunction machine 1. The mail transmission filter 323 transmits the input data attached to the e-mail. The FAX transmission filter 324 transmits the input data by FAX. The PC document transmission filter 325 transmits the input data to the client PC. The preview filter 326 displays the input data on the operation panel 202 of the multifunction device 1 as a preview. The marking analysis filter 327 detects marking data from the input image data and outputs data expressed by the marking data.

  As described above, each activity is constituted by the connection of these filters. For example, the copy activity 331 includes a read filter 301, a document processing filter 311, and a print filter 321. Therefore, the copy activity 331 causes the imaging unit 121 to read image data from the original, performs image processing on the image data as necessary, and then prints the image data on the printing unit 122. Let

  The printer activity 332 is configured by connecting a PC document reception filter 305, a document processing filter 311, and a print filter 321. Accordingly, the printer activity 332 receives image data from the client PC, performs image processing on the image data as necessary, and then causes the printing unit 122 to print the image data.

  The report activity 333 is configured as shown in FIG. FIG. 4 is a diagram illustrating a configuration example of a report activity. As shown in FIG. 4, the report activity 333 includes a connection between a report filter 306 serving as an input filter and an output filter. In the figure, the reason why the output filter is not specified is that the output filter differs depending on the output form. For example, when outputting a report as a paper document, the print filter 321 is used as an output filter. Further, when the report is transmitted by mail, the mail transmission filter 323 is used as an output filter. With such a configuration, the report activity 333 includes setting information for various components of the MFP 1, management information managed by the various components, history information recorded according to processing of the various components, and the like. Provides a service (hereinafter referred to as “report service”) for outputting a report for reporting to the user. That is, in the multi-function device 1, the report output function is realized in an integrated manner by the report activity 333, not for each component.

  Note that the addition of a new activity in the application layer 30 can be realized by connecting a filter. If there is no filter suitable for the new activity, it is possible to add a new activity by installing the filter and connecting the filter with another filter.

  Returning to FIG. The device service layer 40 is a portion in which lower functions commonly used by each filter in the application logic layer 30 are mounted, and includes, for example, an image pipe 41, a data management unit 42, a report definition unit 43, and the like. . The image pipe 41 realizes the above-described pipe function. That is, output data from a certain filter is transmitted to the next filter. The data management unit 42 manages the management information, setting information, history information, and the like in addition to a database in which user information is registered and a database in which document or image data is stored. The report definition unit 43 will be described later.

  The application logic layer 30 is a portion that can be changed such as addition or deletion of activities or filters, while the device service layer 40 is a fixed portion that restricts at least component deletion.

  The device control layer 50 is a part on which a group of program modules called a driver that controls a device (hardware) is mounted. For example, the scanner control unit 51, the plotter control unit 52, the storage control unit 53, and the FCU control unit 54. And a network control unit 55 and the like. Each control unit controls a device attached to the name of the control unit.

  The report service of the multifunction device 1 will be described in more detail. FIG. 5 is a diagram illustrating a class configuration example of each component related to the report service. FIG. 5 shows a class configuration of the report filter 306 in the application logic layer 30 and the report definition unit 43 in the device service layer 40.

  The report definition unit 43 includes a report definition document class 431, a report format class 432, a report item class 433, a logical report class 434, a report definition management class 435, and the like. The report definition document class 431 is a class representing a “report definition document”, and an instance (report definition document object 431I) is generated for each report definition document. Here, the “report definition document” refers to information in which the specification of the report is defined, and is created for each information to be output of the report (hereinafter referred to as “report source information”). be registered. In other words, a component that uses the report service needs to create a report definition document (that is, an instance of the report definition document class 431) that defines the specifications desired by the component and register it in the report definition unit 43 in advance. There is.

  Examples of information defined in the report definition document include a report name, a report format, an output method, an output timing, a storage location of report source information, and the like. The report name is the name of the report. The report format is information that defines the output format of the report. In the report format, for example, mapping information between report source information such as setting information and history information and a report is defined. More specifically, the arrangement (layout) of each item constituting the report source information on the report is defined in, for example, an XML format. The output method is information that defines a report output method (output destination), such as printing, mail transmission, and FAX transmission. The output timing is information that defines the timing for outputting a report. The output timing is set according to conditions such as the occurrence of various events (report output instruction by the user, occurrence of abnormality of the multifunction device 1), and the amount of report source information accumulated reaching a predetermined amount. The storage location of the report source information is information for identifying the storage location of the report source information, and corresponds to, for example, a file name or a URL. The report definition document is uniquely identified by the report ID. Therefore, each instance of the report definition document class 431 (report definition document object 431I) is managed in association with the report ID, and is identified by the report ID.

  The report format class 432 is a class that represents the report format described above, and an instance (report format object 432I) is generated for each report format. The report item class 433 is a class that represents each item (item) constituting the report, and an instance (report item object 433I) is generated for each item. The logical report class 434 is a class representing a report, and an instance (logical report object 434I) is generated for each output report. The logical report object 434I is generated according to the report definition document by the report definition document object 431I. The generated logical report object 434I is converted into image data and output by an output method according to the report definition document output method.

  The report definition management class 435 is a class that accepts and manages registration of a report definition document (strictly speaking, a report definition document object 431I that represents a report definition document), and an instance (report definition management object 435I) is a report One exists in the definition unit 43.

  On the other hand, the report filter 306 includes a report filter class 3061, a report filter job 3062, a report operation condition class 3063, and the like. The report filter class 3061 is a class that represents the report filter 306. The report filter job class 3062 is a class that controls the processing (job) of the report filter 306. The report operation condition class 3063 is a class that holds operation conditions related to the job of the report filter 306. For example, the report operation condition class 3063 holds a report ID as information for identifying a report to be processed.

  In FIG. 5, a component 340 is an example of a component (filter) that uses the report service in the application layer 30. The component 340 includes a concrete report item class 341, a concrete report format class 342, and a concrete report definition class 343. These are classes that inherit the report item class 433, the report format class 432, and the report definition class 431, and are extended for the component 340. That is, the report item class 433, the report format class 432, and the report definition document class 431 can be extended as necessary in the component that uses the report service. By extending the class, the report format can be customized beyond the range that can be set by the report definition document. However, inheritance and extension of these classes are not necessarily required in a component that uses the report service.

  Hereinafter, a processing procedure of the multifunction machine 1 will be described. FIG. 6 is a sequence diagram for explaining report creation and output processing in the multifunction peripheral. In FIG. 6, a component 350 is an example of a component (program) that uses the report service. For example, the component 350 is a filter in the application logic layer 30 or a component in the control layer 20. The component 350 registers history information recorded each time the function is executed, or management information or setting information (report source information) for executing the function in the data management unit 42 in a predetermined format. For example, the data management unit 42 stores the report source information as a file in the HDD 233 via the storage control unit 53. In FIG. 6, a process for creating and outputting a report based on the report source information will be described.

  For example, when the multifunction device 1 is turned on and the multifunction device 1 is activated, the plug-in management unit 22 initializes each filter and the like in the application logic layer 30. The component 350 is also instructed to be initialized by the plug-in management unit 22 (S101). In response to the initialization instruction, the component 350 generates a report definition document object 431I (S102). At this time, the component 350 sets a report name, an output method, an output timing, and the like in the report definition document object 431I.

  Subsequently, the component 350 generates a report format object 432I (S103). At this time, the component 350 registers mapping information including arrangement information of each item constituting the report source information in the report format object 432I. Subsequently, after registering the report format object 432I in the report definition document object 431I, the component 350 registers the report definition document object 431I together with its report ID in the report definition management object 435I (S104). The report definition management object 435I manages the report ID and the report definition document object 431I in association with each other. Strictly speaking, a report item object 433I is generated for each item constituting the report source information and the report item object 433I is registered in the report definition document object 431I, but is omitted for convenience in the drawing.

  As described above, the report definition document of the component 350 is registered in the report definition unit 43. For other filters and the like, those using the report service execute the same processing as the component 350. Therefore, various report definition documents can be registered in the report definition unit 43 according to the report source information.

  Thereafter, when any event occurs in the device (system) in the process of using the multifunction device 1, the event is notified to the report activity 333 (S105-1). In addition, when a report output request is explicitly requested by the user through an operation via the operation panel 202, the request event is notified to the report activity 333 (S105-2). In response to the notification of these events, the report activity 333 requests the report definition management object 435I to search for the report definition document using the notified event as a search condition regarding the output timing (S106).

  The report definition management object 435I searches the registered report definition document object 431I for an event whose output timing is the event specified in the search condition (S107). For example, when the event that occurred in step S105-1 is “FAX transmission completion” and the output timing related to the report definition document object 431I registered by the component 350 is “FAX transmission completion”, the report definition document The object 431I is searched. Also, if the output timing of the report definition document object 431I registered by the component 350 is “completion of 10 fax transmissions”, the current fax transmission may be the 10th since the last report output. For example, the report definition document object 431I is retrieved.

  If a report to be output is explicitly specified by the user in step S105-2, the report definition document 431I related to the specified report is searched in step S107.

  In any case, the report definition management object 435I returns the report ID associated with the searched report definition document object 431I to the report activity 333. If the corresponding report definition document object 431I does not exist, that fact is returned, and the subsequent processing (report creation and output) is not executed.

  When the report ID is returned from the report definition management object 435I, the report activity 333 specifies the report ID and requests the report filter 306 to execute the report creation process (S109). The report ID specified in the request is registered in the report operation condition object 3063I of the report filter 306.

  The report filter 306 specifies a report ID and requests the report definition management object 435I to create a report (S110). The report definition management object 435I requests the report definition document object 431I associated with the specified report ID to create a report (S111). The report definition document object 431I specifies the “storage location of the report source information” set in itself as information constituting the report definition document, and requests the data management unit 42 to acquire the report source information (S112). . The data management unit 42 acquires report source information (for example, transmission history accumulated by the FAX transmission filter 224) from the designated storage location (file or the like), and returns it to the report definition document object 431 (S113).

  The report definition document object 431I that has acquired the report source information sets the report source information in the report format object 432I registered in itself (S114). Subsequently, the report definition document object 431I converts (formats) report source information in an arbitrary format for each component into a format defined in the report format object 432I (S115). Specifically, the logical report object 434I is generated as a result of applying the format defined in the report format object 432I to the report source information (S116). Accordingly, the generated logical report object 434I holds the value and information indicating the arrangement position and the like (hereinafter referred to as “report information”) for each item to be output as a report.

  Subsequently, the report filter 306 instructs the logical report object 434I to convert it into image data (S117). The logical report object 434I generates image data of the report based on the report information set for itself (S118). The report filter 306 outputs the generated image data to the image pipe 41 (S119).

  When detecting the input of image data to the image pipe 41, the output filter 320 reads the image data from the image pipe 41 (S120) and outputs it (S121). For example, when the output filter 320 is the print filter 321, the image data is printed by the printing unit 122. The output filter is selected according to the output method in the report definition document.

  FIG. 7 is a diagram illustrating a first example of an output image of a report. FIG. 7 shows an example in which the contents of the address book managed by the multifunction device 1 are output as a report. In this report, for each record registered in the address book, a registration number, a user name, a fax number, a mail address, or the like is output. In this case, information recorded in a predetermined format as an address book is output in accordance with a report definition document format corresponding to the address book.

  FIG. 8 is a diagram illustrating a second example of an output image of a report. In the example of FIG. 8, an example is shown in which the print filter 321 outputs an error history in which error information generated when printing image data is recorded. In the report, for each job in which an error has occurred, an ID, a user ID or user name, a document name, and a creation date / start date / time are output. In this case, information recorded in a predetermined format as an error history is output in accordance with a report definition document format corresponding to the error history.

  As described above, the multi-function device 1 according to the embodiment of the present invention can register a report definition document in each component (program) that uses a report service, and can create a report according to the report definition document. Has a report creation function. Therefore, each component only needs to define a report definition document, and it is not necessary to implement logic for creating and outputting a report for each component. Such a situation also applies to newly added components, and it is possible to flexibly cope with the addition of new components.

  In addition, since a report format is defined in the report definition document, and the report is generated according to the format, the report can be output in a different format according to the report source information while being general-purpose.

  The report filter 306 in the application logic layer 30 can be uninstalled. However, the component (report definition unit 43) for registering and managing the report definition document in the multifunction device 1 is not in the report filter 306. The device service layer 40 is a fixed part. Therefore, each component can use the report service without having a dependency relationship with the report filter 306. Therefore, even when the report filter 306 is uninstalled, it is possible to avoid a problem in the operation of each component or the failure to compile the source code of each component.

  In the present embodiment, the multifunction peripheral (image forming apparatus) has been described as an example of an electronic apparatus. However, an electronic apparatus that can execute a plurality of programs other than the image forming apparatus and in which report source information is recorded. The present invention can be effectively applied to any device.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

FIG. 2 is a diagram illustrating an example of a hardware configuration of a multifunction machine according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a software configuration example of a multifunction machine according to an embodiment of the present invention. It is a figure for demonstrating the concept of a pipe & filter. It is a figure which shows the structural example of a report activity. It is a figure which shows the class structural example of each component regarding a report service. FIG. 10 is a sequence diagram for explaining report creation and output processing in a multifunction peripheral. It is a figure which shows the 1st example of the output image of a report. It is a figure which shows the 2nd example of the output image of a report.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 MFP 10 User interface layer 11 Communication server part 12 Local UI part 20 Control layer 21 Request management part 22 In-machine monitoring part 23 Plug-in management part 30 Application logic layer 40 Device service layer 41 Image pipe 42 Data management part 43 Report definition part 50 Device Control Layer 51 Scanner Control Unit 52 Plotter Control Unit 53 Storage Control Unit 54 FCU Control Unit 55 Network Control Unit 201 Controller 202 Operation Panel 203 Facsimile Control Unit 211 CPU
212 ASIC
221 NB
222 SB
231 MEM-P
232 MEM-C
233 HDD
234 Memory card slot 235 Memory card 241 NIC
242 USB device 243 IEEE 1394 device 244 Centronics device 301 Reading filter 302 Storage document reading filter 303 Mail reception filter 304 FAX reception filter 305 PC document reception filter 306 Report filter 311 Document processing filter 312 Marking generation filter 321 Print document 322 Storage document registration filter 323 Mail transmission filter 324 FAX transmission filter 325 PC document transmission filter 326 Preview filter 327 Marking analysis filter 431 Report definition document class 432 Report format class 433 Report item class 434 Logical report class 435 Report definition management class 3061 Report filter class 3062 Report filter job 3036 report Door operating conditions class

Claims (15)

An electronic device capable of executing a plurality of programs,
Among the plurality of programs, a program that uses a service that outputs a report creates specification information in which the specification of the report is defined according to information to be output of the report ,
A specification management means for accepting and managing registration of the created specification information;
Report creation means for obtaining information to be output and creating the report related to the information according to the specification information;
An electronic apparatus comprising: a report output unit that outputs the report created by the report creation unit. The specification information includes format information that defines the format of the report,
The electronic apparatus according to claim 1, wherein the report creation unit creates the report according to a format defined by the format information. The specification information defines the timing for outputting the report,
The specification management means searches for the specification information corresponding to the event corresponding to the event from the managed specification information according to the event that occurs in the electronic device,
The electronic apparatus according to claim 1, wherein the report creating unit creates a report related to the searched specification information. The specification information defines the output method of the report,
4. The electronic apparatus according to claim 1, wherein the output unit outputs the report to an output destination corresponding to the output method. The specification information shows a storage location of the information to be output,
5. The electronic apparatus according to claim 1, wherein the report creation unit acquires the information to be output from the storage location. A report creation method executed by an electronic device capable of executing a plurality of programs,
Among the plurality of programs, a program that uses a service that outputs a report creates a specification information in which a report specification is defined according to information to be output of the report ;
A specification management procedure for accepting and managing registration of the created specification information;
A report creation procedure for acquiring the information to be output and creating the report related to the information according to the specification information;
And a report output procedure for outputting the report created in the report creation procedure. The specification information includes format information that defines the format of the report,
7. The report creation method according to claim 6, wherein the report creation procedure creates the report according to a format defined by the format information. The specification information defines the timing for outputting the report,
The specification management procedure searches for specification information corresponding to the event corresponding to the event from the specification information being managed according to an event occurring in the electronic device,
8. The report creation method according to claim 6, wherein the report creation procedure creates a report related to the searched specification information. The specification information defines the output method of the report,
The report creation method according to claim 6, wherein the output procedure outputs the report to an output destination corresponding to the output method. The specification information shows a storage location of the information to be output,
The report creation method according to claim 6, wherein the report creation procedure acquires information to be output from the storage location. To electronic devices that can execute multiple programs,
Among the plurality of programs, a program that uses a service that outputs a report creates a specification information in which a report specification is defined according to information to be output of the report ;
A specification management procedure for accepting and managing registration of the created specification information;
A report creation procedure for acquiring the information to be output and creating the report related to the information according to the specification information;
A report creation program for executing a report output procedure for outputting the report created in the report creation procedure. The specification information includes format information that defines the format of the report,
12. The report creation program according to claim 11, wherein the report creation procedure creates the report according to a format defined by the format information. The specification information defines the timing for outputting the report,
The specification management procedure searches for specification information corresponding to the event corresponding to the event from the specification information being managed according to an event occurring in the electronic device,
13. The report creation program according to claim 11, wherein the report creation procedure creates a report related to the searched specification information. The specification information defines the output method of the report,
The report creation program according to claim 11, wherein the output procedure outputs the report to an output destination corresponding to the output method. The specification information shows a storage location of the information to be output,
The report creation program according to claim 11, wherein the report creation procedure acquires information to be output from the storage location.

Images