Skip to main content

FieldLogs

Using Batch Operations

Batch Operations refer to several processes that are run in a single batch. In FieldLogs, Batch Operations are used in the following cases:

  1. Generating Reports.

  2. Export/Import of Data.

  3. Processing OEM Manuals.

  4. Mass Generation and Mass Deletion of Templates.

You can access the Batch Operations page from the main menu.

BO1.png

The left pane displays a list of Batch Operations. You can filter the list by date range.

BO3.png

You can also filter them based on Type and/or Status.

bofilters.png

A Batch Operation can have one of the following statuses.

  • Scheduled: The Batch Operation has been registered in the system. It will start as soon as the execution resources are available.

    Note

    The Operations are not always executed in the order they were registered.

  • Running: The Batch Operation is currently being executed.

  • Paused: The Batch Operation is paused. It will resume as soon as the execution resources are available.

  • Completed: The Batch Operation has been successfully executed.

  • Completed with errors: The Batch Operation has been fully executed. However, some errors occurred during execution.

  • Expired: Some Batch Operations result in a file download. This status indicates that the file is no longer available for download.

    Note

    This status applies only to Batch Operations that have a file to be downloaded at the end of the Operation, eg., a report or a data export. By default, the download window for the file is 10 days.

  • Failed: The Batch Operation was not fully executed.

Errors During Batch Operations

When a Batch Operation is processed, it may generate errors. Based on their severity levels, these errors can be classified into two groups.

  1. Warning: Minor errors that usually do not affect the process completion

  2. Fatal: Errors that prevent the successful completion of the process.

S.no

WARNING

FATAL

1

Contains the text 'Warning'.

Contains the text 'FATAL'.

2

Warnings are usually non-critical and do not affect the Batch Operation.

They can be ignored if they do not affect the outcome of the operation.

Critical errors indicate that a serious error has occurred.

The Batch Operation will likely fail, and the FieldLogs support team must be notified.

3

Indicates a non-critical discrepancy between the data expected and the data being parsed.

Indicates that an error has occurred during an important stage of the process.

4

Warnings serve to inform us. Further investigation can be done.

Errors indicate that the process failed, or partially worked.

5

Example: When a picture file is referenced but cannot be found.

Example: Unexpected errors thrown by the operation.

Errors in Batch Operations while Processing OEM Manuals

The errors thrown while processing OEM Manuals are listed below.

FATAL

S.no

Error Text

Description

Recommended Action

1

FATAL: Unexpected error.

The software threw an unexpected error.

Please contact FieldLogs support.

2

FATAL: Error while parsing a file <<filename>>

While processing a baseline, an error was encountered while parsing.

The filename is included in the error message.

This error could be Software-related or Manual-related.

Please contact FieldLogs support.

3

FATAL: Failed to ensure repository element for <<picDocKey>>.

While processing a baseline, a converted picture could not be stored.

The picture reference is included in the error message.

This error is Software-related .

Please contact FieldLogs support.

4

FATAL: <<InsertImpacts>>.

During Screening, a Screening Hit could not be stored in the Database.

This error is Software-related .

Please contact FieldLogs support.

The warnings thrown while processing OEM Manuals are listed below.

WARNING

S.no

Error Text

Reason

Recommended Action

Occurs while processing a PDF file

1

A pdf file with the same name <<fileName>> already exists in the manual.

While processing PDF files, another PDF file with the same name exists.

This error is Manual-related.

This indicates an issue with the filename used.

Please get in touch with FieldLogs Support if further assistance is required.

Occurs while processing a Picture Conversion

2

Failed to convert a picture file <<fileName>> to PNG format.

While processing picture files, the picture file could not be converted to a PNG format.

This error could be Software-related or Manual-related.

This indicates an issue with a picture file in the Manual.

Please get in touch with FieldLogs Support if further assistance is required.

Occurs while processing a Baseline

3

The interactivity file cannot be found.

While processing VRML files, the interactivity file was found missing.

This error is Manual-related.

This indicates a missing file.

Please get in touch with FieldLogs Support if further assistance is required.

Occurs during the Step and HTML generation from a manual in SGML format

4

Failed to parse SGML conditional effectivity from node <<nodeName>> with number <<name of SB or COC>>.

An unexpected format was encountered when parsing SB or COC Effectivity data. The SB or COC Effectivity data is not in line with the SGML specifications

The error message contains:

  • the SGML node name, and

  • the name of SB or COC.

This error is Manual-related.

This indicates an issue with the content of the manual.

Please contact FieldLogs support.

5

Invalid Entity String in SGML file <<malformedEntity>>

A malformed Entity has been found in the SGML file. The error message contains the malformed Entity.

