Creating the BII

The LN Studio online help describes how to model using tables of type ‘form’. Additionally, the following limitations must be taken into account for LN:

  • Only the Create/Change/Delete methods are supported for screen scraping BIIs. So no List/Show and no other standard or specific methods are supported. A constraint check is done in the LN Implementation Generator to enforce this.
  • The BOR Importer doesn't deliver form definitions or screen scraping settings. So the implementation of existing BOR-based screen scraping implementations cannot be migrated in one step to the LN Studio. Instead, the BID can be imported from the BOR and the Form Importer must be used to retrieve the session information from LN. Then a new BII can be modeled in the in the LN Studio.
  • Unless specified otherwise in this chapter, the constraints for BOR-based screen scraping implementations also hold for LN Studio screen scraping implementations.
  • Screen scraping can only be used for three types of LN sessions/forms: stand-alone sessions type 1 (single-occurrence), stand-alone sessions type 2 (multi-occurrence editable grid) and stand-alone sessions type 3 (same as type 2, but having view fields). Processing sessions (type 4) cannot be used. Also so-called ‘multi main table sessions’ cannot be used.
  • Using text fields is unsupported. Also language-dependent text handling is unsupported for screen scraping implementations.
  • So-called ‘segmented fields’ as used in some LN sessions cannot be modeled in the LN Studio.
  • Using sessions in ‘multi main table’ mode is unsupported.
  • At runtime, the processingScope of a request is limited to ‘business_entity’ and ‘business_entity_component’.
Note: 
  • Using screen scraping will significantly slow down performance.
  • Hooks (including method hooks) can be used for screen scraping implementations. You can also use a batch implementation for a method in a screen scraping BII.
  • Tables of type ‘form’ can be linked per component implementation. This means that it is possible to implement one component through a normal table mapping, while implementing another component through screen scraping. However, for a single component, database tables and forms cannot be combined.
  • Interaction points are unused in the business object runtime. The interaction point and its default value (if any) is handled automatically in the session. Consequently, if the interaction point’s default value in the LN Studio differs from the default value as defined in LN, the latter will be used.