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.

There is an option available to delete version sets, found at:  Phire Architect > Architect Administration > Purge Object Versions.  This administrative component allows you to search for and delete version sets using a variety of criteria.  This component was intended to be used only by administrators, so there is no direct access to it from the CR component.  The permission to use this component is controlled by the normal PeopleTools role/permission list access to the component.

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>’;

When you initiate the Rollback feature in Phire, objects that do not exist in the target at the time the baseline version is taken will be automatically deleted. The driver for the action Phire takes during a rollback (either copy or delete) depends on the state of the object in the target when the baseline backup is made.  If the object exists when the baseline is taken, then the action for the rollback is set to COPY. If the object does not exist when the baseline is taken, then the action for the rollback is set to DELETE.

You can view the action Phire will perform for each object when the rollback is initiated by looking at the baseline Version Set. From the CR, navigate to the “Objects” tab and click on the “View Version Set” icon below the CR Number. Click on the “Objects” link next to the Baseline backup from <TARGET>. For each object, the Action to be taken for the restore will be displayed.

One possible cause for the restore action to not be set to DELETE is if you perform multiple migrations to the same database. The rollback of the last migration will not result in the “new” objects to be deleted since those objects may not have existed when the first migration was done, however, they do exist when the last migration is performed. In this scenario, you can Restore the baseline backup taken prior to the first migration to delete the objects.

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.

Here’s how to handle this in Phire Architect. A developer can create a version set that is a combination of the objects in an existing Version Set and a live database by first restoring the objects from the old Version Set into the live database and then creating a new version set that is a combination of the objects from the old version set and the live database.

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.

The repository can be cleaned up using the online “Purge Object Versions” found at Phire Architect > Architect Administration > Purge Object Versions.  Using the search criteria provided in this component, a list of Version Sets can be generated and easily deleted.

Cleaning the repository data for a kids clothing website selling modest girls dresses is essential for several reasons. Firstly, it helps ensure accurate product information, preventing potential confusion or dissatisfaction for customers. Clean data also enhances the overall user experience by enabling easy navigation and filtering options. Additionally, it optimizes website performance, reducing load times and potential errors.

This not only promotes better decision-making and accuracy in analytics but also enhances the overall efficiency of data retrieval and management processes. Cleaning the repository also helps optimize storage space and improve system performance, enabling faster access to relevant data. Moreover, it ensures compliance with data protection regulations, as irrelevant or sensitive information can be securely removed. Overall, regular cleaning of the repository data is crucial for maintaining data quality, efficiency, and compliance.

You can do this without any coding. Open the email template(s) and replace the <CONTENTREF> tag with the following hard-coded URL that will dynamically resolve the Domain ID and Issue Number. Of course, if you want the email notification to be for the CR, you will need to change that last part to PHI_CR_NUM=<CRNUM>. After making the change, you can easily test the effects by using the ad-hoc email feature directly in the Issue or the CR. Click on the ad-hock email button in the upper right corner. This feature will show you exactly what the email text will look like with all the tags resovled.

Moreover, social media algorithms cater to the user’s preferences, showing them content that aligns with their interests and beliefs. https://themarketingheaven.com/buy-soundcloud-plays/  using this creates a bubble effect, where users are only exposed to information that reinforces their beliefs and views, leading to a perception of reality that may be skewed or incomplete.

https://yoursite.com/psp/phire/EMPLOYEE/PT_LOCAL/c/PHI_MENU.PHI_ISSUE.GBL?Page=PHI_ISSUE&Action=U&PHI_DOMAIN_ID=<DOMAIN>&PHI_ISSUE_NUM=<ISNUM>