TED NAL Distribution removes filename from Run Path of Distributed Application

Filename is removed from Run Path when Applications are Distributed
Application Objects that have a "Path to file" value defined including a filename are losing the filename when they are distributed
The filename included in the "Path to file" value of an Application Object is removed once the Application is Distributed for some NAL-TED distributions.
This occurs for Distributed Applications that have the SOURCE_PATH macro defined and it is not used in the "Path to file" value.
This does not occur for Distributed Applications that do not have the SOURCE_PATH defined.
The "Path to file" value is not changed to reflect the subscriber location if the SOURCE_PATH macro is not defined.

Fixed in ZENworks 7 Server Management Service Pack 1 Interim Release 3a, available at https://download.novell.com

With the update installed, the Distribution process will no longer modify the "Path to file" for any Distributed Application. If the"Path to file" value needs to be modified for the Subscriber's location, define a SOURCE_PATH macro in the Application and use the SOURCE_PATH macro in the "Path to file" value. The SOURCE_PATH macro value will be updated with the Subscriber's information when the Application is Distributed.

workaround
Define and use a SOURCE_PATH macro in the "Path to file" value. This will prevent the "Path to file" value from being modified and losing the filename when the Application is distributed. This is also in line with the requirements when working with the updated code.

1. Create a Simple Application (or AOT style) that has no SOURCE_PATH defined and a "Path to file" value that includes a complete path with filename
2. Create a Simple Application (or AOT style) that has the SOURCE_PATH macro defined and a "Path to file" value that includes a complete path with filename
3. Create a Simple Application (or AOT style) that has the SOURCE_PATH macro defined and a "Path to file" value that uses the SOURCE_PATH macro and a filename
4. Create a MSI application that has no SOURCE_PATH macro defined and has a "Path to file" value that includes the complete path with filename
5. Create a MSI application that has the SOURCE_PATH macro defined and has a "Path to file" value that includes the complete path with filename
6. Create a MSI application that has the SOURCE_PATH macro defined and has a "Path to file" value that uses the SOURCE_PATH macro and a filename
7. Create a NAL TED Distribution that includes all six applications created above
8. Distribute the NAL TED Distribution to another site/server's Subscriber
   

Results:
Applications create in 1 and 4 above will not have the "Path to file" value modified in any way. The "Path to file" value will not reflect the Subscriber location.

Applications created in 2, 3, 5 and 6 will have the "Path to file" modified to the Subscriber destination and the filename will be removed.

Note: References to filename can be any filename at the end of the"Path to file" value.