Migrating Security
Does anyone use Phire to migrate security permissions and roles. We were wondering how we could use Phire to assist in managing PeopleSoft security. We have HRMS, Campus Solutions and Finance.
Does anyone use Phire to migrate security permissions and roles. We were wondering how we could use Phire to assist in managing PeopleSoft security. We have HRMS, Campus Solutions and Finance.
With the publication of v13.2.00 in summer of 2018, the answer is “YES”. This feature works through a recurring process scheduler program that monitors an email inbox for incoming requests to approve/deny and posts them. The feature begins when the email notification is sent out to users that need to approve a CR. The new email template tag: <EAPRADDRESS> resolves to a series of hyperlinks in the email offering the user the options to approve or deny the request. Clicking the link sets up a reply email to the configured email inbox, and the user simply presses send. So a couple of clicks and the reply is sent for Phire to process. Success or error conditions are returned to the user in a reply email as the request is processed. The net effect is the same as if the user were to navigate into the CR through the PIA and click approve or deny.
Prior to this release of Phire, the application supported an email link to the “CR Task Approval” component, which shows a list of all CRs pending approval by the current user. Using this feature requires that the user log in to the application through the PIA to see and respond to items in the list. That feature is still supported as it always has been and for some users may be preferable.
Is there anyway we could add some Pass or Fail Verbs ?
Does PHIRE encrypt the code in transit between the environments?
Would there be a query to know when was the Phire upgrade was implemented. We can see that version can be found on PS_PHI_INSTALL but it doesn’t indicate when was it applied.
I would like to track the forum in Feedly. Is there an RSS Feed somewhere? I have not found one, yet.
Thank you,
john3
How to configure project naming convention so we can migrate the same project definition name from source to target environments including the project definition properties and comments? For example – When developers create a PeopleSoft project and they need to update the Project definition properties (who, when, incident number, what changes or why its need etc). We need to migrate same project definition (including properties) to other environments.
At Phire, we closely follow the updates to PeopleTools published by Oracle/PeopleSoft. As a result, we have historically published our support for new PeopleTools versions within 30 days of announcement by Oracle/ PeopleSoft. Here is a table of past and current PeopleTools versions and what version of Phire supports each:
PT Version Phire Version Availability
8.56 v12.1.05 Jul 2016
8.55 v10.2.05 Dec 2015
8.54 v9.2.00 Aug 2014
8.53 v8.1.01 Feb 2013
8.52 v6.2.04 Nov 2011
8.51 v5.2.02 Sep 2010
8.50 v4.2.04 Nov 2009