A customer recently created some custom IScript that was triggered from a page button. Pressing the button popped open a new browser window with printer-friendly text saved down from a variety of data fields on the page. Everything worked fine except that not everyone was authorized to use the button logic. Isolating the error pointed to the custom IScript call, per the following line.
ViewContentURL(GenerateScriptContentURL(%Portal, %Node, Record.<custom recname>, Field.PRINT_BTN, "FieldFormula", "IScript_<custom IScript>"));
When implementing an IScript, the container or WEBLIB record name must be prefixed with "WEBLIB_". So the code line above should really read something like:
ViewContentURL(GenerateScriptContentURL(%Portal, %Node, Record.WEBLIB_<remainder of custom recname>, Field.PRINT_BTN, "FieldFormula", "IScript_<custom IScript>"));
An HCM 8.9 customer recently complained to me of unreasonably long waits to browse Job Openings. Skeptical and hasty, I assumed the problem was the individual's user ID or their computer. Maybe too many Job Openings related to their ID, or perhaps clearing the browser cache would help?
Wrong and wrong.
PeopleSoft HCM customers regularly copy their production database to development and test environments in order to keep the different databases synchronised and up-to-date. Regularly, the question arises as to whether to anonymise the production data so that maintenance personnel cannot access employees' confidential data. In the end, in our experience, most companies choose to better their application security but not to apply any data masking between production and its copies. But let's review some elements of the debate, and what data you might want to scramble if you choose this path.
Trevor Roskewich, Senior Identity Consultat at Nulli will be presenting to the Calgary Oracle User Group (COUG) at the Suncor Energy Centre at 8:00 AM on December 15, 2011. His presentation, co-produced with Lisa Gryschuk, Senior Human Information Consultant at Nulli, addresses the critical business integration between Human Capital Management and Identity Management.
HCM applications are a principle source of an organizations’ identity data and thus critical to your identity, access governance and security processes. Leveraging job classifications / codes an organization's identity and security processes are dependent on tightly integrating at the business and system levels to provide Request Based Access Control and Role Based Access Control (RBAC). Identity Access Management architects and analysts are working more strategically with their peers in Human Capital Management to provide their organizations with fluid management of human information while leveraging the two systems to increase productivity for all employees in the organization.
This presenation will be of interest to HCM Analysts, HR Supervisors, HR Managers, Middleware Architects, IAM Architects, Enterprise Architects and Security professionals looking to automate securing applications, databases and providing transparent information on who has access to what information within the organization.
Presentation: Identity of the Enterprise
Human Capital Management (HCM), also known as Human Resources (HR), is a critical application forming the foundation of every business’ success. Trevor will be speaking to best practices for HCM/HR and how they can support maximizing the financial and business process returns of deploying and managing enterprise provisioning and role management.
Aside from the wonderful grammar, this 11:15 AM session being held at Western Canada Regional User Group (WCRUG) in Vancouver, BC on November 10, 2011 will be of interest to everyone in the enterprise.
Human Capital Management (HCM), also known as Human Resources (HR), is a critical application forming the foundation of every business’ success. Knowing who your people are and what role they play along with associated cost/benefit metrics is what HCM/HR applications are best at performing. Nulli believes this Human Information (HI) is central to the success of many applications. High quality Human Information is a key requirement for reliable security and identity processes as well as for HCM.
For many years, Oracle has provided a well documented OAM SSO solution for PeopleSoft using typical header variable integration. However, PeopleBooks for PeopleTools 8.51 has become so, shall we say, refined, it's now harder to acheive success with such time-tested integration steps.