Regarding Lawson Landmark

Author
Messages
Vijay S
Veteran Member
Posts: 174
Veteran Member
    I have experience on working on Lawson 7.x, 8.x and 9.x versions of Lawson. I haven't had an opportunity to work on Landmark.
    I am mostly a technical developer and have experience on 4GL, case tools, bit javascript, process flow and little bit of design studio. I have the following queries.
    1) What language they are using in New modules of Landmark (Is it pure java or some propriety language which they have developed) ? I heard that HR and PR are still on Lawson 4GL ?
    2) Is is easy to customize and develop new programs as it use to be with 4GL and CASE tools?
    3) Are the tables designed in new module totally different with those still on S3 ?
    4) Is process flow automator able to interact with both new modules and the one in S3 using same DME and AGS calls.
    5) Is ESS/MSS still there ? Are there any difference(s) between S3 and the one having New modules.
    6) I hope LSF would still be there without any change(s) ?
    7) Is design studio still there ?

    Appreciate your help !

    Thanks
    Vijay
    Kwane McNeal
    Veteran Member
    Posts: 479
    Veteran Member
      Vijay,
      Landmark *currently* lives alongside LSF. What that means is *right now* there is still an LSF, but Landmark is going to be the new standard as time progresses.

      To answer your questions, here goes:
      1) As LSF still exists, the modules, toolsets, and languages that you know and love, still exist in v10, with the exception of javascript for Portal, as it has been refactored into SharePoint. As for Landmark, it's modules are written in a combination of HTML5, Java, and data is 'modeled' in something called LPL.

      2) Again, as LSF is still there for historic applications, yes you may use 4GL and CASE to your heart's content. As for Landmark based apps, no. There is no publically available toolset allowing you to modify any *base* code directly. Limited mods to the data definitions are available, and configuration is widely customizable in current releases of Landmark

      3) Data is modeled completely differently in Landmark/LPL, versus S3. Landmark allows for access to S3 tables in certain circumstances

      4) Essentially the answer is yes, but it's far more involved than I can explain in the post

      5) Yes, as LSF is still there. The nearest analogue to EMSS in the Landmark/LTM world are external employee and candidate endpoints. As the design is fundamentally different, it would take a training video to explain

      6) IT is, but it does have a fairly significant change, that being the presentation layer has been farmed out to a content engine (SharePoint).

      7) Yes it is on the LSF side.

      Hope this alleviates some concern.

      Kwane

      Vijay S
      Veteran Member
      Posts: 174
      Veteran Member
        Thanks Kwane . The information shared by you is pretty useful.
        ---