Skip to main content

Adding Copyright information to application export files

Oracle APEX 21.2 has introduced a new feature using which we can include copyright information in the application exports. There is a new application property Copyright Banner. We can enter copyright text here. We can use substitution strings #APP_NAME# and #YEAR# in the copyright text. When writing copyright text into the export files, APEX will replace these substitution strings with respective values. #APP_NAME# will be replaced with the current application name and #YEAR# will be replaced with the current calendar year in YYYY format.

So, let's enter some dummy text into Copyright Banner for testing.

Name: #APP_NAME#
All Rights Reserved.
Copyright (c) 1999, #YEAR#, XYZ-Dummy Company.
For further details please refer www.xyz-dummy.com/copyright

Copyright Banner Application Property

Now, if we export the application, then we can see the below copyright information at the top of the application export file as below. Observe, substitution strings are replaced with their values in the generated copyright text.

Copyright Information in the export file

If we export the application as a zip file, then there will be a text file with the name copyright.txt under the exported zip file. This file will contain copyright information. 

Sample copyright.txt file

Copyright information will also be included in Component Exports. However, when exporting components as a zip file, then copyright.txt will be included in the zip file only when Include installation files flag is enabled.

What do you think about this little feature added to APEX?

Thank you.

Labels:

Comments

Mydeen Bin Shajan said…
hi hari, No one should modify our codes or view. Is there any mechanism.
Since all codes are there in DB server. Only Developer should able to access.
Client IT also have access to DB but they should not touch Apex modification.
Please suggest any mechanism
May 20, 2022 at 12:29 PM
Hari said…
Hi Mydeen,

In such cases, you can install "Oracle APEX Runtime Environment". With this users can run their applications, but they will not be able to see or modify APEX code. Check below link for more details.

https://docs.oracle.com/en/database/oracle/application-express/22.1/htmig/about-apex-runtime-environment.html

Regards,
Hari
May 20, 2022 at 1:23 PM
Post a Comment

Popular posts from this blog

ORA-00936: missing expression error while updating data using Tabular form

Are you getting "ORA-00936: missing expression" error while trying to update existing data using tabular form? Are you using "Multi Row Update" or "Tabular Form" processes (ApplyMRU or Apply MRD), then most probably the issue is with a space or new line character you have entered in "Runtime Where Clause" section of "ApplyMRU" process However to know the exact reason behind the error, run page in debug mode and try saving data. Then see debug output. If the issue is with space or new line character which you have entered, then you will see entry similar to below as you can see above (highlighted with yellow color), APEX finds there is some value entered for  "Runtime Where Clause" and it will append this where clause to update query. Since it's not a valid SQL Update statement, we will get "ORA-00936: missing expression" error. Fix : It's obvious. Go to page designer and remove any spaces or new l...
Post a Comment
Read more

Interactive Grid - Conditional Enable/Disable

In this blogpost, I am going to discuss few approaches using which we can conditionally enable/disable Interactive Grid (IG) column(s) based on other column(s) values. Note:    There is a bug  30801170  in APEX 19.2/20.1 with respect to "enable/disable" dynamic actions for IG columns. Workaround for this bug is provided at the end of this blogpost . This bug has been fixed in APEX version 20.2. Client Side Only Conditions If conditions to enable/disable are simple, then we can check those conditions easily on the client side. For e.g. let's consider IG on EMP table with following SQL Query. SELECT EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO FROM EMP Let's consider the requirement as - Enable "Commission" column only when JOB is equals to 'SALESMAN' and disable "Commission" column in all other cases. This can be done declaratively using dynamic actions (DA) DA "Enable/Disable Commission - 1" Create DA and give it a prope...
4 comments
Read more

Interactive Grid - Bulk Operation on Selected Rows

What's the Problem? Let's say you have an IG on employee table and you want to update selected employees commission based on user's input. Ideally, it should be very simple, where you can write UPDATE statement in page process and select IG region as "Editable Region" under "Execution Options" of the page process. But, when you select rows and submit page, you can see that, this process won't get executed! The reason is  Selection of 'Row Selector' check-boxes is not considered as row-change. Thus selected rows are not submitted to server. So, is there any work around?  Yes! Luckily there are lot of JavaScript (JS) APIs available to work with IG. If you are not already aware, you can refer "APEX IG Cookbook"  or  JavaScript API Reference documentation. If we continue with above Employee IG example, when user selects IG rows, enters "Commission %" and clicks on "Update Commission" button, then we can writ...
36 comments
Read more