OA Page access without attaching to any responsibility

Question

All,
I have developed a page where employees can select the gift items. But this selection is possible only on their anniversary day. The page access link should not be available at any time.
So the plan is to send the page access link to them by email on their anniversary date.
The problem is, if I didnt attach this page function to any responsibility, the users will not able to access the page from the email link. (Insufficient privileges)
Is there any way to achieve dis without attaching to any responsibility. Or after attaching to responsibility, is thr any way to hide the link for the user when thy login into APPS?
thr r few workarounds like, give access to all, and on pageLoad check for their anniversary date and then allow if applicable..
Lemme know if there is any way to achieve that before going for the abv mentioned workaround..
- Senthil

Answer 1

Hi,
You want to develop a custom OAF page which can be accessed without login, You can develop using Anonymous or Guest Login implementation. If you want more details please give me your mail id i will send you the document about that.
Mukul/Tapash,
What i have told is about Anonymous or Guest Logins, i think i have discussed about this earlier.
Page Supports Anonymous or Guest Logins :
If you have a Guest user page to display that does not require a user to log in, then you should secure your page with a GUEST user permission. You should also have a explicit grant/function/responsibility assigned to the GUEST user. Note: GUEST is a special seeded user in the Oracle Applications Users form.
In our example, the Benefits Registration Page is an example of a Guest user page. To create a Guest user page:
Step 1: Set the Security Mode property of your page to Self secured.
Step 2: Implement the validateParameters() method in your controllers to protect the integrity of the URL.
Tip: Note that the above two steps are required because your page should exist outside a user's session, and is therefore "bookmarkable". You can find more information on how to set up bookmarkable pages in the Accelerated Validation topic.
Step 3: Set a permission on the rendered attribute of your page layout region using a function security SPEL expression.
So, in our example, let's create a permission called BENEFITS_GUEST, and set the expression ${oa.FunctionSecurity.BENEFITS_GUEST} on the Rendered property of the Benefits Registration Page. We will learn about how to associate this permission with a grant to the GUEST user in the subsequent steps.
The OA Framework requires no authentication and authorization to run a page that is secured using a GUEST user-granted permission.
Note: Although a GLOBAL-granted permission would seem logical to use, it actually is not appropriate in this case. All users except the GUEST user have access to pages that have a GLOBAL grant. In addition, GLOBAL users must first log in and be authenticated in order to access those globally-granted pages.
Thanks.
With Regards,
Kali.
OSSI.