Use Case 3: Add properties to SyteLine CLM stored procedure-based report, EXTGEN

Scope: Additional SyteLine tables/columns, additional custom tables/columns, derived UET properties

Category: Full Code

Tier: UI, OB, BE

Notes: BE - copied extensibility - merging required, UI - personalized extensibility - FormSync required, because of merging requirements, consider use case #5 instead. See note on EXTGEN within SyteLine Code Out of the Database Project section.

Perform these steps:
  1. Create an extended IDO (see Mongoose documentation).
  2. Create unbound properties as placeholders for UET property values whose data types matches column data types.
  3. Personalize SyteLine report to add UET components (typically edit and static components).
    1. Adding new components may require adjusting flex regions or moving of other components
  4. 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.
    2. Add custom code and submit the EXTGEN procedure to the database.
      1. Add UET columns to SELECT statement(s).