Forum

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.

You can restrict object types using the “Object Type Restriction” setup in the Domain Setup Wizard (found at:  Phire Architect > Architect Administration > Domain Setup Wizard).  In that component, navigate to Step 3. Application Code Definitions and open the section for the Change Request Types. Note the button on the right side for the “Object Type Restriction”.

This setup is based on the CR Type and rules can be defined to limit the object types that can be added to CRs and migrated.  It can be configured to “Include” only certain object types, or to “Exclude” certain object types.  Complete the setup and save.  These rules take effect immediately for existing and new CRs.

First, you have seen the “Rollback” button on the CR Migration page, and understand that this will rollback all objects in the original migration.  Now, to selectively pick object(s), you need to navigate to the CR Objects page, and click into the “View Version Sets” button.   Then using the comment, source and date information, locate the baseline version set that would contain the original objects and click the object count hyperlink where you can see the list of individual objects contained in the Version Set.  Then locate the object(s) to restore and click the “Restore this Object Version” button: and follow the prompt.

Phire fully supports the migration of the audit field flags. In order to migrate the Audit Field Flags settings from one database to another, you need to add the Record to the Phire CR object list and have the action set to Copy. When the migration set containing the record definition is migrated, the audit flags will automatically be carried over to the target database.

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 while inspecting the electronic device to upgrade it, for any fixes on the electronic you might need a pcb stackup for any eventuality.

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.

You can accomplish what you want in your current release by following these steps.

1. Remove the source database name from the workflow definition for the “Add Objects to CR” step. This way, development can be done from any database and the developer can add the objects from App Designer project that is found in any database.  Navigate to Step 13: Workflow Definitions in the Domain Setup Wizard and Edit Details of the “Add Objects to CR” step and remove the value in the “Source DB” field.

2.  Remove the requirement for the source database in the “Create Migration Set” step. Navigate to Step 4: Task Code Definitions in the Domain Setup Wizard. Uncheck the “Source DB Required?” checkbox next to the “Create Migration Set” Task Name.

3. Remove the source database from the “Create Migration Set” step in the workflow. Navigate to Step 13: Workflow Definitions in the Domain Setup Wizard and Edit Details of the “Create Migration Set” step and remove the value in the “Source DB” field.

4. When performing the “Create Migration Set” step within a CR, the developer will now need to populate the Source Database at run-time. The developer can specify the Source database by clicking the “Additional Details” tab within the “Tasks” tab of the CR. The Source DB will be enabled and they can choose which database appears.

5. Define which databases are available for Add Objects and Create Migration Set.  Go to step 14: Workflow Databases and add any database and specify which ones you want to make available for Add Objects and Create Migration Set.

This is done through the workflow setup in the Domain Setup Wizard (found at:  Phire Architect > Architect Administration > Domain Setup Wizard).  Go to Step 14. Workflow Definitions, and drill into the details for the migration step in question.  Change the Task Trigger from “Migration” to “Migration w/Baseline” that forces the selection.

In the templates delivered with Phire this option is used for the production migration, and the regular “Migration” is used for the lower environments.  Often, in test environments customers don’t really rollback changes (if there’s a problem found in testing they just fail it in the workflow and re-migration after the developer has fixed it).  But it is important to ensure that the baseline is done migrating to production.

Also, note that this aspect of the workflow is set in the CR at the time it’s created and the setup will only affect new CRs moving forward.  The CR Workflow Reset component is available to address existing CRs if necessary.

Phire utilizes the same Application Designer mechanism to perform the Project Build that developers and administrators are all familiar with.  So the “Build Order” flag on the view record definitions controls this when performing a migration and build in Phire.

Looking at the workflow setup, the step named “Create Migration Set” is typically set with a source database and thus only gets marked complete when the developer successfully creates a Migration Set from that particular source database.  So you can be sure that the workflow will not advance to the later migration steps without that requirement being met.

Next, the migration steps themselves have an optional source in the setup, which locks it into migrating only from a Migration Set created from a particular source.  The source database value is often left blank allowing more flexibility, but can be entered to provide this tighter control.

There is no automated way to skip a workflow step based on existence or non-existence of an object type in the CR – the example being COBOL program which requires the additional manual compile step. The only way to handle your requirement is to make the step to compile the COBOL program an optional step that would be manually skipped by the developer if the CR does not contain a COBOL program. A simple way to communicate and document this situation is for the developer to note the COBOL compile requirement in the migration note.  It is also possible through the workflow API to write a custom method that interrogates the object list and triggers an email or pop-up message as a reminder if there is a COBOL in the list.  Contact support for more information on setting up the workflow API, if that seems like a useful option.