Support for re-using existing DFO requirements
May 31, 2024
1 min read
Defining which documentation is required for operations based on the object types is great way of ensuring a smooth and controlled hand-over to Operations.
Now it is easier to re-use the same requirements for multiple projects.
Introduction
Ensuring that all documents required for operations are delivered is a key focus during project planning and execution. In Omega 365 one can specify which type of documents are required for the objects. By tying documents to objects, one can then identify if the relevant document types have been delivered. The receiver can then approve or reject if the deliveries are satisfying the requirements.
The main process to ensure that DFO requirements are met
What is changing?
In the new version, one can now publish the requirements to org units. If it is published to an org unit, it will become an requirement for that org unit and those underneath.
