Sometimes RPD administrators do not have direct access to files on the server hosting RPD. Step Resources are objects in RPD representing files uploaded by users directly into RPD and can be referenced by step templates properties. However, there are some places in RPD where Step Resources cannot be used. For example:
RunExternalProgram has no way of referencing a Step Resource in the External Command, such as to run a script uploaded as a Step Resource. It also has no way of referencing a Step Resource from the External control file template, but it can reference spool files using symbol notation, such as getFileName.
AssignJobValues Job values file can be a Step Resource, but you cannot set job properties to a Step Resource within that Job values file. An example of this may be that you want to set multiple control files for use in a later step.
SetDocPropsFromConditions Property conditions file can be a Step Resource, but the conditions file can't set any properties to a Step Resource.
It would be helpful to add some sort of symbol notation (such as ${getStepResource(MyStepResource)} to allow Step Resources to be used in instances like these.
