23.1 Insight Release Notes
Industrial Hygiene Insight Stories
PMP-87292 BI - As an end user i want to have a Task Description field in Sample Detail Screen
BI - As an end user i wanted to have all the fields for Equipment Details section under Equipment And Controls as mandatory for Wipe Samples and required new fields to available
Included Surface Sampled Description and Area Description fields under Equipment Details in Sample Equipment.
Industrial Hygiene Package (Dynamic) >> Planned Sample >> Sample Equipment >> Equipment Details
BI - As an end user i want to have a Task Description field in Sample Detail Screen
Included Task Description field under Location Information in Sample Information.
Industrial Hygiene Package (Dynamic) >> Planned Sample >> Sample Details >> Sample Information >> Location Information
BI -As an end user i want to rename Drop down field value of Monitoring Equipment Owned By field
Now we have renamed the value Contractor to Contractor / Consultant / Rental for the Monitoring Equipment Owned By field.
Industrial Hygiene Package (Dynamic) >> Planned Sample >> Sample Equipment >> Sample Equipment Information
Learning Management Insight Stories
PMP-79867 BI - Assigning Multiple Plans to a Training Session
BI - Assigning Multiple Plans to a Training Session
Now the session can be created with multiple plans
Learning Management Package (Dynamic) >> Session >> Course Assignment Details >> Plan Details
Included Plan in the Outcome Details Report in the LMS Reports (Report Central)
Occupational Health Insight Stories
PMP-90465 BI -Renaming Sample ID for Drug test Encounter type screen
BI -Renaming Sample ID for Drug test Encounter type screen
Drug Sample ID, Internal ID and Samples Sequence are the new fields that included under Drug Testing Details in Details - Drug Test in Drug Test.
Occupational Health Package (Dynamic) >> Encounter Information >> Drug Test >> Drug Testing Details
App Builder Cognos Insight Stories
BI Impacts - Integrate the Common CAPA (CREATE) screen in app builder and change the saving approach
Now we are fetching the Action Item information from the application table instead of Mongo reference tables, with this change we can achieve data integrity as there won’t be any data sync issues and earlier we used to join the action items with app data over the Form ID and the Parent Uid at report level, with this change we don’t need to do any additional work at report end.
Related content
© 2018 ProcessMAP Corporation, All Rights Reserved Confidential, may not be disclosed without the express permission of ProcessMAP Corporation