Application Services for System Objects

An Application Service is used to secure an ETPM Page, Portal and other system objects such as Maintenance Objects (MO), Business Objects (BO), Scripts, etc… Each Application Service has different modes based on the type of object.  For example, an Application Service for a BO may have Read, Write, Update, etc...  The Application Service and applicable modes are associated with a User Group.  One User Group may be Read-Only while another allows full rights.  Users are added to the User Group and allowed to perform applicable actions for the different objects.

This entry provides details on the conventions used in ETPM for the Application Services for different system objects. 

In order to determine which Application Service is associated with a specific system object, the following conventions are followed in ETPM: 

Old Style Pages: one Application Service for each separate page.  If the page is a maintenance page, the same Application Service is used to secure the underlying MO.  Example:  Person Maintenance Page

· The description of the application service matches the page name.

· The application service name typically follows the pattern "CILxxxP".

· The access modes are those related to the maintenance object actions.

Portals: each standalone portal has an application service that matches the portal code. 

· The application service's description typically includes the word "Portal".

· The application service name typically follow the pattern "C1xxxxx" / "F1xxxx".

· The access mode is Inquire.

Maintenance Objects: all new style maintenance objects have an application service separate from the page that maintains it.

· The application service's description is the MO description followed by "MO".

· The access modes are typically Add, Change, Delete, Inquire.

Business Objects: some BOs refer to the same application service as the MO. This is the case when there is no lifecycle defined for the BO.  For BOs with a lifecycle, there is a separate application service that defines the maintenance access modes plus access modes for any state transition. 

· The application service's description is the BO description followed by "BO".

· The access modes are typically Add, Change, Delete, Inquire plus any additional state transition based access modes.

Zones: for portals where disparate zones are visible, such as 360 degree view, the product provides an application service for each zone.

· The application service's description is the zone description followed by "Zone".

· The access mode is Inquire.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

This blog is for our Oracle Public Sector Revenue Management customers, delivery partners, and even our fellow Oracle professionals, and is dedicated to all things Oracle Tax and Revenue Management. We will focus on support and implementation tips, announcements, and FAQs (frequently asked questions) for all of our Oracle Public Sector Revenue Management products. This include Oracle Public Sector Revenue Management (PSRM), Oracle Tax Analytics, and our Oracle PSRM Self Service and integration products.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
3
4
5
6
7
9
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today