Scribd Logo
Upload

Welcome to Scribd!

  • Exception Handling

    Uploaded by

    Rio Pramana
    18 views2 pages
    1. The document checks if an Attachment folder is empty, and if not empty sets error and log variables before aborting the job. 2. It checks if an AttachmentInvoice variable is null, and if not null checks the invoice file count and name of sheets, setting detection variables. If errors are found it sets error and log variables before aborting. 3. It repeats the same checks for Attachment CN and AttachmentInventory variables. 4. The next process checks the detection variables values, and if errors are found it sets error and log variables before aborting, otherwise it returns Success.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    1. The document checks if an Attachment folder is empty, and if not empty sets error and log variables before aborting the job. 2. It checks if an AttachmentInvoice variable is null, and if not null checks the invoice file count and name of sheets, setting detection variables. If errors are found it sets error and log variables before aborting. 3. It repeats the same checks for Attachment CN and AttachmentInventory variables. 4. The next process checks the detection variables values, and if errors are found it sets error and log variables before aborting, otherwise it returns Success.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    18 views2 pages

    Exception Handling

    Uploaded by

    Rio Pramana
    1. The document checks if an Attachment folder is empty, and if not empty sets error and log variables before aborting the job. 2. It checks if an AttachmentInvoice variable is null, and if not null checks the invoice file count and name of sheets, setting detection variables. If errors are found it sets error and log variables before aborting. 3. It repeats the same checks for Attachment CN and AttachmentInventory variables. 4. The next process checks the detection variables values, and if errors are found it sets error and log variables before aborting, otherwise it returns Success.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 2

    1.

    Check if Attachment folder is empty


    ${ArchivePath}/${ServerNumber}/${DBLocationFolder}/Attachment
    True: Set variables error & log to db -> delete filenames from result -> Abort job
    2. Check if ${AttachmentInvoice} is not null
    True:
    a. Check count Invoice file
    Eval total files count check if greater than 0
    ${ArchivePath}/${ServerNumber}/${DBLocationFolder}/Attachment
    ${AttachmentInvoice}
    False: Set InvoiceFileDetect variable to false
    True:
    b. Set InvoiceFileDetect variable to true
    c. Check Sheet Invoice
    Input ${ArchivePath}/${ServerNumber}/${DBLocationFolder}/Attachment
    ${AttachmentInvoice} no fields
    Additional input fields sheetname = sheet
    Get ${SheetnameInvoice}
    Filter sheet IN LIST ${SheetnameInvoice}
    …
    Set variable InvoiceSheetDetect to true if there is a sheet with the correct name
    format
    If false, then set variables error, log to db, and abort job
    3. Check Var Attachment CN (Same)
    4. Check Var AttachmentInventory (Same)

    Next process: Check variables value

    1. Check Var AttachmentInvoice


    If ${AttachmentInvoice} is not null, then check file invoice
    Else, go to next
    a. Check file invoice
    If InvoiceFileDetect is true, go to next
    Else, set variables error, log to db, abort job
    2. Check Var AttachmentCN (Same)
    3. Check Var AttachmentInventory (Same)
    Next process is the same, but check for sheet (InvoiceSheetDetect, CNSheetDetect, etc.)

    At this point, if there is no error/abort job, return Success

    You might also like