How does this Row level security work for User calling the CI via a PeopleSoft web service?

Row level security behavior for data updates via web service is different from the online component. This is expected behavior, and is due to the component design. Row level security for the component (which has implemented the row level security), e.g. CI_PERSONAL_DATA, may or may not work in the context of component interface (CI), depending on the component design.  The reason for this is the search record design in the component.  If the default component search record is not based on row level security view, it will NOT support row level security when this component is exposed as component interface (CI).

In summary, row level security support in CI (in all use case, e.g. exceltoci, ci based web service...etc.) depends on the base component design, especially on the default search record. If it uses a row level security view, then row level security will work in CI too. Otherwise, it will NOT work with CI.  In the latter case, if there is a requirement to have the CI (actually its base or underlying component) support row level security, it will require customization to the component itself.

Comments

  1. CI based webserice, User authentication should be enabled and user should have the required row level security, either user is constant/generic Id or all the users who are executing the CI based webservice. Customization will not required as such.

    ReplyDelete

Post a Comment

Popular posts from this blog

Peoplesoft Error: All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=5000(108,503)

Peoplesoft SFTP

Error: Think-time PeopleCode event (Exec), but a SQL update has occurred in the commit interval.