Environments page


This page will provide master -> detail -> detail  -> detail functionality.  The user will be able to add environments, the applications for the environments, the services for the environments and lastly the components for the services.

The only environments that can be entered are within the scope of the roles the user has admin privileges for.

The master (environments) is an interactive report.  This is because I used the wizard to create the page, and it's a "Report with form on a table". 

I've manually added to the region a select list that shows the roles for a user.  When creating a select list based on a sql query, the query has to return two values, the display value and the item value.  The first column returned by the query is the display, the second is the item value.  In my example below I concatenated the role_id so I could visually see the item value.

select role_name||' - '||role_description||' - '||role_id, role_id from ui_roles
where role_id in (select role_id from ui_admin_users where email_address = lower(:APP_USER) and role_name != 'ui_role_admin')
order by role_name

Display null values is set to Yes and the Null display value is "-- select a role --"

For the sql query for the report, added where role_id = :P6_ROLES
Must remember to add P6_ROLES to page items to submit.
Change create button action to "submit page"
Then added branch in processing section to go to page after submit. and add the role_id to the set items in the editing of the page in the branch.  Target it the column in the modal, source is the select list. also added clear cache of page 7.  This was to make sure it's always creating new environment

Next is to have logic that disables the create button when no role has been selected.

Did this using dynamic action. on change, item p6_roles. condition item is null. true action disables create button, false action enables create button.

When the modal form closed, the underlying report did not refresh.  To fix that created a dynamic action on the reports page.

da: Env DLOG Close
Event: Dialog Closed
Selection Type: JavaScript exp
JavaScript Expression:

this.data && this.data.dialogPageId === 7

on true action - refresh the environments region

changed the interactive report to interactive grid. had to get the ids populating again

to move roles select list to left, changed label column span to 1.


Comments

Post a Comment

Popular posts from this blog

Roles Page - Validations and Primary Key

Roles page is a master detail pair of Interactive Grids. Master is the Roles. Detail is the Admins. In the Roles IG properties, the Master Region is the Roles Region.  This appears to be the only setting required to do the master detail coordination. Validations required role_name - must be lower case, alphabetic characters, numerals and underscore.  No leading or trailing spaces. role_id - populated from sequence. email_address - must be lower case with @oracle.com the domain, No leading or trailing spaces. admin_id - populated from sequence.  This column was added to get the master detail coordination working in Apex, normally I wouldn't have used it, the original admin primary key of role_id with email_address didn't work in apex, the email address field would get populated with text of t100x by default. It seems there is some setting possibly of user updateable columns that I found on googling the issue but didn't play with it. role_description - requi...
Read more

Database triggers and Application Express

On the use or not of database triggers.  I've held a view that triggers have a narrower scope than many in the Oracle world.  This view has been challenged in my use of Apex.  Triggers have some significant limitations. - While Oracle allows multiple triggers of the same type to be created, it's not possible to control the order of the firing of triggers.  Why does this matter? If you are integrating to an existing system that has triggers, your trigger might fire before the existing trigger, or after. No assumptions can be made. - Triggers are quite difficult to debug. - Triggers can be disabled thus bypassing all trigger logic. - If integrating to an existing system, you may not have access / privileges to create triggers. Some have said these "limitations" are contrived / atypical.  That may be the case, my background is in Oracle Education (originally) and as a trainer I learned all of the capabilities and limitations of triggers.  My role is ...
Read more

Authorization scheme to prevent access to a specific page

Use of authorization scheme. The roles page is only to be used by a very small subset of users of this application.  An authorization scheme was created in shared components and applied to the roles page: select 'x' from ui_admin_users admin, ui_roles roles where roles.role_name = 'role_admin' and admin.email_address = lower(:APP_USER) Scheme type: Exists SQL Query Error message: You must be a role administrator to maintain roles.
Read more