Forum

During implementation of Phire, or in a “development” instance of Phire, you may not want email being triggered as you test aspects of the application.  An easy way to halt this is turn off the email notifications completely.  This is done on the Domain Setup Wizard (Phire Architect > Architect Administration > Domain Setup Wizard), Step 2. Domain Definition, by unchecking the box: “Enable Email Notifications”.  It can still capture the history of the email events; it just doesn’t send them.

You cannot delete email templates online. You have to delete email templates using SQL delete statement:
DELETE FROM PS_PHI_EML_TBL WHERE PHI_EML_ID = ‘<template name>’;

You can delete a workflow by deleting the CR Type which it is based on.  That is, navigate to Step 3. Application Codes of the Domain Setup Wizard (Phire Architect > Architect Administration > Domain Setup Wizard), open the section for the Change Request Type, and delete the row.  That will also remove the setup on Step 13 and 14 associated with that type.

At this time there is no on-line method of deleting a domain.  But it can be done pretty easily using a SQL script that we deliver named DELETE_SETUP_DATA.SQL.  This can be found in the Script folder in the original Phire download package, or by contacting Phire Technical Support.

A workflow in Phire is derived from the Change Request Type definition.  So you would first create a new CR Type, and then you can create the task list that’s associated.

So start by navigating to:  Phire Architect > Architect Administration > Domain Setup Wizard, Step 3. Application Codes.  In the section for Change Request Types, you can create a new type with a description.  Then on Step 13. Workflow Definitions, you can create the series of tasks that make up the workflow.  Alternatively, if you have an existing workflow that’s pretty close to the one you’re trying to create, you can use the Copy Workflow button after you’ve create the new CR Type value.  Also, complete the setup on Step 14. Workflow Databases for the new workflow.  At that point it should be ready to test and begin using the new workflow.

If your Phire installation is made on a dedicated database, it would have most likely been installed onto a PeopleTools-Only SYS database. If that is the case, the default local node will be PT_LOCAL. To verify the default local node, do the following:

1. Login to the Phire application.
2. Navigate to: PeopleTools > Portal > Node Definition and click Search
3. The local default node will have “1” in the Local Node and “Y” as the “Default Local Node”.

To add content references in your Portal application to point to Phire components, follow these directions. This example shows you how you can add the Phire Architect home page as a link to your Portal application.

1. Login to Phire. Define PSFT_PA as a trusted node.
PeopleTools > Security > Security Objects > Single Signon
Add PSFT_PA as a Message Node Name and Save.

2. Login to Portal. Define PT_LOCAL as a trusted node.
PeopleTools > Security > Security Objects > Single Signon
Add PT_LOCAL as a Message Node Name and Save.

3. Specify the content URI text and Portal URI text for the PT_LOCAL node.
PeopleTools > Portal > Node Definition (Portal tab)

4. Add content reference.
PeopleTools > Portal > Structure and Content (Add Content Reference)
Node Name = PT_LOCAL
URL Type = PeopleSoft Component
Menu Name = PHI_MENU
Market = GBL
Component = PHI_HOME

Unfortunately, there is no relationship that ties the Functional Area list items to Issue Types to achieve what you described.  But you definitely can do it with a “Flex Field”.  You’ll just need to create a table that defines that relationship, and name it as the prompt view in the Flex Field configuration.  Also, I suggest that you make it a “required” Flex Field, then it will be shown on the Help Desk version of the Issue page – otherwise it will be hidden.

We provide the ability to copy the workflow setup from one domain to another using a Data Mover script. You will find a DMS named “COPY_WORKFLOW.DMS” in the scripts folder in the Phire release package. Prior to running this script, you will need to replace the tag values that are in brackets. Also, after the workflow is copied over, be sure to define domain security for the new CR Type.

This requirement has implications for external files (SQR, Crystal, COBOL, etc), and requires that a migration send the new copies of files to each of the file server PS_HOMES in the environment.  That can be done without any additional workflow or manual steps by just adding additional target paths to the File Directories setup.  That is, for “production” you can have multiple server/folder path combinations listed as targets; when a migration is performed then a copy will be delivered to each location.  This setup is found in the Domain Setup Wizard at Phire Architect > Architect Administration > Domain Setup Wizard, Step 10. File Directories.

Yes, you can easily clone a domain using the Domain Setup Wizard (found at:  Phire Architect > Architect Administration > Domain Setup Wizard).  In step 1 of the Wizard, input the source domain name in the Domain ID and input the new domain ID in the Target Domain field and save. That is all you need to do to clone a domain.