Archive for Reporting

Change report – for domain setup

Is there a report mechanism available that would allow me to track any changes that have been made and by whom to the domain fields (e.g database definitions)

Comments (1)

How can I get a report of objects migrated to production during a date range?

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.

Comments

java.lang.NullPointerException error when running Phire compare

We get the following error when attempting to run a Phire compare:

Java Exception: java.lang.NullPointerException: during call of com.guiffy.inside.GuiffyReport.run. (2,763) PHI_FUNCLIB.PHI_COMPARE.FieldFormula  Name:PHI_RunCompare

What causes this and how can this be resolved?

Comments (1)

How to handle refresh of a TEST environment from production?

The key requirement that exists after the refresh of the test environment from production is to put back all the code that existed in the TEST environment prior to the refresh. The migrations that were completed all the way to production will be brought back to the TEST environment during the refresh. The changes to code that will be missing in the TEST environment after the refresh are those migrations that have not yet made it all the way to production. Phire has features that enables you to facilitate the re-applying of all the code that were in the TEST environment prior to the refresh.

Phire maintains a master record of all the migrations that have occurred as well as all the versions of the code that were migrated. After the refresh of the test environment, you can run the Database Refresh Report (found at: Phire Architect > Reports and Queries > Database Refresh Report).  This report shows the list of all the migrations made to TEST, but not to PROD. Once you have the list of all the migrations that need to be re-applied, you can send all those migrations to a release. Next, you can perform a release migration so that all the code that needs to be re-applied will be put back into the TEST environment.

So, as long as all your migrations are performed through Phire, you do not have to do any preparatory work prior to the TEST environment refresh. After the database refresh is completed, Phire provides you with the means to identify the code that needs to be put back and provides the mechanism to restore all the missing code.

Comments (2)

How to compare between two different Version Sets?

There is not a function to compare two complete version sets, but if you have a specific object in mind you can look at version history for that object and compare between two different versions.  Version history for specific object can be found at:  Phire Architect > Versioning and Restoration > Restore Objects.  From this component, you can select any two versions of an object and compare them against each other, or compare a version against one of the live databases.

Comments (2)