APEX

Hi,

We have the following business situation: On one database we have 3 clients. They all use the "same" application just different versions of it. Some clients may use the same application version. All the schemas have the same tables, packages, etc and only differ in data content.

One way to do this is have 3 applications:

App 100 (v1.0). Parsing Schema = Client A
App 200 (v1.5). Parsing Schema = Client B
App 300 (v1.0). Parsing Schema = Client C

If we found a bug in v1.0 and needed to change it we would have to import v1.0 back into App 100 and App 300. Though this is currently not a problem it could be if we had 50 clients/schemas and had to manually import those changes.

An option that was discussed with our development team is to do the following:

App 100 (v1.0). Parsing Schema = 'Dynamic'
App 200 (v1.5). Parsing Schema = 'Dynamic'

*Before people start crying foul I realize that we will need a to define a default parsing schema for development and using the DML functionalities to automatically load data in forms etc.

To compliment only having 2 active versions we'd have a login application which would point the user to their appropriate "version" and the schema to use in that version. We'd store the logic in the following table:

USERNAME APP SCHEMA
clienta 100 clienta_schema
clientb 200 clientb_schema
clientc 100 clientc_schema

The "desired" parsing schema would be stored as a session variable.

Here's what we'd like to happen:

- User goes to our "login" application (residing an a separate / static schema)
- User logs in
- Lookup determines which application they should be directed towards and the schema to use in that application
- User automatically gets forwarded to the appropriate application passing the schema as a variable
- When they "hit" the application it looks for the schema variable and sets the default schema to that value for the session.

Example:

- ClientA logs in
- Look up determines that they are to go to Application 100 and use the clienta_schema schema
- Automatically forwarded to: http://.... parse_schema=clienta_schema
- I know this is not proper APEX syntax, I just want to ensure we focus on the issues at hand
- ClientA is now in Application 100 which is using the clienta_schema as the parsing schema

Can we do this? i.e. can we dynamically define the parsing schema?

I hope that this example outlines the business requirements. If you have any more questions please let me know.

Thank you.

Martin.