Forum

Yes.  In the Phire email configuration, any email notification can include and “Additional To”, “Additional CC” or “Additional BCC” address.

For the Issue Tracking module, you’ll see the options on Page 3: Application Code Definitions of the Domain Setup Wizard (Phire Architect > Architect Administration > Domain Setup Wizard).  The email notification link opens the details for each Issue Type.  Notice the grid tabs for “Additional To”, “Additional CC” or “Additional BCC”.  That entry can include a hard-coded email address, a listserv address or a reference to a user/role following the syntax described on the page help.

For the Change Request module, you’ll see the options on Page 13: Workflow Definitions of the Domain Setup Wizard (Phire Architect > Architect Administration > Domain Setup Wizard).  The email notification link opens the details for each step in the workflow.  The same tabs are available here to enter an address or a user/role.

We deliver a couple of queries that will provide this information.  Navigate to Phire Architect > Reports & Queries > PS Queries.  In that list you’ll find two queries to focus on.

First is:  PHI_OBJECT_RESTORE.  Run to HTML and follow the prompts to get a list of individual objects that were migrated/restored to the selected environment during the period.  This includes a reference to the CR number and the user that performed the migration.  The column on the far right will indicate “Workflow = Yes” if it was related to a migration event.  Those that have “Workflow = No” indicate that they were restored outside of the workflow as some special event, and may prompt further investigation.

Second is:  PHI_MIGR_REQ_HISTORY.  This one is similar but reports at a higher level just the migrations that occurred with the count of objects in each event.

These are delivered as regular PS queries, so if necessary they can be cloned and edited to change the criteria or columns shown.

A powerful feature of Phire is its ability to automatically perform the App Designer “project build” following a migration.  This of course is the process of synchronizing the database tables/views/indexes with any updated record definitions in the project.  Without this feature in Phire, a user needs to log into the target environment using App Designer following a migration to manually perform the build.

The trick however, is that the PeopleTools App Designer program only operates on Windows, thus Phire needs a Windows server to run it on.  So there are two choices if you want to automate the project build in Phire – either put Phire on a Windows application server, or setup a Windows process scheduler.   If using a Windows app server then the build can run in-line as part of the migration.   If using a Unix/Linux app server, then a Windows process scheduler can be used.  In that setup then the build is submitted as a separate process on the scheduler after the migration is complete.

The choice is set on Page 2: Domain Definition in the Domain Setup Wizard (Phire Architect > Architect Administration > Domain Setup Wizard).  The option “Build Method” includes options to perform the build on either the App Server or on the Process Scheduler (or None, if that’s your choice).  Additional setup for the process scheduler is shown if that choice is selected.

On the Migration page of the Change Request component are two buttons:  “Standard Migration” and “Ad hoc Migration”.

When entering a Standard Migration, the target is assumed based on the status of the workflow (see the Task page of the CR).  This generally represents the common migration path and business process that all work follows.  And controls in the workflow will prevent migration to a given target until prerequisite steps are completed, and then only by the assigned user or a member of the assigned role.  When complete, the workflow will automatically advance to indicate that the migration has occurred.

The Ad hoc Migration on the other hand, is intended to request a migration to a target that is not likely to be in the normal workflow, or in special circumstances to work outside of the controls of the workflow.  The Ad hoc Migration does not advance the workflow upon completion.  A common example is a training or sandbox database that is not normally part of the migration path, but occasionally needs to receive code as it moves through testing.  Another example is a test database that has been refreshed and needs a CR re-migrated – the ad hoc migration allows this to be done without having to fail the CR workflow back to the earlier migration step.  The list of available targets is setup on Page 14: Workflow Databases in the Domain Setup Wizard (Phire Architect > Architect Administration > Domain Setup Wizard).  Additionally, only a user with permission to migrate to the selected target will be able to initiate the migration.

This list of available databases on the Ad hoc Migration prompt page is setup page at: Page 14: Workflow Databases in the Domain Setup Wizard (Phire Architect > Architect Administration > Domain Setup Wizard).  Specifically, the databases that are marked with “Ad hoc Migration”.  To add more targets, just select and/or add the additional database entries and select the “Ad hoc Migration” check box.  This change takes effect immediately for all existing and newly created CRs.  Users with access to the CR can put in a request, but only users with permission to migrate to the selected target will be allowed to initiate the process.