T24: EB.TABLE.PROCEDURES & EB.TABLE.DEFINITION

[Adnan Bin Wasim]

Dear Friends,

 

Can anyone tell me what's the purpose of applications :

 

EB.TABLE.DEFINITION

EB.TABLE.PROCEDURES

 

N.B. using T24 R06

 

Kindly, explain with simple example.

 

Regards,

 

Adnan

 

[Pawel (privately)]

Hi,

 

This is another way of template programming. It is worth of consideration if you are going to build new T24 applications. It should be ok for typical applications.

 

Pros: abstraction from any T24 application (code) template. You are less affected on upgrades when you build your local applications using EB.TABLE.DEFINITION / EB.TABLE.PROCEDURES. You will not need to do anything with your applications even if application templates are changed.

 

Cons: not everything is possible. Concept has been also introduced in R06 and it is not really "mature" in this release I suppose. There were some problems / things that I disliked, but applications build that way were working.

 

You could build similar template code abstraction layer on your own. Just imagine that you take current templates (H, W, ...) and modify them so they call routines defined in your parametrization tables (eg. in EB.TABLE.PROCEDURES). Layout of application is defined in EB.TABLE.DEFINITION.

 

You should already have "live" examples in your R06 EB.TABLE.DEFINITION. Temenos will be also able to deliver you some basic information about this concept.

 

Hope this helps a bit :)

 

Kind regards

Pawel

----------------------------------------------------
Stwórz własną stronę startową!
Zbierz najciekawsze treści w jednym miejscu!
Internet od nowa! http://klik.wp.pl/?adr=http://pozbierane.pl&sid=902

[Iker Salbidegoitia]

These applications intend to substitute Template programming. EB.TABLE.DEFINITION will create PGM.FILE, STANDARD.SELECTION, FILE.CONTROL and file Layout when authorizing the record. Always will create $NAU and $HIS applications. Can add multivalues Drill downs and usual fuctions of applications

EB.TABLE.PROCEDURES will add procedures as is templates. Before Author, After Auth, Check ID Checkfiles, etc....

 

Saves lots of work when local developments are needed.

 

There are few cons but nothing a good design can not solve.

2009/10/31 Adnan Bin Wasim <adn...@gmail.com>

[Adnanbw]

Thanks Everyone....So much for enlightenin'


God Bless U

[Adnanbw]

Guys, I tried to create a test template using these applications but
no luck so far...As Iker mentioned that It's supposed to create
PGM.FILE, FILE.CONTROL AND FILE.LAYOUT itself...it's not happening...
Even if I create them manually , it's not quite working......Can u
anyone tell me exact steps i m supposed to take for creatin' template
using these applications.

Regards,

Adnan Bin Wasim




On Nov 1, 3:59 pm, Iker Salbidegoitia <iker.salbidegoi...@gmail.com>
wrote:

> These applications intend to substitute Template programming.
> EB.TABLE.DEFINITION will create PGM.FILE, STANDARD.SELECTION, FILE.CONTROL
> and file Layout when authorizing the record. Always will create $NAU and
> $HIS applications. Can add multivalues Drill downs and usual fuctions of
> applications
> EB.TABLE.PROCEDURES will add procedures as is templates. Before Author,
> After Auth, Check ID Checkfiles, etc....
>
> Saves lots of work when local developments are needed.
>
> There are few cons but nothing a good design can not solve.
>

> 2009/10/31 Adnan Bin Wasim <adna...@gmail.com>

>
>
>
> > Dear Friends,
>
> > Can anyone tell me what's the purpose of applications :
>
> > EB.TABLE.DEFINITION
> > EB.TABLE.PROCEDURES
>
> > N.B. using T24 R06
>
> > Kindly, explain with simple example.
>
> > Regards,
>

> > Adnan- Hide quoted text -
>
> - Show quoted text -