PJP Documentation > Reference Manual Menu
The Phantom Job Processor has the capacity to run previously defined Easy Out reports. To schedule an Easy Out report to be run by a phantom, the PJP administrator should enter “EO” in the run instruction field of the Process Detail screen. For defining a new process to run, the admin will be presented with 2 list boxes, allowing her to choose the report which needs to be run.
Easy Out reports can be set up under any of the 15 main menus of the TCS system. Once “EO” is entered for a new run instruction, the system will examine all of the currently defined Easy Out reports to see which of the menu classifications contain defined reports which are not already set up to be run by the current phantom. Menus which don’t contain Easy Out reports which are available to be set up will not be listed.
Here is a list of possible menu numbers and descriptions which may appear in the list:
1. Data Entry
2. Correspondence
3. Inquiry
4. Trust
5. Collector
6. Collector Management
7. General
8. Month End
9. Utility
10. Management Strategy
11. Precollect
12. Special User
13. Legal
14. Standard
15. Transactional Services
Once a menu classification is determined, the system will compile a list of Easy Out reports under that menu which are available to be added to the current phantom. If there is only one report, the admin will be asked if that’s the one that he wants to add. If there are more reports than one, a list of the available reports will be displayed on the screen.
After the desired report is chosen, the “Run Instruction” field will be built by the system and displayed as follows:
EO–nn-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Where “nn” is the menu number and the Xs are the report description.
Note: The admin should never try to build this run instruction directly by entering it into the “Run Instruction” field. The only way to set up an Easy Out report to run under PJP is to interact with the selection lists as described above.
This field is only visible if the run instruction points to an Easy Out report which has been set up to go to the printer instead of to a save-list, and if a folder has been set up in the Configuration Screen.
If a file name is entered here, the output from the Easy Out processing will be routed to a sequential file on your Cubs host. If this field is left blank, output will be routed to the printer.
Please only use alphabetic and numeric characters for the file name, along with underscores. At execution time, the program will append a date, time, and “.txt” to the file name entered here. For example, if you enter “My_File” here, the actual file name will look like this:
My_File_20110115_142341.txt
showing that the file was produced 01/15/2011 at 14:23:41. The file will be tab-delimited and will contain only the column headings and the detail line data with no formatting, subtotals, or report headings.
The usage of stacked inputs with Easy Out reports is discouraged. The TCS program to define Easy Out reports has the capability to set up user interactivity so that prompting takes place at run time. This is an important and valuable feature when a live user is involved to make choices about the immediate parameters to be fed into the report logic. However, the nature of PJP is that there is no live user to make such choices. Therefore, we strongly suggest that any “programmed” responses be configured at Easy Out setup time rather than at PJP setup time.
However, there is one exception to this rule. If the user is expected to enter a date on a report to be run by PJP, it may be appropriate to use one of the @DATE symbolic values which are available as part of the stacked input functionality.
Columbia Ultimate designed Easy Out to be interactively run by a live user. In adapting the Easy Out functionality to be useable under PJP, we had to bypass some of that interactivity. Because of that, here are a few constraints that we needed to implement:
- There is no facility for displaying an Easy Out report on the screen. Reports which are set up to be displayed on the screen will not be executed by PJP.
- The interactive prompting for Branch has been disabled.
- Some files (i.e. TRANS and TRANSX) can have 2 lives, depending upon the current pre-month end status. If PJP finds a pre-month end situation for one of those files, it will default to the pre-month end file (i.e. TRANSX) without prompting.
Copyright 2011, Cubs Consulting, Inc.