This error is Manual-related.

This indicates an issue with the content of the manual.

Please contact FieldLogs support.

6

Exception processing Entity <<malformedEntity>>

A malformed Entity caused an error in the process. The error message contains the malformed Entity.

This error is Manual-related.

This indicates an issue with the content of the manual.

Please contact FieldLogs support.

7

Found unknown Entity <<fileName>>

The file declared in the SGML as an attachment could not be found.

This error is Manual-related.

This indicates a missing file or an issue with the content of the manual.

Please contact FieldLogs support.

Occurs while processing a manual in S1000D format

8

No S1000D file could be found in the file <<fileName >>.zip

The uploaded zip file is incorrect. It does not contain any S1000D data.

This error is Manual-related.

This indicates that no XML file could be found in the zip file.

Please contact FieldLogs suppport.

Occurs during the Step and HTML generation from a manual in S1000D format

9

Empty InternalRef.

Data was found missing while validating Internal References.

This error is Manual-related.

This indicates an issue with the content of the manual.

Please contact FieldLogs support.

10

Unknown InternalRef type.

An unexpected type of internal reference was encountered.

This error is Manual-related.

This indicates an issue with the content of the manual.

Please contact FieldLogs support.

Occurs during the Tool Data Extraction from an ITEM manual in S1000D format

11

Tool cannot be parsed.

Data was found missing.

This error is Software-related.

Please contact FieldLogs support.

12

More data than expected.

An unexpected format was encountered.

This error is Software-related or Manual-related.

Please contact FieldLogs support.

13

Can't parse tool number/name in file <<fileName>>.

An unexpected format was encountered.

The number and the name of the tool could not be found in the title, dmAddress, or infoName tags.

This error is Software-related.

Please contact FieldLogs support.

14

Can't parse tool main para in description in file <<fileName>>.

An unexpected format was encountered or data was found missing.

This error is Software-related.

Please contact FieldLogs support.

15

Tool data too large to be stored in the DB.

An unexpected format was encountered.

This error is Software-related.

Please contact FieldLogs support.

16

Can’t parse table in file <<fileName>>.

Data was found missing.

This error is Software-related.

Please contact FieldLogs support.

17

Error while parsing tool quantity in file <<fileName>>.

An unexpected format was encountered in the file.

This error is Software-related.

Please contact FieldLogs support.

18

Can't parse tool description in file <<fileName>>.

An unexpected format was encountered or data was found missing.

This error is Software-related.

Please contact FieldLogs support.

19

Unrecognized tool characteristics structure in file <<fileName>>.

An unexpected format was encountered or data was found missing in the file.

This error is Software-related.

Please contact FieldLogs support.

20

Unrecognized tool status structure in file <<fileName>>.

An unexpected format was encountered or data was found missing in the file.

This error is Software-related.

Please contact FieldLogs support.

21

Error in tool structure in file <<fileName>>.

An unexpected format was encountered or data was found missing in the file.

This error is Software-related.

Please contact FieldLogs support.

Occurs during Parts Data Parsing of a manual in S1000D format

22

Couldn't parse part SB <<sbText>> in file <<fileName>>.

Data was found missing in the file.

Textual data about the SB that could not be parsed is included in the error message.

This error is Manual-related.

This indicates an issue with the content of the Manual.

Please contact FieldLogs support.

23

Error while parsing sbs of part <<partNumber>> in file <<fileName>>.

An unexpected format was encountered.

The part number is included in the error message.

This error is Manual-related.

This indicates an issue with the content of the Manual.

Please contact FieldLogs support.

24

Error while parsing CSN <<csn>> in file <<fileName>>.

An unexpected format was encountered.

The Catalog Sequence Number (CSN) is included in the error message.

This error is Manual-related.

This indicates an issue with the content of the Manual.

Please contact FieldLogs support.

25

Unknown relation type parsed <<replacementCode>>.

An unexpected format was encountered.

A replacement code is a code that is not recognized by the system.

This error is Manual-related.

This indicates an issue with the content of the Manual.

Please contact FieldLogs support.

26

Error while parsing part quantity for CSN <<CSN>> in file <<fileName>>.

An unexpected format was encountered.

The Catalog Sequence Number (CSN) is included in the error message.

This error is Manual-related.

This indicates an issue with the content of the Manual.

Please contact FieldLogs support.

27

Error: Part <<partName>> (<<partCSN>>) can't be added in the DB from file <<fileName>>.

An unexpected format was encountered.

The Catalog Sequence Number (CSN) is included in the error message.

This error is Manual-related.

This indicates an issue with the content of the Manual.

Please contact FieldLogs support.

In this section: