Better PULL support
- Added additional information to the usage profiles regarding the support TLS protocols, if TLS is mandatory, the supported MEPs
- Added additional information to the usage profiles to the documentation
- The PModes of a single partner are now sorted alphabetical in the client
- Inbound PULL signals on non empty MPCs created a OS path error sometimes
- There are warnings now in the user interface if the user tries to perform MEPs for users that use a usage profile that does not support this - nonetheless it is still possible to perform the operations and configuration
- Depending on the usage profile of a user the outbound TLS protocol list is passed to the TLS engine
- There is a warning now in the log if a partners usage profile defines TLS to be mandatory and the connection is a unsecured connection
- The field RefToMessageId was set in outbound user messages even if the message was pulled - this has to be empty for PULL messages