Bill McCormick wrote: >Because the background CSP process is not using a license - remember the >license is held by the session, not the process - we take a license on >the jobbed process by default. Then you can tie it to whatever you like >through the available API's.
This makes sense, but has the unfortunate side-effect that at least one free license slot must exist to start a job from a CSP page, even though this job shouldn't (and won't - after the login) take up a license slot. Doing the login *before* the Job prevents this requirement for an extra license slot, but presumably permanently ties the CSP process to a license, which seems undesirable. I have not found a way to return the CSP process to it's state of not using a license connection after the Job. Do you know of a workaround that removes the requirement of a free license slot without tying the CSP process to a license? Gertjan. -- Gertjan Klein
