Watch the webinar above, or view it on YouTube.

WEBINAR: CM evolveIT for LANSA Snack & Learn

Join us for a journey through the capabilities of CM evolveIT, highlighting the new LANSA capabilities. We cover CM evolveIT analysis capabilities including component impact analysis, Relationship Diagrams & Data Lineage analysis. All of these capabilities are available as a cloud-based SaaS browser application. The impact analysis can be visualized using interactive diagrams.

Use cases include:

  • Estimation of major change
  • Modernization of legacy LANSA applications
  • Meet audit and data traceability requirements
  • Interfacing with external applications
  • Facilitate on-boarding and minimize communication overhead
  • Provide a common reference for the Development and DevOps teams

The webinar is presented by Dimitris Vayenas, LANSA Enterprise Architect, and Roger Hammer, CM evolveIT Product Owner.

Webinar: CM evolveIT for LANSA Snack & Learn
Wednesday, March 10th 2021, 12:00pm-1:00pm ET

White Paper: CM evolveIT for CA Plex, CA 2E, and LANSA.

Webinar Q&A

Code to analyze complex code can easily become more complex than the code being analyzed. How do you focus down to the critical sections of code?
Our approach with the product is parse all potential information like a compiler, and then filter the information for the analyst – so they can focus on what is important to them. Our product architecture (API and Graph DB) enables a lot of flexibility for the analyst process the information in different ways

Is the solution, a licensed product for sale, or a service provided?
CM evolveIT for Lansa is a Cloud based software as a service (SaaS) application.

Does it have visibility to permanent file overrides?
EvolveIT provides the information in the repository in conjuction with the actual code that it runs. If any piece, not just this, piece of information is available via the LANSA Developer then it can be reported in EvolveIT as per the clients request.

How does it handle variable calls to functions and programs?, ie CALL #VARIABLE
At this stage, we just create keywords of all the variables, and you can search them accordingly as with any other “fixed/named” variable that points to fields/columns in the DB Schema. Moreover, we are in the process of grouping sets of variables so that one can search the concurrent existence of the same set of variables in different statements or sections of the statement. e.g. you can check if the combination of #param1 #param2 that exist in a WITH_ARGS exists in other statements or fractions of statements (e.g. in a TO_GET).

What about forms, server modules, Reuseable part, VL_Web an WAM’s? can they be used also?
Yes, it is work in progress. Our aim is to be able to link each and every field that appears on the application screen with its respective application field(s) and DB Schema column(s). We know it means a lot during troubleshooting to have this information readily available. We are looking for clients for proof of concept that employ v14, v15 VLF schema.

Can this platform connect to our LifeCycleManagement repo? – Rocket’s ALDON LMi
We have a portal based process to upload the model and source code to CM evolveIT. We will work with each customer that would like to integrate their LifeCycleManagement tool to our portal for updates.

I dont see nodes for web pages, reusable parts, forms, dialogs, views… do you support those kind of LANSA programs or just the older non-rdmlx green screen applications from the 90’s?
Currently we support the green screen applications, but there is on going work on actually connecting every field on the screen of the application with its respective application field and column on the DB Schema. To this end, the object(net), member(net) and property(net) of the VLF schema can be utilised.

Is the xref using the internal xref tables in LANSA or only looking in the code?
We are using a number of the internal XREF tables of the repository as a reference. Yet, the key determinant is the parsing of the actual code that exists (albeit in encrypted form for the old version of LANSA) in the repository. The repository is being used to gather references to the nodes, edges as extracted by our parser. Complimentary information such as Access Routes, Validation Rules etc., are extracted from the repository.

Our code is pretty complex, how could we do a POC?
Our POC process starts with an upload of your Lansa Model to our Portal. Everything else is handled by our automation to build a POC Database and send back your credentials for accessing the CM evolveIT Cloud instance with your Database.

How long does it take to install and configure?
There is no customer installation needed. CM evolveIT for Lanse is a Cloud based Software as a Service model enabling customers / users to focus on getting the answers they need and mot managing software and database updates. Once we receive your Model, we can have a customer up and running in a matter of a few days. Updates to a database can be completed in hours.