Use Case 4: Customizing application logic of SyteLine stored procedure - EXTGEN

Use Case #4: Customizing application logic of SyteLine stored procedure - EXTGEN

Scope: Chaining business logic to execute one procedure after another, including custom ReplDoc-based inbound BODs within OnInboundBodProcessedSp, persisting tmp/staging table data during development, injecting PRINT or RAISERROR statements to visualize code execution, copying UET data during various SyteLine copying operations - JobCopySp, etc., triggering asynchronous AES event, utilizing SubmitTaskSp to initiate Mongoose background task processing, Monitor/report errors.

Category: Full Code

Tier: BE

Notes: BE - copied extensibility - merging required. See note on EXTGEN within SyteLine Code Out of the Database Project section.

Perform these steps:
  1. Create EXTGEN procedure.
    1. Use the Edit Stored Procedure form or another SQL query editor to:
      1. Copy existing SyteLine stored procedure – no new or altered parameters are permitted. Number and type of parameters in EXTGEN must exactly match original SyteLine stored procedure.
      2. Ensure that the new procedure’s name follows the strict naming convention of EXTGEN_<base procedure name> where <base procedure name> contains the SyteLine code.
      3. Remove all code generated by ETPBlock.exe. It is required the standard EXTGEN code block is removed, otherwise an EXTGEN of an EXTGEN scenario will be created and is not recommended.
        Note: Cloud does not permit you to create procedures which contain dynamic SQL statements.
    2. Add custom code and submit the EXTGEN procedure to the database.