Archive for Setup

How to set the default for the CR Type?

It is quite easy to set the default CR Type using 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.  Select the one to be used as the default, and save.  Alternatively, you can have no default forcing the user to select from the available list before saving a new CR the first time.


How to restrict object types allowed in a Phire CR?

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.


How to prevent Issue status from being updated by the CR?

You can prevent the update of the issue status as the CR status changes by updating the workflow definition and setting all the Issue Status fields to blank.

Phire Architect > Architect Administration > Administer Workflow, select the Domain and CR Type. For each step, blank out the Issue Status field.

If you have one CR to multiple Issue relationship, we recommend that you do not have the CR automatically change the status of the Issues. Instead, we recommend that you disable this feature using the instructions above and manually update the status of each of the associated issues.


How to handle development starting in multiple databases?

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.


How to force the selection of the baseline during migration?

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.


How to ensure that migrations are always done from a specific source database?

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.


How to enable developers to download files from different environments?

Developers can access files (SQRs, COBOLs, etc.) that are residing on the servers for the various environments from the Objects page within the Change Request. First, the developer needs to add the file name to the CR Object list. Then to download or upload the file from/to an environment, the developer needs to click the download or upload button next to the file name in the CR Objects. The prompt page will offer a list of databases available to the developer.

The list is controlled by setup in the Domain Setup Wizard on Step 14. Workflow Databases (found at Phire Architect > Architect Administration > Domain Setup Wizard).  There you will find the “File Upload” and “Object View/Download” options listed for each database within each CR Type.  The file upload option is further limited by “Restore Object” security and the lock status of the particular file within Phire.

How to test a fuse without a multimeter? This may sound difficult, but it is actually something that anyone could learn. Check this and much more in this link and find out about the best in the world of electronics


How to display the domain name in worklists such as My Change Requests?

The option to show the domain throughout the application is on the configuration page:  Phire Architect > Architect Administration > License Code;  in the checkbox labeled “Display Domain Name”.  This will take effect immediately in many of the work list and result list pages in Phire.  With this turned off CR numbers for example will be shown like this: “CR000001”.  With this turned on, they will be displays like this:  “HCM-CR000001” (where “HCM” is the name of the domain).

For customers that have just one domain in their Phire implementation, it’s reasonable to turn this off and keep the display simple.  But if there are multiple domains in the implementation, then it is important to distinguish the domain associated with a CR or Issue and it make sense to turn it on.


How to disable the auto-assign checkbox on the Issue without customizing?

You can disable the auto-assign checkbox on the issue component without customizing. This is done through Phire security. Navigate to:  Phire Architect > Security Administration > Domain Security

Select the Role from which you want to take away the auto-assign checkbox.
Click the Permission List link next to your Domain.
Uncheck the “Override Auto Assignment” permission.

Note: If the user belongs to multiple roles, you need to make you take away the above permission from all the roles. If at least one role assigned to a user has this permission, then the auto-assign checkbox will still be enabled.


How can the Directory Import feature in Add Files to CR page be disabled?

The “Directory Import” function is meant to be a feature for the developer to facilitate the inputting of the CR object list. Security implications of this feature is minimal since the files are not being imported; instead, this feature is simply determining the list of the files in a directory that is accessible from the Phire application server to make it easier to add the file names to the CR without having to type each file name.

Since this is a development function, there is usually not a requirement to disable this feature.  So, if you want to completely disable this function, you can do so by updating the PHI_CR_FILE_ADD page and making the “Directory Import” button invisible.


« Previous Page« Previous entries « Previous Page · Next Page » Next entries »Next Page »