8.5
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.5
- System Requirements
- Basics
- Features
- The Nature of PReS Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Variable Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
Technical
The format of the IP address must be one of the following:
l 127.0.0.1: The local computer. Typically this IP should have all the accesses checked.
l 255.255.255.255: Everyone on the same subnet. This is equivalent to hard-coding the current
subnet, such as 192.168.1.255 or 10.0.0.255.
l 192.168.0.42 : A single IP address. This can be any valid address on the same subnet.
l 10.0.255.255:Any IPin the 10.0.X.X range.
To automatically detect machines on the network and add them
1. Make sure the machine you want to detect is turned on and the Messenger service is started
2.
Click on the Refresh button under the list
3. Add the necessary permissions to the detected machines
4. Click OK
5. Restart the Messenger service.
To remove an entry in the list
1. Remove all checkmarks from the entry
2. Click OK
3. Restart the Messenger service
Warning
The following considerations are to be understood when using the Access Manager to configure
IPlimitations:
l Each permission type (column)is evaluated from top to bottom (column per column)in the order
they are visible in the Access Manager window. This means that wide ranges should always be
at the top to increase performance. For example, if you accept HTTPconnections from any IP,