In the Administration Dialog of ProcMan we define the Object Browser definition for the emergency instructions, using the previously defined action:
After creating this definition the planners should be able to start the emergency instruction Object Browser:
In the Administration Dialog of ProcMan we define the process for the emergency instructions:
In the process definition we define the parameters we need, using proper parameter name prefixes:
In the process definition the previously defined actions have to be assigned to the activities and the process cleanup:
After creating this definition the developers should be able to start a new emergency instruction process:
In the Administration Dialog of ProcMan we define actions which we will need in the emergency instructions.
Action for the developer requests:
Action for the planner approval:
Action for the process report:
Action for the cleanup on process deletes:
Action for the Object Browser:
Imagine that in a company planed batch programs are running on several systems. The company needs an information system for production planners, where they can find emergency instructions for every planed batch program, in the case that it fails. For sure the information system shall also allow creating of new emergency instructions and maintaining of existing once.
In this example is shown how to configure the ProcMan’s Universal Object Module to handle this issue. The emergency instructions will be maintained by processes of a dedicated process type. The production planners can access the emergency instructions using the Object Browser.
In this example the process for maintaining emergency instructions has two activities. In the first one the developers specify a request for creating new or changing/deleting of existing emergency instructions. In the second activity the production planners approve the developer requests and save the requested emergency instructions into the ProcMan’s repository.
First, we need configuration file/files for the new process. In this example we will use one configuration file in all actions. After creating the configuration file etc/hos_docu_call_config_EI.php (EI means Emergency Instructions) as a copy of the sample file etc/hos_docu_config.php.sample and editing it, the configuration file looks like this (normally it would contain also descriptions in comments, but for the purpose of this document we removed them):
While editing the configuration file we have decided that the process ID will be 'EMERGENCY_INSTRUCTIONS', that the name of the repository archive will be 'EI', that the process parameter prefix will be 'EI.PROC.', that the prefixes of object key/data parameters will be 'EI.KEY.'/'EI.DATA.' , that there will be an object key parameters 'EI.KEY.SYSTEM'/'EI.KEY.DIR'/'EI.KEY.FILE' containing the information about the system/directory/file name of a program which is the object of an emergency instruction and that there will be an object data parameter 'EI.DATA.ENABLED' containing the information whether an emergency instruction is enabled or not. Further we have specified expressions for how the system, key and enabled information of an emergency instruction will be evaluated from the object parameters.