theWorX Archives - Page 17 of 76

MUX Views – Change Ownership

$0.00
This is a standalone process that can be run by an admin to change the ownership of MUX views from a specified user to another specified user. The process contains a single custom script, which has the following parameters that must be updated prior to running the process:

currentOwnerId (required): Resource ID for the current Owner (unique_name from srm_resources table)

newOwnerId (required): Resource ID for the new Owner (unique_name from srm_resources table)

viewCode (optional): Code for the specific view to update - leave blank if you want to transfer ownership for all views (odf_ui_views.code)

The script will update the owner for all views that are marked as shared, as long as the new owner doesn’t have a similar view with the exact same name. If there are views that can’t be updated, they will be logged in the process log. To Run:

Navigate to the process called Admin - MUX Views - Change Ownership.

Navigate to the Start Step tab, Click on the Update Owner action, and click the Custom Script Parameters tab.

Enter the Resource ID for the current view owner into the currentOwnerId parameter.

Enter the Resource ID for the new owner into the newOwnerId parameter.

If you want to update a specific view only, enter that in the viewCode parameter.

Run the process via Organizer in Classic.
Details
Tech-Trick – Purge Notifications

$0.00

Over time notifications can build up in the CA PPM system and should be purged, so as not to hinder performance. The SQL statements mentioned in the tech doc can be implemented within a process in CA PPM to either purge notifications on an ongoing basis or remove all of them at once.

Details
Capacity Planning by Role and Application – Oracle

$0.00

This portlet pulls back the Availability and Allocation totals by Role between a user-specified Start and Finish Date, then the user can drilldown to look at the information for Applications. The Time Period filter allows for comparing these values across different timeframes (monthly, weekly, quarterly, annual) as desired. Other filters allow for looking at Active or Inactive Roles (or both) and including Active or Inactive Projects (or both) in the totals.

Details
OWB Basics Module 7: Autoschedule

$0.00

This video describes the process to Autoschedule a project using OWB. The video is available in both .m4v and .wmv formats.

Details
Idea Allocations Uploader

$0.00

The idea allocation uploader allows you to import in allocations from an external Excel spreadsheet. Populate an Excel template with required fields then import them directly from the Clarity UI. Once imported you’ll see the allocations right on the Team tab of the Idea.

Details
Current Proxies – Oracle

$0.00

The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active. The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date).

Details
Time Entry and Approval Overview – Clarity PPM MUX v15.6+

$0.00

Rego’s training video that walks through the Time Entry and Approval process for Clarity PPM – Modern User Experience. This video was created using Clarity PPM version 15.6.

Details
Concatenate Multi-Value Lookup into One Field for Display Purposes – Oracle

$0.00

The Concatenate Multi-Value Lookup into One Field for Display Purposes technical trick provides an overview of how to group or concatenate the various levels and values of a Multi-Value lookup into one field in both Oracle and SQL Server environments. This allows the lookup values to be more easily displayed in a portlet. The function concatenates the values together using a choice of delimiter, which then allows the multi-value lookup to be viewed as one portlet column, in the same manner as any other object attribute.

Details
Allocation Compliance for PM (JS Report)

$0.00

Allocation Compliance for PM report gives a view of resource Allocation percentage for active resources on the team of an investment for a selected Investment Manager. It allows the PM to see resources on their project over the coming months and whether they are over or under allocated. Allocation Percentage is calculated as (‘Allocated Hours’ / ‘Available Hours’) * 100. User can further narrow their search Month Start Date and Investment Manager. User can use exact dates or relative dates for Month Start Date filter parameter.

Details
PrLock Clear for Timesheet Locks – Oracle

$0.00
The process is built to clear the random timesheet locks that happens occasionally. There are three Processes and one lookup component and one job definition in the package.

PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.

The Lookup PRLock Check (Timesheet) (Id: REGO_PRLOCK_CHECK) should be used to update the GEL parameters for the above process.

PRLock (Timesheets) Record Removal All (ID: rego_prlk_rc_rmv_all) This deletes ALL prtimesheet locks.

Or

Rego Remove Timesheet Locks (ID: rego_rmv_ts_locks). This process is run as a job “PrLock Clear for Timesheet Locks” which performs the same functionality as the above two processes. The process and job definition are separate XOG files.
Details
Project Allocation Uploader – Oracle

$0.00
The interface runs using a MS Excel template called Project Allocation Upload that will be distributed to users.

Configuration

A master object called Allocation Upload Files will be created. The object will contain a required attachment field on the create page that will receive the Project Allocation Upload MS Excel file.

A new sub-object called Allocation Upload Records will be created. This object will contain the fields necessary to receive the data rows from the Project Allocation Upload template.

