Notes for the Process Form

Process definitions

One must be made for each process. The most important information is the Process ID, which the administrator has no way of knowing otherwise.

Process Name

The name the Process is known as in the lists etc. in the administration module.

Process ID

The implementation name of the ProcessEntryPoint used to activate the function.

Process Comment

Enter any comments about the process or the deployment you wish to communicate to the administrator

Use Default Presentation

Enter Yes if the default Presentation is used (A Presentation with the same name as the Process - without any template suffix or override name).

Presentation Definitions

One for each Presentation - apart from the default Presentation.

Presentation Name

The Name of the Presentation. To some extent this ought to describe the special behavior of the Presentation.

Each Presentation defines a different look/functionality of a process. The Process ID is a unique identification of the process (specifying the implementation name of the ProcessEntryPoint for the process).

Template Suffix

The template suffix used when identifying the templates used by the process, when the Presentation is the current presentation. (E.g. a template called MYTEMPL as the base name will be called MYTEMPL_USER, when the suffix _USER is specified for the Presentation).

Template Override Name

When only one template is known by the Websydian Express framework, a template override name can be used.

This can for instance be relevant if you wish to just load a static page, which another party has supplied.

Presentation Comments

Enter any comment you wish to communicate to the administrator about the Presentation.

Frames for Frameset

This is only relevant for presentations using a frameset process.

If the Process defines a frameset it is important that the administrator knows exactly which frames he can use. All of the frames defined in the template by the /(NAME-...) replacement marker must be specified.

Objects

Physical Tables

Enter any new or changed physical files used by the process.

Views / Logical Files

Enter any new or changed Views/logical files used by the process

Server Functions

Enter any new or changed server functions (e.g. SingleFetch/BlockFetch - or more specialized business functions) used by the process.

Web Server Functions

Enter any new or changed web server functions (e.g. Page Generators, Eventhandlers, ProcessEntrypoint) used by the process.

Templates

Enter any new or changed templates used by the process. If you use several presentations for the process you can either indicate all of the templates used - or just give the base names - and let the administrator find all of the templates based on the presentations. You just need to be sure that developer and administrator agrees on which choice is made concerning this.