Ability to customize columns on a PVO at the offering level.

user716429-Oracle

Organization Name

The Cleveland Clinic Foundation

Description

To be able to configure the PVO columns selected for extraction at the Offering level and not only at the Job level.
Per Support: “This is by design. Each job is unique with its own PVOs, that each have their own unique customizations. The customizations you make to PVOs within the jobs do not have an effect on the Offerings which are tied to the root PVOs. A change in this design would be considered an Enhancement Request.”

Use Case and Business Need

BICC Changes in ESS schedules uncheck PVO Columns already Selected.
Recently we broke apart several existing jobs into smaller jobs typically consisting of between 1 and 5 PVO’s.
These PVO’s were already existing within an offering, however when we created the new jobs, the PVO customizations we had previously been extracting seemed to revert to “standard” for at least 40 PVO’s, by “standard” we mean assuming this to be the default column selections.
An example of this is from the StandardDistributionPVO.
This PVO exists in the CCF-PODetailAndRequisitioning Offering. We moved it from its original job and into a new job specific to it, i.e. it is the only PVO in the job. Instead of getting the expected columns however, it was found to have about 60 columns fewer than previously experienced.

 

More details

Why are some columns deselected in a PVO just for changing the job scheduling?
Should the customization be at the offering level and not the job level?

Original Idea Number: 7c4cb53486

Dave Kekish

This would have saved us a number of hours spent re-customizing the pvo's after we split the jobs up.