The master object will store the file level data while the sub-object will store the rows that belong to the file.

Users must be granted security to view and edit the master and sub-objects in order to run the upload process.

Project Allocation Upload Template

The Project Allocation Upload template must remain static. Any changes other than creating additional time periods or additional rows will cause the process to error.

Only the Project Allocation Upload template can be used to load records to the new objects.

The Project Allocation Upload will only accept months across the x-axis in the format DD/MM/YYYY. The month headers must appear in the first row of the template and contain the first day of the month.

The template must be distributed to the users that will be using the upload functionality.

Users will be required to enter an Investment ID and Resource ID so the process can correctly identify investments and resources to upload the allocation hours against.

A Staff OBS is not required but can be populated by users to have the data uploaded into CA PPM.

The owner of the Project Allocation Upload template is responsible for providing users a valid list of Staff OBS Units.

Investments will not be created through the interface. As such a valid Investment ID must be provided.

Resources can be added to the investment team through the interface. If a valid Resource ID is provided the resource’s allocation will be updated if the resource already exists on the investment. If the resource does not already exist on the investment the resource will be added to the team along with the allocation hours.

The Project Allocation Upload template will accept hours, not allocation percentages. Because CA PPM stores allocations as percentages of a resource’s availability the upload process must convert hours to a percentage. As a result small rounding errors may occur in the neighborhood of .01 hours per month.

Resources cannot be removed from investment teams through the interface.

The Project Allocation Upload template will support allocation uploads to different instances of the same role on the same investment as long as different Staff OBS units are provided.

If multiple instances of the same role are assigned to the investment with the same Staff OBS the process will not know which instance of the role to upload the hours to. In these cases the process will consider these records as invalid. The PM will need to manually remove one of the instances or upload the hours manually..

If multiple instances of the same role with the same Staff OBS unit are assigned to the same investment in the upload template the monthly hours will be totaled by investment, by role, by Staff OBS.

The allocation template will follow the format in the screenshot area.

Process

To initiate the Allocation Interface a user will create a new Allocation Upload File instance, attach the Project Allocation Upload Template, and save the record. The file attachment field is an “enter-once” field, meaning that once a value has been set it cannot be changed. If a user wishes to upload another field they will create a new record.

After the file has been attached the user will be presented with two check box fields, one to Validate and one to Validate and Upload. Checking either or both options will initiate the process.

The process will first determine if any sub-object instances exist for the file. In other words, do any records already exist in the Allocation Upload Records sub-object pertaining to the newly uploaded file. If there are no records in the sub-object the process will use the uploaded file and read its contents into the sub-object. If errors are encountered during the file read they will be written to the process console, the process will throw an error, and end.

Next, records will be validated. Only the sub-object instances that belong to the master object will be validated. Records belonging to other master object instances will not be validated or processed. All records in a status of Ready for Processing, Failed Validation, or Xog Load Error will be validated. Records will fail validation if an investment is not found corresponding to the investment ID provided, a resource is not found corresponding to the resource ID provided, or the date provided is not valid, or a provided Staff OBS does not yield a match. Records that fail validation will be flagged as invalid along with a description as to why they failed validation. Records that pass validation will be flagged as Ready for Processing and locked. The sub-object instances can be exported to excel if further analysis is required. If the Validate & Upload option was not selected the process will end here.

Regarding the Staff OBS. Only one OBS can be designed as the OBS that the interface will use to validate the Staff OBS records.

The Staff OBS value from the template must match against the name of an OBS node in the designed Staff OBS.

If the Staff OBS value matches against multiple nodes in the Staff OBS the record will be flagged as invalid as the process will not know which node to use.

If the Validate & Upload option was selected the process will continue and any valid records will be xog’ed into the investment team. The xog will be executed as the user that initiated the process so any security rules enforced by xog will be respected by the process.

Successful records will be flagged as Processed Successfully in the sub-object and remain locked. Records that did not load successfully, due to a xog error or security limitation will be flagged as Xog Load Error, unlocked, and updated with a description containing the full xog output.

Records that failed validation or failed the xog load can be manually edited and revalidated, and attempt to be uploaded again. Subsequent runs of the process will not read in data from the file, but rather process only sub-object instances that currently exist.
Details
Time Tracking Stalker – Resource Manager – Oracle

$0.00

The Time Tracking Stalker - RM workflow process automatically sends an email to Resource Managers for each one of their resources that have not submitted their timesheet for a prior open time period, thus informing the RM if their resources are submitting their timesheets on time. Project Managers will also benefit since the notifications will help to ensure that time is being posted against their projects in a timely manner, helping to provide them with an accurate view of time expended on the projects.

Details