Only synchronous requests provide a full request context, e.g. the user id. For async requests (e.g. web services without authentication) the user ID would not be available. That leads to problems when a process graph loads data from the user workspace or another process graph. Therefore, request information such as the user id must be stored with the process graph or the context should not come from the request, but from the user who has stored the process graph.
Only synchronous requests provide a full request context, e.g. the user id. For async requests (e.g. web services without authentication) the user ID would not be available. That leads to problems when a process graph loads data from the user workspace or another process graph. Therefore, request information such as the user id must be stored with the process graph or the context should not come from the request, but from the user who has stored the process graph.