jph_tours
6th March 2015, 12:17
I am working for an Infor integrator and i still have questions on developments.

Customization of tables:
- Use of customer defined fields. It seems that it does not just change the definition of the table but just its dictionary $BSE/dict.
This could be a good solution for any migration. How can we then add conditions in the DAL, program script.
Can I customize the screens with these fields from the dynamic form editor or should i customize the display only from the WEB interface
- Creation of a secondary table, bound by the same key as the standard table and use specific features sec.add.table ...
Is archiving takes into account these kind of tables. How can i do otherwise ? What then is the impact in case of new feature pact installation.

Customization of screens:
- What is it desirable to use personalization features in web IU / LN UI or make changes to the dynamic form editor

Specic developments:
- Is it desirable to develop in the same package td, ti ... or create a specic package repeating the same module Coding?
- Is it not make more sense to focus on DAL 2 for behavior management screen fields?
- Are there any standard functions for exporting to Excel ?
- Should we use API reither than use diorect call to library often used in scripts. What is the impact on performance ?
- What are the best solutions for use in the case of realization of inbound or outbound interfaces with third party applications: ION, Web services, files, exchange ...

Other:
- Is it possible to activate SCM without having a development license?
- Does the launch of outdoor application Baan is always possible since the WEB UI and UI or LN, for example run Excel directly from a session
- How works the Workbench sessions ? eg tssoc8351m000.

Could you share with me your best practices.

bhushanchanda
6th March 2015, 13:05
Those are too many questions - Let me give it a try.


Customization of tables:
- Use of customer defined fields. It seems that it does not just change the definition of the table but just its dictionary $BSE/dict.

This could be a good solution for any migration. How can we then add conditions in the DAL, program script.


- Go through these threads and you will know all about CDF.
http://www.baanboard.com/baanboard/showthread.php?t=56416
http://www.baanboard.com/baanboard/showthread.php?t=60751&highlight=CDF
http://www.baanboard.com/baanboard/showthread.php?t=66548
http://www.baanboard.com/baanboard/showthread.php?t=65971
http://www.baanboard.com/baanboard/showthread.php?t=57212


Can I customize the screens with these fields from the dynamic form editor or should i customize the display only from the WEB interface


You can add them on forms using DFE.


- Creation of a secondary table, bound by the same key as the standard table and use specific features sec.add.table ...
Is archiving takes into account these kind of tables. How can i do otherwise ? What then is the impact in case of new feature pact installation.

Handling secondary tables is a critical task. You need to take care that you have a DAL2 for the secondary table. Go for it only if you have standard source code (in case if you are looking to handle standard session) I do not think archiving will take care of standard tables. When a main table record is deleted related secondary table records are not automatically deleted by the 4GL-Engine. The DAL of the main table is responsible for cleanup of related secondary table records.


Customization of screens:
- What is it desirable to use personalization features in web IU / LN UI or make changes to the dynamic form editor


Personalization features and DFE are two different things with each having its own features. Not sure how to compare them. Offcourse end-users can use Personalization Feature but not DFE.


Specfic developments:
- Is it desirable to develop in the same package td, ti ... or create a specic package repeating the same module Coding?


You can either have your own module code or you can have your own package. Development wise, having your own package is better. The directory structure is better with your own package.


- Is it not make more sense to focus on DAL 2 for behavior management screen fields?


With DAL and Extended DAL (DAL2) with UI Template, you can have a better control over your session fields.


- Are there any standard functions for exporting to Excel ?

Depends - If you want to export your form into excel, you have export to excel option. If you want to output your report to excel, you can create an Excel Device. You can create your own Device and code your own ttstpconv else you can programmatically create a csv file and open it with Excel on client. Search on board and you will find many threads.


- Should we use API reither than use diorect call to library often used in scripts. What is the impact on performance ?


If on LN, you can use DAL for record insertions. API has issues sometimes with MMT Sessions. DLL's are faster if you understand a proper usage. Generally, you should prefer combination of DAL and DLL's and use API only if nothing else is possible.


- What are the best solutions for use in the case of realization of inbound or outbound interfaces with third party applications: ION, Web services, files, exchange ...

ION comes with a lot of value added features with ION Connect, BOD's, BDE's. If you are good with developing SOAP based webservices, LN has inbuilt functions to call Webmethods of the webservices. So, again depends on you. But comparably, ION gives wider range of functionalities.


Other:
- Is it possible to activate SCM without having a development license?


I guess you will need a development license. SCM with Application Studio will need an additional license. Though not sure about this.


- Does the launch of outdoor application Baan is always possible since the WEB UI and UI or LN, for example run Excel directly from a session


Yes, inbuilt function start.application.local() can launch outdoor applications on client machine.


- How works the Workbench sessions ? eg tssoc8351m000.

Could you share with me your best practices.

Never used.