Welcome to the Clarity SaaS Transition Blog series. This blog series provides customers with updates regarding the Clarity SaaS transition to the Google Cloud Platform™ (GCP). In the first few blogs, Broadcom provided updates on various aspects of the migration including the overview, pre-transition activities, the actual transition process, and the various authentication methods available in GCP.
This post will focus on how customers using Clarity PPM 15.7, or higher versions, can analyze their existing environments and review their customizations. Broadcom's next post will focus on how customers using Clarity PPM 15.6.1 and lower versions can use the PPM Customization Discovery Analysis Job to analyze and review customizations.
Customers using Clarity PPM release 15.7, or higher, can use the Customizations Overview report to view all the content that is not out-of-the-box Clarity PPM content. This report shows all content added as part of your implementation.
The report contains database objects such as tables, views, functions, etc... that are not included as out-of-the-box content in the Clarity PPM schema. The report also contains other types of custom Clarity content created, such as Studio objects and attributes, NSQL queries, GEL scripts, reports, and jobs.
The Customizations Overview report helps customers generate a list of custom attributes in their current production SaaS environment. Customers can then:
- Remove attributes they do not need.
This is crucial because many customers create customizations with a specific objective in mind. If this objective is a one-time activity, then the customizations still exist in the Clarity PPM database but are perhaps no longer utilized.
- Customers can use this transition as an opportunity to clean up their Clarity PPM database.
- Update their testing plans to ensure they test custom attributes in the GCP environment that will be provided to them.
The Customizations Overview report provides the following information:
|
Item
|
Description
|
Broadcom's Recommendation
|
|
Attribute
|
The report includes a list of custom attributes, for a given Object, created in Studio
|
No customer action is required. All attributes will be transitioned to the GCP data center.
|
|
Custom Script
|
The report includes a list of custom GEL scripts available in processes
|
Broadcom will only migrate GEL scripts whose status is "active" or "on-hold". Broadcom will not migrate scripts in a "draft" status.
Customers should review their GEL scripts & remove any scripts they don't use in their production environment.
|
|
Object
|
The report includes a list of custom Studio objects
|
No action required by customers. All custom studio objects will be migrated to the GCP data center.
|
|
Query
|
The report includes a list of custom NSQL queries
|
All queries will be migrated to the GCP data center.
Customers should review queries and remove any queries that they don't use in their production environment.
|
|
Report
|
The report includes a list of custom report definitions
|
All reports will be migrated to the GCP data center.
Customers should select a minimal set of key reports to be converted. Certain reports may require significant effort to convert.
To learn more about customizing reports, please review this blog. Customers should remove unused reports from the production environment.
|
|
Job
|
The report includes a list of custom job definitions
|
All jobs will be migrated to the GCP data center.
|
|
Function
|
The report includes a list of functions created in the Clarity PPM schema.
|
Broadcom will not migrate functions, that are not out of the box, listed here to the GCP data center.
|
|
Index
|
The report includes a list of indexes created in the Clarity PPM schema.
|
Broadcom will not migrate indexes, that are not out of the box, listed here to the GCP data center.
|
|
Package
|
The report includes a list of packages created in the Clarity PPM schema.
|
Broadcom will not migrate custom packages to the GCP data center.
|
|
Package Body
|
The report includes a list of package body definitions created in the Clarity PPM schema.
|
Broadcom will not migrate package bodies, that are not out of the box, to the GCP data center.
|
|
Stored Procedure
|
The report includes a list of stored procedures created in the Clarity PPM schema.
|
Broadcom will not migrate stored procedures, that are not out of the box, listed here to the GCP data center.
|
|
Table
|
The report includes a list of tables created in the Clarity PPM schema.
|
Broadcom will migrate tables listed here to the GCP data center.
|
|
Trigger
|
The report includes a list of triggers created in the Clarity PPM schema.
|
Broadcom will not migrate triggers, that are not out of the box, listed here to the GCP data center.
|
|
View
|
The report includes a list of views created in the Clarity PPM schema.
|
Broadcom will not migrate views, that are not out of the box, listed here to the GCP data center.
|
Thank you for being a part of the Clarity community. Please write to clarityppm.saas@broadcom.com in case you have any specific questions for us.
The next blog on using the PPM Customization Discovery Analysis Job will be published on April 20, 2020.
#ca_clarity_ppm #gcp #clarityppmsaas