You can reduce the number of packages a day by implementing a promotion, build and deployment schedule. When relying on a preset schedule for promotions, builds and deployments, efficient communication between CNC and development is essential. Object Management Workbench (OMW) can be configured to meet this communication need. By implementing the minor changes described below your organization will save time, improve the efficiency of communications with CNC and provide auditable records of object promotion requests.
What is OMW?
Object Management Workbench (OMW) is Oracle's tool within EnterpriseOne used to manage the development and promotion of objects between environments.
Typical Users of OMW
The most typical users of OMW are the following:
CNC administrators
Developers
Business Analysts
Use Case
The following Best Practice configuration is used when efficient and auditable communication between developers and CNC is needed.
Example:
Your Developer completes development of a new report in the DV920 environment (status 21) and it needs to be promoted and built to the PY920 environment (status 26) for testing by the user community. The developer would typically submit an email or helpdesk ticket to CNC requesting the promotion and build. CNC then promotes the project containing the new report from status 21 to status 26 followed by a package build for PY920. This can occur several times a day requiring multiple ad-hoc builds.
Best Practice Example:
Your Developer completes development of a new report in the DV920 environment (status 21) and it needs to be promoted and built to the PY920 environment (status 26) for testing by the user community. The developer would promote the project containing the new report to status 23 indicating it is ready for PY920 before the scheduled promotion and build time. CNC automatically checks for all projects at status 23 and promotes them to status 26 at the scheduled time and completes the process with a package build for PY920.
Typical Configuration
The typical OMW status configuration is as follows:
Status Use
21 In Development (DV920)
26 In Prototype (PY920)
28 Ready for PD
38 In Production (PD920)
Best Practice Configuration
The Best Practice OMW status configuration is as follows:
Status Use
21 In Development (DV920)
23 Ready for PY920
26 In Prototype (PY920)
28 Ready for PD
32 Management approval
38 In Production (PD920)
Benefits
By implementing the best practice OMW configuration described above your organization would realize the following benefits:
Efficient communication with CNC staff
Reduced use of email or tickets for recurring process of promotions and builds
Auditable logging of object promotion requests and approvals at each step
Increased development time up to the promotion/build cut-off time
Reduced number of package builds needed
Implementation
Contact GSI for help implementing this solution!
Have a question about Best Practices in JDE System Management, please contact us at inquiries@GetGSI.com!